<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The rise of the business anarchist</title>
	<atom:link href="http://sidewise.biz/2009/08/business-anarchist/feed/" rel="self" type="application/rss+xml" />
	<link>http://sidewise.biz/2009/08/business-anarchist/</link>
	<description>A side-wise view of business and the enterprise</description>
	<lastBuildDate>Tue, 19 Jul 2011 18:29:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Enterprise Debt and the Shirky Principle &#124; Developers Blog</title>
		<link>http://sidewise.biz/2009/08/business-anarchist/comment-page-1/#comment-121</link>
		<dc:creator>Enterprise Debt and the Shirky Principle &#124; Developers Blog</dc:creator>
		<pubDate>Tue, 19 Jul 2011 18:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://sidewise.biz/?p=118#comment-121</guid>
		<description>[...] say this is &#8216;political&#8217; is an understatement&#8230;  And unfortunately, by its business-anarchist nature, enterprise-architecture tends to highlight the inherent absurdities of these kinds of [...]</description>
		<content:encoded><![CDATA[<p>[...] say this is &#8216;political&#8217; is an understatement&#8230;  And unfortunately, by its business-anarchist nature, enterprise-architecture tends to highlight the inherent absurdities of these kinds of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aun</title>
		<link>http://sidewise.biz/2009/08/business-anarchist/comment-page-1/#comment-31</link>
		<dc:creator>aun</dc:creator>
		<pubDate>Tue, 01 Sep 2009 13:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://sidewise.biz/?p=118#comment-31</guid>
		<description>We have got all these points bundled and academical founded under the term of &quot;Corporate Entrepreneurship&quot;, don&#039;t we? Anyway I strongly agree that we need coporate entrepreneurs, colleagues with an entrepreneurial mindset who are acting in the borders of an organisation.</description>
		<content:encoded><![CDATA[<p>We have got all these points bundled and academical founded under the term of &#8220;Corporate Entrepreneurship&#8221;, don&#8217;t we? Anyway I strongly agree that we need coporate entrepreneurs, colleagues with an entrepreneurial mindset who are acting in the borders of an organisation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TomG</title>
		<link>http://sidewise.biz/2009/08/business-anarchist/comment-page-1/#comment-28</link>
		<dc:creator>TomG</dc:creator>
		<pubDate>Mon, 24 Aug 2009 15:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://sidewise.biz/?p=118#comment-28</guid>
		<description>Hi Myron - many thanks for comments.

Not surprised this would make sense from an Army perspective, because infantry especially will need to be able to think fast on the fly, keeping the focus on the overall mission whilst adapting tactics to meet often rapidly-changing circumstances. Rigid rule-following was necessary in Roman or Napoleonic times, because the tactics (the line, the square) depended on unity and on interlock; but it&#039;s not a viable tactic in an urban guerilla context. The old Taylorist analytic &#039;scientific management&#039;, with its rigid hierarchies and equally rigid separation between &#039;brain&#039; and &#039;brawn&#039;, does indeed work well for specific tasks (McDonald&#039;s &#039;THE way to clean a floor&quot;) or for a wider context when there is little or no change; but the &#039;anarchist&#039; skillset needs to come more to the fore wherever there are complex conditions and high rates of change. Neither the &#039;analyst&#039; nor the &#039;anarchist&#039; are correct for all circumstances: we need to be able to do either, as appropriate, according to the context. Which means we first need to know &lt;em&gt;what&lt;/em&gt; the context is, &lt;em&gt;how&lt;/em&gt; we use each skillset, and &lt;em&gt;when&lt;/em&gt; and &lt;em&gt;why&lt;/em&gt; we need to switch between them.

On the Cynefin &#039;sense / analyse / respond&#039; etc, perhaps ought to point out that these are selected &lt;em&gt;decision/response&lt;/em&gt; tactics that would be used &lt;em&gt;within&lt;/em&gt; a full process-loop such as John Boyd&#039;s OODA, Deming&#039;s PDCA or the Six-Sigma DMAIC. Follow the link on the Wikipedia page on Cynefin to Dave Snowden&#039;s HBR article for more details on this, or contact Dave direct at &lt;a href=&quot;http://www.cognitive-edge.com&quot; rel=&quot;nofollow&quot;&gt;Cognitive Edge&lt;/a&gt;. (Dave was formerly one of IBM&#039;s leading consultants on knowledge-management - I know he&#039;s worked with US Army and similar groups in the past, if that&#039;s of interest.)

I was intrigued by your comment about &quot;comparing business anarchist, organizational anarchist, and enterprise anarchist&quot;. You&#039;re right, they &lt;em&gt;are&lt;/em&gt; different contexts, with somewhat different skillsets, though what I was focussing more on here was the contrasts between the roles and functions of overall &#039;analyst&#039; and &#039;anarchist&#039; skillsets. As you&#039;ll see from my other weblog ( &lt;a href=&quot;http://weblog.tomgraves.org&quot; rel=&quot;nofollow&quot;&gt;weblog.tomgraves.org&lt;/a&gt; ), my main business focus at present is an extended form of enterprise-architecture that covers the whole enterprise rather solely the enterprise-IT. The &#039;enterprise-anarchist&#039; skillset comes in with common concerns such as applying a business-, performance- or technical-reference model (see FEAF or DODAF) to a real-world context where &#039;the rules&#039; specified by the reference-model need adaptation to be usable in practice. In essence, I regard this aspect of enterprise-architecture and like as a bridge between strategy, operations and risk/opportunity-management - with the former and the latter relying more on the &#039;anarchist&#039;, and operations (or management, at any rate!) probably more preferring the &#039;analyst&#039;.

I also agree strongly with your point about the distinction between &#039;breaking rules&#039; versus &#039;superseding rules&#039; - a subtle but very important distinction. The key anchor here is that the vision (&#039;overall mission of missions&#039; might be an equivalent term in a military context?) provides both the justification and the guiide for any context in which we need to supersede &#039;the rules&#039; of the  &#039;standard operating procedure&#039; or the like. If we bend the rules, we expect to do so &lt;em&gt;with full responsibility&lt;/em&gt;, and also with sufficient reason to show &lt;em&gt;why&lt;/em&gt; we supersede the standard rules.

Much food for thought - many thanks again, anyway.</description>
		<content:encoded><![CDATA[<p>Hi Myron &#8211; many thanks for comments.</p>
<p>Not surprised this would make sense from an Army perspective, because infantry especially will need to be able to think fast on the fly, keeping the focus on the overall mission whilst adapting tactics to meet often rapidly-changing circumstances. Rigid rule-following was necessary in Roman or Napoleonic times, because the tactics (the line, the square) depended on unity and on interlock; but it&#8217;s not a viable tactic in an urban guerilla context. The old Taylorist analytic &#8216;scientific management&#8217;, with its rigid hierarchies and equally rigid separation between &#8216;brain&#8217; and &#8216;brawn&#8217;, does indeed work well for specific tasks (McDonald&#8217;s &#8216;THE way to clean a floor&#8221;) or for a wider context when there is little or no change; but the &#8216;anarchist&#8217; skillset needs to come more to the fore wherever there are complex conditions and high rates of change. Neither the &#8216;analyst&#8217; nor the &#8216;anarchist&#8217; are correct for all circumstances: we need to be able to do either, as appropriate, according to the context. Which means we first need to know <em>what</em> the context is, <em>how</em> we use each skillset, and <em>when</em> and <em>why</em> we need to switch between them.</p>
<p>On the Cynefin &#8216;sense / analyse / respond&#8217; etc, perhaps ought to point out that these are selected <em>decision/response</em> tactics that would be used <em>within</em> a full process-loop such as John Boyd&#8217;s OODA, Deming&#8217;s PDCA or the Six-Sigma DMAIC. Follow the link on the Wikipedia page on Cynefin to Dave Snowden&#8217;s HBR article for more details on this, or contact Dave direct at <a href="http://www.cognitive-edge.com" rel="nofollow">Cognitive Edge</a>. (Dave was formerly one of IBM&#8217;s leading consultants on knowledge-management &#8211; I know he&#8217;s worked with US Army and similar groups in the past, if that&#8217;s of interest.)</p>
<p>I was intrigued by your comment about &#8220;comparing business anarchist, organizational anarchist, and enterprise anarchist&#8221;. You&#8217;re right, they <em>are</em> different contexts, with somewhat different skillsets, though what I was focussing more on here was the contrasts between the roles and functions of overall &#8216;analyst&#8217; and &#8216;anarchist&#8217; skillsets. As you&#8217;ll see from my other weblog ( <a href="http://weblog.tomgraves.org" rel="nofollow">weblog.tomgraves.org</a> ), my main business focus at present is an extended form of enterprise-architecture that covers the whole enterprise rather solely the enterprise-IT. The &#8216;enterprise-anarchist&#8217; skillset comes in with common concerns such as applying a business-, performance- or technical-reference model (see FEAF or DODAF) to a real-world context where &#8216;the rules&#8217; specified by the reference-model need adaptation to be usable in practice. In essence, I regard this aspect of enterprise-architecture and like as a bridge between strategy, operations and risk/opportunity-management &#8211; with the former and the latter relying more on the &#8216;anarchist&#8217;, and operations (or management, at any rate!) probably more preferring the &#8216;analyst&#8217;.</p>
<p>I also agree strongly with your point about the distinction between &#8216;breaking rules&#8217; versus &#8216;superseding rules&#8217; &#8211; a subtle but very important distinction. The key anchor here is that the vision (&#8216;overall mission of missions&#8217; might be an equivalent term in a military context?) provides both the justification and the guiide for any context in which we need to supersede &#8216;the rules&#8217; of the  &#8216;standard operating procedure&#8217; or the like. If we bend the rules, we expect to do so <em>with full responsibility</em>, and also with sufficient reason to show <em>why</em> we supersede the standard rules.</p>
<p>Much food for thought &#8211; many thanks again, anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Myron Chaffee</title>
		<link>http://sidewise.biz/2009/08/business-anarchist/comment-page-1/#comment-27</link>
		<dc:creator>Myron Chaffee</dc:creator>
		<pubDate>Mon, 24 Aug 2009 14:51:02 +0000</pubDate>
		<guid isPermaLink="false">http://sidewise.biz/?p=118#comment-27</guid>
		<description>This is very well written, being thoughtful and organized. It brings clarity to the concept of the business anarchist. It would be interesting to read your thoughts comparing business anarchist, organizational anarchist, and enterprise anarchist.

Of Michelle Tripp&#039;s six skills, I concur completely - however, I would like to build upon skill #1. Instead of breaking rules, I would prefer superseding rules. This is important to bring out a focus on the actual concern. The concern would be upon that which is created such that that which is superseded is demonstrated as such. Interestingly, the superseding state obtained is gained though the exercise of the other five skills. What really intrigued me was the discussion of sense/ analyze/ respond. There are several of these types of process outlines. However, I find John Boyd&#039;s OODA loop (observe/ orient/ decide/ act) to be most compelling due to its mathematical foundation and its demonstrated truth. I say truth, because a true anarchist enjoys heresy. I end with the following links - good places to start looking into this, if you wish:
 
http://www.goalsys.com/books/documents/DESTRUCTION_AND_CREATION.pdf
http://en.wikipedia.org/wiki/John_Boyd_(military_strategist)</description>
		<content:encoded><![CDATA[<p>This is very well written, being thoughtful and organized. It brings clarity to the concept of the business anarchist. It would be interesting to read your thoughts comparing business anarchist, organizational anarchist, and enterprise anarchist.</p>
<p>Of Michelle Tripp&#8217;s six skills, I concur completely &#8211; however, I would like to build upon skill #1. Instead of breaking rules, I would prefer superseding rules. This is important to bring out a focus on the actual concern. The concern would be upon that which is created such that that which is superseded is demonstrated as such. Interestingly, the superseding state obtained is gained though the exercise of the other five skills. What really intrigued me was the discussion of sense/ analyze/ respond. There are several of these types of process outlines. However, I find John Boyd&#8217;s OODA loop (observe/ orient/ decide/ act) to be most compelling due to its mathematical foundation and its demonstrated truth. I say truth, because a true anarchist enjoys heresy. I end with the following links &#8211; good places to start looking into this, if you wish:</p>
<p><a href="http://www.goalsys.com/books/documents/DESTRUCTION_AND_CREATION.pdf" rel="nofollow">http://www.goalsys.com/books/documents/DESTRUCTION_AND_CREATION.pdf</a><br />
<a href="http://en.wikipedia.org/wiki/John_Boyd_(military_strategist)" rel="nofollow">http://en.wikipedia.org/wiki/John_Boyd_(military_strategist)</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

