<html 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=us-ascii">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 10">
<meta name=Originator content="Microsoft Word 10">
<link rel=File-List href="cid:filelist.xml@01C413D7.90A5FC30">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:Compatibility>
<w:ApplyBreakingRules/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:536871559 0 0 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
p
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
mso-pagination:widow-orphan;
font-size:8.5pt;
font-family:Verdana;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
p.style1, li.style1, div.style1
{mso-style-name:style1;
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
span.emailstyle18
{mso-style-name:emailstyle18;
font-family:Arial;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:red;
mso-text-animation:none;
font-weight:normal;
font-style:normal;
text-decoration:none;
text-underline:none;
text-decoration:none;
text-line-through:none;}
span.EmailStyle19
{mso-style-type:personal-reply;
mso-style-noshow:yes;
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:10.0pt;
font-family:Arial;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:navy;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]-->
</head>
<body lang=EN-GB link=blue vlink=purple style='tab-interval:36.0pt'>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color=navy
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt;color:navy;
mso-ansi-language:EN-US'>So we in <span class=SpellE>OSworld</span> intimately know
the simplest method of communing- opening the space so that hierarchy doesn’t
<span class=SpellE>monopolise</span>-rule, and human common sense flourishes
over time<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color=navy
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt;color:navy;
mso-ansi-language:EN-US'>Yet my research of </span></font><st1:country-region><st1:place><font
color=navy><span lang=EN-US style='color:navy;mso-ansi-language:EN-US'>UK</span></font></st1:place></st1:country-region><font
color=navy><span lang=EN-US style='color:navy;mso-ansi-language:EN-US'> open
spacers the last 3 weeks shows an extreme modesty. We <span class=GramE>mumble
:</span><o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color=navy
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt;color:navy;
mso-ansi-language:EN-US'>-yes OST is the best <span class=GramE>agent for
making hierarchy connect</span> positively with other forms of self-<span
class=SpellE>organising</span><o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color=navy
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt;color:navy;
mso-ansi-language:EN-US'>-BUT clients only want one OST, so it’s a loss
leader to run a facilitation business around</span></font><span lang=EN-US
style='mso-ansi-language:EN-US'> <font color=navy><span style='color:navy'><o:p></o:p></span></font></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'>I beg to disagree - wholeheartedly. Here’s
an exploration. Join in; say how to do it better; but I will hear no more of
OST being difficult to design in as the connecting thread of large scale or
continuous <span class=SpellE>organisational</span> change. That’s false <span
class=GramE>modesty ,</span> what <span class=SpellE>todays</span>’ world
can least afford from us.<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'>Exploration 1<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'>Convene roundtables of 5 people in 1-day
open spaces. Find some way to make the topic people come to discuss getting
over hierarchy in an <span class=SpellE>organisation’s</span> system (and
how any such process figuratively or literally depends on continuously opening
space). At these roundtables, I suggest inviting people whose function gives
them the budget to buy something that starts continuous system change from
hierarchy being the big loser in the <span class=SpellE>organisational</span>
design, to it being the connector with making teams win, or people’s
networks win or whichever is the self-<span class=SpellE>organising</span> you
believe a company’s context most needs to promote first<o:p></o:p></span></font></p>
<p><font size=1 face=Verdana><span style='font-size:8.5pt'>HR1.1 The first time
a large organisation's system gets over hierarchy is the greatest value
multiplying breakthrough. (After that, designing the best of hierarchy and the
best of every form of knowledge working is relatively simple as an
organisational change intervention) <o:p></o:p></span></font></p>
<p><font size=1 face=Verdana><span style='font-size:8.5pt'>HR1.2 Ask which is
your organisation's breakthrough KM arena: hierarchy &...<br>
<span class=GramE>examples</span>:<br>
<span class=GramE>hierarchy</span> & teams<br>
<span class=GramE>hierarchy</span> & <span class=SpellE>CoPs</span><br>
<span class=GramE>hierarchy</span> & people's social networks<br>
<span class=GramE>hierarchy</span> & value exchanges as mapped by <span
class=SpellE>Allee</span><br>
<span class=GramE>hierarchy</span> & transparency across networks of organisations
as needed in Nuclear clean up<br>
<span class=GramE>hierarchy</span> & selectively empowering entrepreneurs (<span
class=SpellE>eg</span> including collaboration with SME clusters)<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'>I have it mind that the way to negotiate
who wants to come such roundtables may be to start publishing such pattern
rules (of trust-flow or value multiplication) anywhere that people read. I need
help <span class=SpellE>wordsmithing</span> this pattern rules. I need help
exploring how we do these roundtable workshops. I openly hope that someone
somewhere makes a great business out of them faster than I do but that we share
the confidences. I will not rest while I hear facilitators of Open space tell
me they cannot design OST as the central connecting method that governs
continuous change in <span class=SpellE>organisational</span> systems. We are
losing the world while you confess that OST is the loss leader in your
businesses. <o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'>Hope it was OK to speak openly like this.
Transformation was never going to be a wholly modest game to play. Was it?<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'>Chris macrae, <a
href="mailto:wcbn007@easynet.co.uk">wcbn007@easynet.co.uk</a><o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><st1:country-region><st1:place><span
class=SpellE><span class=GramE><font size=2 color=navy face=Arial><span
lang=EN-US style='font-size:10.0pt;font-family:Arial;color:navy;mso-ansi-language:
EN-US'>Uk</span></font></span></span></st1:place></st1:country-region><font
size=2 color=navy face=Arial><span lang=EN-US style='font-size:10.0pt;
font-family:Arial;color:navy;mso-ansi-language:EN-US'> mobile 0793 144 2446<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy;mso-ansi-language:EN-US'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:
12.0pt;margin-left:72.0pt'><font size=3 face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt;mso-ansi-language:EN-US'><br>
<br>
<?/smaller><?/color><?/fontfamily><?fontfamily><?param Arial><?color><?param 0000,0000,8080><?smaller> <o:p></o:p></span></font></p>
<?/smaller><?/color><?/fontfamily></div>
</body>
</html>
*
*
==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of oslist@listserv.boisestate.edu,
Visit:
<p>
http://listserv.boisestate.edu/archives/oslist.html
*
*
==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of oslist@listserv.boisestate.edu,
Visit:
<p>
http://listserv.boisestate.edu/archives/oslist.html