<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1250">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Georgia;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'>Hi Michael,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'>Thanks for sharing this. It’s something I have
wanted to try, but not yet found a sponsor ready for it. My only other
experience was connected to the Community Commons project where we uploaded all
the proceedings to a wiki and then circulated the URL to community stakeholders
and media to make the proceedings widely available to the community in the
hopes of continuing the conversation in the grocery store, by mailboxes, etc…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'>I am currently working on how to interweave the
proceedings (especially the action planning) with the Community Weaving
website. This is particularly for community-based initiatives where the
connections can be more difficult to sustain than in a company. The
idea is basically, that sponsors can be trained as community weavers so they
have access to all reports and the resource treasury. Participants
register as good neighbours and can form action groups and post and record
activities using the CW website. All of the ripples of the event can be
tracked by the sponsor CW’s (and the community at large)—who are
basically witnesses to the self-organizing of the participants. As all
the activities are visible and available to the whole CW network, it provides
opportunity for the ripples to spread as others in the community become aware
of what’s going on and follow their two feet. Lots of other upsides and synergies
with this one, and still some hurdles to navigate.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'>Cheers,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'>Wendy<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Georgia><span style='font-size:12.0pt;
font-family:Georgia'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=3 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> OSLIST
[mailto:OSLIST@LISTSERV.BOISESTATE.EDU] <b><span style='font-weight:bold'>On
Behalf Of </span></b>Michael Herman<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 05, 2007
2:28 PM<br>
<b><span style='font-weight:bold'>To:</span></b> OSLIST@LISTSERV.BOISESTATE.EDU<br>
<b><span style='font-weight:bold'>Subject:</span></b> documenting for ripple
effect</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hi All, <br>
<br>
Just back from a "senior executive forum" for a company in South
Africa, 1.5 days in OS, where we did something new and different with
documentation. We tweaked the notes reporting template to help start a
weblog with the proceedings, as soon as the corporate IT guys can get the tech
side of things together. <br>
<br>
This Forum was top 60 people in the company. 600 others report to
them. The 60 have been meeting semi-annually for several years, and know
themselves to be a circle. The 600 are the beginning of the rest of the
org (of 12,000 total) all of which currently knows itself as a set of silos
rather than circles. <br>
<br>
So with the proceedings, we asked the usual... issue, convener, participants,
summary. To satisfy the corporate yearning for action, we had a space for
'immediate next steps' in the template. Then we added to other
fields: Summary for 600 direct reports (if not same as above) and Summary
for Whole Organization (if not....). <br>
<br>
On most issues, scribes said share with all. On a few issues, qualified
summaries were written. On all issues, this will provide the necessary
info to establish a weblog that can be open to at least the next largest
circle, with the thought that this new view of "strategy" might be
offered to the 600 and ultimately "leaked" out to the rest of the
organization. <br>
<br>
The hope is that we might use these proceedings and followup news in weblog
form to help turn the 600 into a circle of conversations, that might eventually
also be convened periodically, in whole or in parts, in open space. It
helps, as well, that these 60 will continue to meet and generate news in
semi-annual gatherings. <br>
<br>
I thought there might be other places where we are working where it would make
sense to ask participants to craft directly and immediately their messages for
some larger circle of colleagues or stakeholders, with or without a blog
structure as the delivery/conversation vehicle. <br>
<br>
Anybody else documenting events in weblogs these days?<br>
<br>
On our way from "meetings" to "practice."<br>
<br>
Cheers, MichaelH<br>
<br>
<br clear=all>
<br>
-- <br>
<br>
Michael Herman<br>
Michael Herman Associates <br>
<st1:Street w:st="on"><st1:address w:st="on">300 West North Ave #1105</st1:address></st1:Street><br>
<st1:place w:st="on"><st1:City w:st="on">Chicago</st1:City> <st1:State w:st="on">IL</st1:State>
<st1:PostalCode w:st="on">60610</st1:PostalCode> <st1:country-region w:st="on">USA</st1:country-region></st1:place><br>
<br>
phone: 312-280-7838<br>
email: <a href="mailto:michael@michaelherman.com">michael@michaelherman.com</a><br>
skype: globalchicago<br>
<br>
<a href="http://www.michaelherman.com">http://www.michaelherman.com</a><br>
<a href="http://www.openspaceworld.org">http://www.openspaceworld.org</a><br>
<a href="http://www.chicagoconservationcorps.org">http://www.chicagoconservationcorps.org</a>
* * ==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU ------------------------------ To subscribe,
unsubscribe, change your options, view the archives of
oslist@listserv.boisestate.edu: http://listserv.boisestate.edu/archives/oslist.html
To learn about OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist <o:p></o:p></span></font></p>
<p><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>--<br>
No virus found in this incoming message.<br>
Checked by AVG Free Edition.<br>
Version: 7.5.446 / Virus Database: 268.18.26/748 - Release Date: 4/5/2007 3:33
PM</span></font><o:p></o:p></p>
</div>
</body>
</html>
<BR>
<P><FONT SIZE=2>--<BR>
No virus found in this outgoing message.<BR>
Checked by AVG Free Edition.<BR>
Version: 7.5.446 / Virus Database: 268.18.26/748 - Release Date: 4/5/2007 3:33 PM<BR>
</FONT> </P>
*
*
==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of oslist@listserv.boisestate.edu:
http://listserv.boisestate.edu/archives/oslist.html
To learn about OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist