<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
For the past 6 years, since 2008, we have successfully used
this1-day conference event meeting design (listed below) to
socialize Open Space in Greater Boston. One of the design goals is
to give people a taste of OST and gently introduce them to the
concept and format.<br>
<br>
We have done 11 half-day Open Spaces with 175 or more people
participating, since 2008.<br>
<br>
The AM is what everyone thinks they want: the predictable and
well-understood conference format, the usual routine, with keynote,
breakouts etc. <br>
<br>
The PM is the canonical Open Space format as described in the Guide.
We do full proceedings, because we noticed that the Guide has lots
to say about these, and typical public OST events have weak
proceedings... or none at all. So we experimented and innovated a
little bit....<br>
<br>
Proceedings<br>
<br>
It includes full proceedings. We modify that a little: We have
people who process the proceedings for the session conveners. This
lightens the load on the session conveners and makes it more likely
that even a newbie will convene a session. They remain responsible
for seeing that the session proceedings gets collected. <br>
<br>
For smaller events, we render the PDF right there, by entering the
text and pictures of the artifacts (flip chart diagrams etc) <br>
For larger events, we take a picture of the filled-out forms, send
them to a transcriber we have engaged, and they send back the text
in real time during the event. The event ends and within 12 hours we
can get the PDF into everyone's inbox. 90% of the woerk is done when
the Open Space ends. Then we drink martinis. And to the rest the
next day.<br>
<br>
Multiple Exit Points<br>
<br>
One aspect of the 1-day design is what we call "multiple opt-out
exit points": people new to Open Space might NOT be comfortable with
it as described in print. So we provide explicit messaging in the
promo, like this:<br>
<br>
"Open Space in the afternoon..after a great lunch..."<br>
"You do not have to do anything at all during the opening. You can
just sit quietly and observe it."<br>
"...if you do like it, you can participate for awhile, and even
then, leave anytime you want...."<br>
<br>
So the thinking of new participants might be....<br>
<br>
"...I'm going to the event to hear from the AM speakers. The lunch
is free, so I stay for that..."<br>
"...This Open Space thing..hmm...it says I can observe the opening
without having to do anything, maybe I'll do that...sit in the
back....and bailout if it's not my cup of tea....if I stay, I can
still play passive, and exit anytime....hmmm..."<br>
<br>
The basic idea is to invite people into it. We do that by providing
multiple opt-out exit points. Easy. We do messaging that makes it
plain you can watch the opening and decide for yourself if you want
to stay or go. Etc...<br>
<br>
They usually all stay. All day. They get to the opening and once
they are there, they usually go all the way. Many newbies end up
convening sessions!<br>
<br>
=========================<br>
Agile Boston 1-day Conference format:<br>
=========================<br>
Moving through time: AM is a traditional conference, PM is Open
Space<br>
<br>
AM: Theme X (might be stated as a statement) <br>
<br>
Keynote speaker (full assembly)<br>
Break<br>
Other plenaries (full assembly, shorter time length than keynote)<br>
Break <br>
Breakout sessions (held in smaller spaces)<br>
<br>
LUNCH<br>
...setup Open Space at lunch...<br>
<br>
PM Theme X (always stated as a question) <br>
<br>
Open Space opening circle<br>
Open Space<br>
Open Space closing circle<br>
Social/happy hour<br>
<br>
Within 24 hrs or less:<br>
Proceedings out<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<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>