<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Michael,<br>
<br>
Thank you for your reply. Regarding "unauthorized" or not
formally-authorized OST in organizations, remember, I am framing the
discussion inside the wider context of a typical business
corporation, one trying to improve by considering some changes. I am
not talking about any other context. OST is often used for Agile
retrospectives for example. I am not talking about that.<br>
<br>
So the context for discussion I am suggesting is the context of a
typical business corporation, one trying to improve by considering
some enterprise-wide (or division-wide) changes. A wide-scope
change.<br>
<br>
Typically, these changes are a "push from authority" without respect
to what the people who do the work want, think or feel. Many Agile
frameworks (most notably "SAFe") are implemented in this way. As
push. <br>
<br>
Open Space offers a refreshing alternative to mandates, "push", and
formally authorized coercion. Or so it seems. Since most formally
authorized leaders cannot commit to the so-called "risk of Open
Space," the wide-scope OST usually (almost) never happens.
Meanwhile, everybody knows the issues and that they might never see
the light of day in any kind of formally authorized way. <br>
<br>
Now, getting back your comment, yes: anyone can hold an Open Space
event at any time, about any thing, for any reason. At issue is what
happens next. Perhaps a group can meet to discuss HOW to get some
attention to key issues from formally authorized leaders. Etc. As
you yourself say, "folks knew full well that formal authorization
was needed and had figured out ways addressing that need."<br>
<br>
What I'm really, really interested in is deconstructing OST in
authority terms, and advancing that know-how, so that it can be
reduced to explicit knowledge that others can access quickly in
service to...progress. That essay is my naive attempt to actually
begin the process.<br>
<br>
<br>
Daniel <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/30/15 6:26 AM, Michael M Pannwitz
wrote:<br>
</div>
<blockquote cite="mid:565C3272.7000204@gmail.com" type="cite">Dear
Daniel,
<br>
<br>
somehow, I dont see what has happened in almost all os gatherings
I have facilitated: people deciding to act and actually going
ahead with it after the gathering not being formally authorized.
<br>
As this happened regularly I wondered how those self-authorized
activities fared or got along with formal authorization.
Eventually, I found out that folks knew full well that formal
authorization was needed and had figured out ways addressing that
need.
<br>
<br>
I wondered about Beth. Did she and her group simply suggested
something formal authority should do or was she and others
involved in implementing the stuff they were interested in?
<br>
<br>
Invariably, I as facilitator would intervene with some off-handed
remark about "suggestions" or "recommendations" or what xyz should
do pointing out that there is nothing wrong with that but ....
<br>
<br>
cheers
<br>
mmp
<br>
<br>
On 30.11.2015 12:15, Daniel Mezick via OSList wrote:
<br>
<blockquote type="cite">Hi Koos,
<br>
<br>
Thanks for your comment on personal passion. There's this very
<br>
interesting paper on the various authority types (informal,
formal,
<br>
personal) which is pretty good, I am including it here if you
want to
<br>
check it out.
<br>
<br>
I hear you when you say "I can initiate that process of
authorizing
<br>
myself by taking responsibility for my passion." This is exactly
what we
<br>
hope will happen inside company-sponsored OST events.
<br>
<br>
Within the context of Open Space held in an organization that
wants to
<br>
explore an enterprise-wide change, we can expect the following
to be
<br>
true, if the event is to work well:
<br>
<br>
1. Formally Authorized Leader. A person formally and highly
authorized
<br>
by the organization sends an invite with a theme. This "formally
<br>
authorizes" the time and space for the gathering.
<br>
<br>
2. Proceedings and Intent to Act- with Inclusion. That same
person
<br>
welcomes everyone on event-day, and at the opening, encourages
the
<br>
generation of proceedings, and signals that those proceedings
will be
<br>
inspected and acted upon, not just by the formally authorized
leaders
<br>
(the so-called "higher ups") but also with the new and emerging
leaders
<br>
who have identified themselves during the event ("be prepared to
be
<br>
surprised.") In other words, the people present are being
invited to
<br>
have their say, document it, and expect that these issues are
going be
<br>
input into a formally authorized and inclusive process of
deciding,
<br>
acting, and improving things.
<br>
<br>
<br>
Now, absent these two facts, how "important" is the OST event?
How much
<br>
"action" can ensue?
<br>
<br>
1. Formally Authorized Leader. No formally authorized leader
issuing the
<br>
invite? Or someone /without enough authorization to matter?/ The
signal
<br>
is clear: this theme (and this event) is /not important/ to the
people
<br>
who make the decisions.
<br>
<br>
2. Proceedings and Intent to Act- with Inclusion. Since no one
in the
<br>
room has enough formal authority to implement plans suggested in
the
<br>
proceedings, we can reasonably expect nothing whatsoever to
ensue in
<br>
formal terms after the meeting. This, because people who /could/
do
<br>
something about it (those formally authorized by the
organization) "do
<br>
not care."
<br>
<br>
So- the highly authorized Sponsor (or Host) is essential.
Otherwise, in
<br>
authority terms, the OST event and what happens there just
doesn't
<br>
matter from an organizational point of view. It cannot have much
of an
<br>
impact.
<br>
<br>
Much ado about nothing?
<br>
<br>
<br>
<br>
Here's that paper I mentioned earlier:
<br>
<a class="moz-txt-link-freetext" href="https://www.it.uu.se/edu/course/homepage/projektDV/ht09/BART_Green_Molenkamp.pdf">https://www.it.uu.se/edu/course/homepage/projektDV/ht09/BART_Green_Molenkamp.pdf</a>
<br>
<br>
<br>
<br>
I notice that most people prefer to avoid discussing authority.
Since
<br>
our families are the first place where we encounter this concept
and
<br>
develop our relationship with it, perhaps it is true that
discussing
<br>
authority can be very triggering. Thanks for sticking your neck
out and
<br>
I certainly hope to hear back from you and others on this
thread.
<br>
<br>
Daniel
<br>
<br>
On 11/30/15 12:57 AM, Koos de Heer wrote:
<br>
<blockquote type="cite">
<br>
Hi Daniel,
<br>
<br>
<br>
Thank you for an interesting line of thought. What I am
thinking is
<br>
that there is also the aspect of a person standing up and
speaking for
<br>
a passion that they have (be it in the form of raising a topic
or just
<br>
speaking in a break out session) and in that way claiming
authority.
<br>
In your essay, authority seems to always come from someone
else. And
<br>
of course authority only is there when others believe it to be
there.
<br>
But the initiative to bestow authority on me does not always
come from
<br>
others. I can also initiate that process of authorizing myself
by
<br>
taking responsibility for my passion.
<br>
<br>
Koos
<br>
<br>
*Van:*OSList [<a class="moz-txt-link-freetext" href="mailto:oslist-bounces@lists.openspacetech.org">mailto:oslist-bounces@lists.openspacetech.org</a>]
*Namens
<br>
*Daniel Mezick via OSList
<br>
*V**erzonden:*maandag 30 november 2015 0:13
<br>
*Aan:* <a class="moz-txt-link-abbreviated" href="mailto:oslist@lists.openspacetech.org">oslist@lists.openspacetech.org</a>
<br>
*Onderwerp:* [OSList] What's authority got to do with Open
Space ?
<br>
<br>
What's authority got to do with Open Space ? Apparently
nothing at
<br>
all, at least on the surface...
<br>
<br>
Wait. Once we peek under the surface, what do we actually
find?
<br>
<br>
This completely heretical essay attempts to answer at least
part of
<br>
that question.
<br>
<br>
The context is the use of Open Space in a large business
enterprise,
<br>
convened with intent to explore the potential for making a
very big,
<br>
very complex enterprise-wide change.
<br>
<br>
{Please note, the word "authority" might trigger feelings of:
<br>
/soul-sucking bureaucracy/, unfair and /_illegitimate
leadership
<br>
hierarchy_/, and the like. Some "triggered" readers may want
to
<br>
opt-out of continuing at this time...)
<br>
<br>
Authority Distribution in Open Space:
<br>
<a class="moz-txt-link-freetext" href="http://newtechusa.net/agile/authority-distribution-in-open-space/">http://newtechusa.net/agile/authority-distribution-in-open-space/</a>
<br>
Open Space is a most interesting format for "gathering,", also
known
<br>
as "meeting."
<br>
<br>
What exactly is going on in Open Space?
<br>
<br>
<br>
<br>
--
<br>
Daniel Mezick
<br>
Culture Strategist. Author. Keynoter.
<br>
(203) 915 7248. Bio. <a class="moz-txt-link-rfc2396E" href="http://www.DanielMezick.com/"><http://www.DanielMezick.com/></a>
Blog.
<br>
<a class="moz-txt-link-rfc2396E" href="http://www.NewTechUSA.net/blog/"><http://www.NewTechUSA.net/blog/></a> Twitter.
<br>
<a class="moz-txt-link-rfc2396E" href="https://twitter.com/DanielMezick"><https://twitter.com/DanielMezick></a>
<br>
Book: The Culture Game. <a class="moz-txt-link-rfc2396E" href="http://theculturegame.com/"><http://theculturegame.com/></a>
<br>
Book: The OpenSpace Agility Handbook.
<br>
<a class="moz-txt-link-rfc2396E" href="http://www.amazon.com/OpenSpace-Agility-Handbook-Daniel-Mezick/dp/0984875336"><http://www.amazon.com/OpenSpace-Agility-Handbook-Daniel-Mezick/dp/0984875336></a>
<br>
<br>
<br>
</blockquote>
<br>
--
<br>
Daniel Mezick
<br>
Culture Strategist. Author. Keynoter.
<br>
(203) 915 7248. Bio. <a class="moz-txt-link-rfc2396E" href="http://www.DanielMezick.com/"><http://www.DanielMezick.com/></a> Blog.
<br>
<a class="moz-txt-link-rfc2396E" href="http://www.NewTechUSA.net/blog/"><http://www.NewTechUSA.net/blog/></a> Twitter.
<br>
<a class="moz-txt-link-rfc2396E" href="https://twitter.com/DanielMezick"><https://twitter.com/DanielMezick></a>
<br>
Book: The Culture Game. <a class="moz-txt-link-rfc2396E" href="http://theculturegame.com/"><http://theculturegame.com/></a>
<br>
Book: The OpenSpace Agility Handbook.
<br>
<a class="moz-txt-link-rfc2396E" href="http://www.amazon.com/OpenSpace-Agility-Handbook-Daniel-Mezick/dp/0984875336"><http://www.amazon.com/OpenSpace-Agility-Handbook-Daniel-Mezick/dp/0984875336></a>
<br>
<br>
<br>
<br>
_______________________________________________
<br>
OSList mailing list
<br>
To post send emails to <a class="moz-txt-link-abbreviated" href="mailto:OSList@lists.openspacetech.org">OSList@lists.openspacetech.org</a>
<br>
To unsubscribe send an email to
<a class="moz-txt-link-abbreviated" href="mailto:OSList-leave@lists.openspacetech.org">OSList-leave@lists.openspacetech.org</a>
<br>
To subscribe or manage your subscription click below:
<br>
<a class="moz-txt-link-freetext" href="http://lists.openspacetech.org/listinfo.cgi/oslist-openspacetech.org">http://lists.openspacetech.org/listinfo.cgi/oslist-openspacetech.org</a>
<br>
Past archives can be viewed here:
<a class="moz-txt-link-freetext" href="http://www.mail-archive.com/oslist@lists.openspacetech.org">http://www.mail-archive.com/oslist@lists.openspacetech.org</a>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
Daniel Mezick<br>
Culture Strategist. Author. Keynoter.<br>
(203) 915 7248.
<a href="http://www.DanielMezick.com/"> Bio.</a>
<a href="http://www.NewTechUSA.net/blog/">Blog.</a>
<a href="https://twitter.com/DanielMezick">Twitter.</a>
<br>
Book: <a href="http://theculturegame.com/">The Culture Game.</a>
<br>
Book: <a
href="http://www.amazon.com/OpenSpace-Agility-Handbook-Daniel-Mezick/dp/0984875336">The
OpenSpace Agility Handbook.</a>
<br>
</div>
</body>
</html>