<?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: Musing about collective intelligence and Agile and complex systems problems</title>
	<atom:link href="http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/</link>
	<description>a blog about information</description>
	<lastBuildDate>Fri, 19 Mar 2010 09:20:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jacob Jesson</title>
		<link>http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/comment-page-1/#comment-147088</link>
		<dc:creator>Jacob Jesson</dc:creator>
		<pubDate>Thu, 14 Jun 2007 16:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/#comment-147088</guid>
		<description>Excellent post, thank you!  About the same time you met with Doug Engelbart, I was in Cambridge for a session at the New England Complex Systems Institute.  Two of MIT&#039;s finest business minds were there, Peter Senge and John Sterman.  Yaneer Bar-Yam led the session.  The presentations and discussions focused on how to apply complex systems thinking in a business context.  The concept of evolutionary processes, or in the case of IT, evolutionary engineering were front and center.   Your post, and the following comments, are spot on in so many ways.

A significant challenge I face in my practice is finding a means for large and established organizations to transform into a more evolutionary type business and IT model.  Newer and smaller organizations have the benefit of either starting off &quot;correctly&quot; or transforming quickly due to their small size.  I firmly believe that the transformative process for larger organizations is an evolutionary process as well.  

I agree with Doug that the whole structure should be considered.  Too often though, the complexity of the whole structure is used as a justification for why the whole structure is too big to consider.  I think that the &quot;too big to consider&quot; argument assumes that a firm control structure must be in place and thus all of the variables must be closely managed.  Clearly this is impossible.  As Doug points out, this type of control thinking is what is causing the problem in the first place.  So, it is in this context that the transformative process must also incorporate the same concepts as the &quot;agile&quot; environment we seek.</description>
		<content:encoded><![CDATA[<p>Excellent post, thank you!  About the same time you met with Doug Engelbart, I was in Cambridge for a session at the New England Complex Systems Institute.  Two of MIT&#8217;s finest business minds were there, Peter Senge and John Sterman.  Yaneer Bar-Yam led the session.  The presentations and discussions focused on how to apply complex systems thinking in a business context.  The concept of evolutionary processes, or in the case of IT, evolutionary engineering were front and center.   Your post, and the following comments, are spot on in so many ways.</p>
<p>A significant challenge I face in my practice is finding a means for large and established organizations to transform into a more evolutionary type business and IT model.  Newer and smaller organizations have the benefit of either starting off &#8220;correctly&#8221; or transforming quickly due to their small size.  I firmly believe that the transformative process for larger organizations is an evolutionary process as well.  </p>
<p>I agree with Doug that the whole structure should be considered.  Too often though, the complexity of the whole structure is used as a justification for why the whole structure is too big to consider.  I think that the &#8220;too big to consider&#8221; argument assumes that a firm control structure must be in place and thus all of the variables must be closely managed.  Clearly this is impossible.  As Doug points out, this type of control thinking is what is causing the problem in the first place.  So, it is in this context that the transformative process must also incorporate the same concepts as the &#8220;agile&#8221; environment we seek.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Lucas</title>
		<link>http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/comment-page-1/#comment-142866</link>
		<dc:creator>Bob Lucas</dc:creator>
		<pubDate>Tue, 05 Jun 2007 16:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/#comment-142866</guid>
		<description>I have come to a very similar conclusion via my experience  with the US DOD environment and it&#039;s forced expansion of it area of responsibilities due to current events.

The world is so large and complex that we need to evolve a living organism model where we bring together smart and experienced people and support them with rapid access to whatever knowledge base required.   Let them rapidly consider different options in an iterative process so they can evolve optimal solutions and react/adjust in agile manner to the changing environment.</description>
		<content:encoded><![CDATA[<p>I have come to a very similar conclusion via my experience  with the US DOD environment and it&#8217;s forced expansion of it area of responsibilities due to current events.</p>
<p>The world is so large and complex that we need to evolve a living organism model where we bring together smart and experienced people and support them with rapid access to whatever knowledge base required.   Let them rapidly consider different options in an iterative process so they can evolve optimal solutions and react/adjust in agile manner to the changing environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Smoliar</title>
		<link>http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/comment-page-1/#comment-136649</link>
		<dc:creator>Stephen Smoliar</dc:creator>
		<pubDate>Thu, 24 May 2007 17:16:44 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/#comment-136649</guid>
		<description>I worry that all this talk about fractals amounts to a rehash of Haeckel&#039;s theory of recapitulation (&quot;ontogeny recapituaaltes phylogeny&quot;) seen through the lenses of Mandelbrot&#039;s &quot;fractal geometry of nature&quot; and mapped over to &quot;organic organizations!&quot;  I prefer to put my money on Giddens&#039; structuration theory.  This assumes a dialectical relationship between the STRUCTURES of rules and resources in any social organization and the &quot;regular social practices&quot; that actually take place around those rules and resources.  Giddens is less interested in the question of whether an organization should be hierarchical and more interested in how to REPRODUCE successful engagements between structures and practices.</description>
		<content:encoded><![CDATA[<p>I worry that all this talk about fractals amounts to a rehash of Haeckel&#8217;s theory of recapitulation (&#8220;ontogeny recapituaaltes phylogeny&#8221;) seen through the lenses of Mandelbrot&#8217;s &#8220;fractal geometry of nature&#8221; and mapped over to &#8220;organic organizations!&#8221;  I prefer to put my money on Giddens&#8217; structuration theory.  This assumes a dialectical relationship between the STRUCTURES of rules and resources in any social organization and the &#8220;regular social practices&#8221; that actually take place around those rules and resources.  Giddens is less interested in the question of whether an organization should be hierarchical and more interested in how to REPRODUCE successful engagements between structures and practices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug</title>
		<link>http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/comment-page-1/#comment-136628</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Thu, 24 May 2007 16:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2007/05/23/musing-about-collective-intelligence-and-agile-and-complex-systems-problems/#comment-136628</guid>
		<description>JP,
My recent reading has been in and around Corporate Democracy. This relates to all you are saying about an Agile and fractal nature of an organization. 
Some related links:
http://www.gbn.com/BookClubSelectionDisplayServlet.srv?si=69
http://www.designnine.com/library/docs/other_papers/Democratic_Company.pdf
and http://worldblu.com/ although this site has not been updated for a while.

These ideas and what you have said in this post are swimming in a mixup in my brain. I would love to have some discussion to help put them in order.

The organization should not be de-fractalised. It needs to embrace the Agile and open methods. By changing the basic organization from a management hierarchy, into smaller groups making decisions, and putting the power at the edges of the network all the benefits of the Agile methods are available. 
The issue is really about the people with power giving up control and trusting that the folks on the edges know what they are doing. The same issue keeps corporate CIOs from using OSS. They don&#039;t have someone to blame, another form of control.
The discussion needs to be wider than just using OSS or Agile methods. The whole structure of the organization should be considered.</description>
		<content:encoded><![CDATA[<p>JP,<br />
My recent reading has been in and around Corporate Democracy. This relates to all you are saying about an Agile and fractal nature of an organization.<br />
Some related links:<br />
<a href="http://www.gbn.com/BookClubSelectionDisplayServlet.srv?si=69" rel="nofollow">http://www.gbn.com/BookClubSelectionDisplayServlet.srv?si=69</a><br />
<a href="http://www.designnine.com/library/docs/other_papers/Democratic_Company.pdf" rel="nofollow">http://www.designnine.com/library/docs/other_papers/Democratic_Company.pdf</a><br />
and <a href="http://worldblu.com/" rel="nofollow">http://worldblu.com/</a> although this site has not been updated for a while.</p>
<p>These ideas and what you have said in this post are swimming in a mixup in my brain. I would love to have some discussion to help put them in order.</p>
<p>The organization should not be de-fractalised. It needs to embrace the Agile and open methods. By changing the basic organization from a management hierarchy, into smaller groups making decisions, and putting the power at the edges of the network all the benefits of the Agile methods are available.<br />
The issue is really about the people with power giving up control and trusting that the folks on the edges know what they are doing. The same issue keeps corporate CIOs from using OSS. They don&#8217;t have someone to blame, another form of control.<br />
The discussion needs to be wider than just using OSS or Agile methods. The whole structure of the organization should be considered.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
