<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Wow Lisa,<br>
<br>
I am very grateful for your detailed reply to my 4 questions, and
for your kind invitation. Thank you! <br>
<br>
I receive and accept your kind invite. But before I act, I plan to
ruminate on your thoughtful send. <br>
<br>
Regards,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 10/19/14 7:39 PM, Lisa Heft - wrote:<br>
</div>
<blockquote
cite="mid:9CB2F3E5-2130-46C4-8E6E-E251784B4A17@openingspace.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hi, folks - Daniel it’s hard for me to stay in these email streams
for immediate back-and-forth because my life and client task work
does not always allow that - but I wanted to ‘dip my toe’ in and
say I echo what Michael H and Chris and others say about it not in
my experience being anything about public or private,
organizational or community, existing community or temporary one,
or any of that. It’s about thoughtful pre-work, appropriate
documentation design, selecting the right process (tool for the
job), doing good full-form Open Space, and other things very
specific to each client (sponsor / host / convenor / however we
wish to name them) and each situation or need.
<div><br>
</div>
<div>We’ve had earlier conversations on this list about what is
the minimum for what is Open Space, and our other conversations
(though you could see it differently / that’s welcome) tend to
find:</div>
<div>- host / client / sponsor / coordinator / convenor - usually
useful if it is not the facilitator </div>
<div>- facilitator though it does not have to be one that is
‘professional’ or uses this way of naming themselves</div>
<div>- opening circle</div>
<div>- agenda co-creation (without a facilitator’s ‘helping’,
merging, synthesizing, the group voting, etc. - all ideas
welcome and on the agenda)</div>
<div>- explanation of 4 principles and law (some people use the
5th principle, some do not, either works), butterfly, bumblebee
(for some, also ‘be prepared to be surprised’, for some people,
not)</div>
<div>- these guidelines / invitations above - about how
participants might choose to be - are usually helpful on visual
/ posters</div>
<div>- multiple discussion areas around (ideally) a great big
room, (ideally but different people have different opinions)
over multiple session times</div>
<div>- closing circle for reflection and comments</div>
<div>- ideally, some form of documentation so folks can see /
learn across all the groups, not just the ones they were able to
get to</div>
<div><br>
</div>
<div>Okay now here is where I would like to invite you to imagine
that each situation is different, when it comes to
documentation. I would like to invite you to release a
measurement of what is ‘timely’ and what is ‘late’ proceedings.
Assuming thoughtful discussions have happened in the pre-work,
appropriate documentation is designed, and this is (ideally)
custom for each event / organization / community / situation /
need / context.</div>
<div>There are some conversations which inform us (facilitator and
client) that it is absolutely appropriate to have a full
book-like, full-on narrative of all the conversations that
happened-sort-of-style-of Book of Proceedings. And reasons to
either turn it around overnight - right there in the event - or
reasons to on-purpose, delay dissemination to actually leverage
the momentum of the event, include reflective thinkers taking
more time for their notes (not just the quick-responders), help
people rest and integrate their experience before looking back
at their ‘data’ to learn about the knowledge shared across all
the groups, and so on. Reasons to say ‘everything in by x:00 and
we won’t be helping you remember that - whoever is in by then is
in’ - and reasons to interact with each convenor and notes-taker
post-event to ask if the’d like to add or refine or complete or
add things. Each need / situation appropriate to the context,
culture, use of information post-event, and so on. Sometimes
documentation is appropriate as a list of who raised what topic,
and that is all. Sometimes it’s about action and next steps.
Sometimes it’s just about knowledge-sharing without the need for
next steps. And so on. Whether organization or community, public
or private, conference or planning meeting, issue or
experience-sharing.</div>
<div><br>
</div>
<div>Then there is the ‘sponsor commitment to follow through’ -
which is nice (in those particular instances when that was
appropriate to the situation) but not always necessary, in my
experience. People do amazing things and (as someone mentioned)
not always measurable to the eye, ‘by 5:00’, post meeting, for
us to see. People do the work whether approval happens, if they
want to. They stay with an organization or leave it to follow
their passion, if they discovered their passion and voice in the
Open Space event. They find ways around. They decide not to. So
yes - in an organization, it’s always nice when the sponsor
commits, when pre-work conversations help the sponsor think in
advance, perhaps even create the mechanisms that support
follow-up and post-event sustainability. When really thoughtful
pre-work discussions inform whether action or next steps *are*
needed and possible *after THIS* event - or are unrealistic /
unsupportable, in reality. Or are better discerned and
articulated after reflecting on the patterns and learnings of
this event, even perhaps after more work is done identifying
resources or champions or partners and such, and where the Open
Space is part of a *chain* of meetings / actions / steps /
reflections / and so on over time.</div>
<div><br>
</div>
<div>And to me? It’s not about the process, that part. That part
is universal to any facilitation process that engages group
wisdom and diverse voices. </div>
<div><br>
</div>
<div>Here I go swimming away back into my life and client work but
I do like dipping in now and then ;o)</div>
<div><br>
</div>
<div>As always, thanks for inviting the question, Dan, and I look
forward to hearing, as always, what others think and have
experienced…</div>
<div><br>
</div>
<div>Lisa</div>
<div><br>
<div>
<div>On Oct 17, 2014, at 11:38 AM, Daniel Mezick via OSList
<<a moz-do-not-send="true"
href="mailto:oslist@lists.openspacetech.org">oslist@lists.openspacetech.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF" style="font-family:
TrebuchetMS; font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px;">Hi Michael,<br>
<br>
I'm confused now, and so I believe I am about to learn
something new here... I'll know by your answers to these
questions:<br>
<br>
What are the minimum essentials of Open Space structure?
For example, are the following elements necessary at all?<br>
<br>
<ol>
<li>Sponsor</li>
<li>Theme<br>
</li>
<li>Invitation in advance, referring to Theme<br>
</li>
<li>Opening Circle</li>
<li>Facilitator</li>
<li>Explanation of the 1Law/ 5Principles</li>
<li>Posters</li>
<li>Closing Circle</li>
<li>Timely Proceedings</li>
<li>Sponsor commitment to follow though on Proceedings</li>
</ol>
<br>
If these are not essential to structure, why not? If so,
why so?<br>
<br>
Thanks for your help! Very Eager to hear your (hopefully<span
class="Apple-converted-space"> </span><i>detailed</i>)
answers!<br>
<br>
Daniel<br>
<br>
<br>
<div class="moz-cite-prefix">On 10/17/14 1:27 PM, Michael
Herman wrote:<br>
</div>
<blockquote
cite="mid:CAD8j=QEsd3y3ZJBgS6yG264D9EJCRm4J9fWVtoSGo6t050QdPQ@mail.gmail.com"
type="cite">No. I'm saying the setting, context, culture
doesn't matter so much. The structure, setup and
commitment matter. I'm saying don't assume that public
gatherings aren't capable of having real impact. And of
course corporate/organizational/private isn't any
guarantee of impact and follow<span></span>through. <br>
<br>
<blockquote class="gmail_quote" style="margin: 0px 0px
0px 0.8ex; border-left-width: 1px; border-left-color:
rgb(204, 204, 204); border-left-style: solid;
padding-left: 1ex; position: static; z-index: auto;">
<div text="#000000" bgcolor="#FFFFFF"><br>
<div>On 10/17/14 10:15 AM, Michael Herman wrote:<br>
</div>
<blockquote type="cite">Not sure the differences you
articulate have anything to do with public and
private, Daniel. It's about the different
structures. I've seen very loose corporate
add-on events and very productive and long-lived
action (spanning years and continents) come from
open public conferences. So id say structure
matters much more than setting.Â
<div><br>
</div>
</blockquote>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta http-equiv="Content-Style-Type" content="text/css">
<title></title>
<meta name="Generator" content="Cocoa HTML Writer">
<meta name="CocoaVersion" content="1138">
<style type="text/css">
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Arial}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Arial; color: #0000ee}
p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Arial; color: #1a37ee}
span.s1 {text-decoration: underline}
span.s2 {color: #000000}
span.s3 {text-decoration: underline ; color: #0000ee}
</style>
<p class="p1">Daniel Mezick, President</p>
<p class="p1">New Technology Solutions Inc.</p>
<p class="p1">(203) 915 7248 (cell)</p>
<p class="p2"><span class="s1"><a
href="http://newtechusa.net/dan-mezick/">Bio</a></span><span
class="s2">. <a href="http://newtechusa.net/blog/"><span
class="s1">Blog</span></a>. <a
href="http://twitter.com/#%21/danmezick/"><span class="s1">Twitter</span></a>.<span
class="Apple-converted-space"> </span></span></p>
<p class="p3"><span class="s2">Examine my new book:<span
class="Apple-converted-space"> </span><a
href="http://newtechusa.net/about/the-culture-game-book/"><span
class="s1">The Culture Game </span></a></span><span
class="s1">: Tools for the Agile Manager</span><span
class="s2">.</span></p>
<p class="p1">Explore Agile Team <a
href="http://newtechusa.net/services/agile-scrum-training/"><span
class="s3">Training</span></a> and <a
href="http://newtechusa.net/services/agile-scrum-coaching/"><span
class="s3">Coaching.</span></a></p>
<p class="p1">Explore the <a
href="http://newtechusa.net//user-groups/ma/"><span class="s3">Agile
Boston </span></a>Community.<span
class="Apple-converted-space"> </span></p>
</div>
</body>
</html>