<?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: Silos and the art of Empirical Theology</title>
	<atom:link href="http://www.ribbonfarm.com/2007/07/08/silos-and-the-art-of-empirical-theology/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ribbonfarm.com/2007/07/08/silos-and-the-art-of-empirical-theology/</link>
	<description>experiments in refactored perception</description>
	<lastBuildDate>Wed, 08 Feb 2012 03:00:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Venkat</title>
		<link>http://www.ribbonfarm.com/2007/07/08/silos-and-the-art-of-empirical-theology/#comment-242</link>
		<dc:creator>Venkat</dc:creator>
		<pubDate>Mon, 16 Jul 2007 01:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.ribbonfarm.com/2007/07/08/silos-and-the-art-of-empirical-theology/#comment-242</guid>
		<description>Well, most departments are also silos, yes. But in matrix organizations (which I&#039;ll talk about next in this theme), it is not clear how process and departmental structure interact.

But if you ignore terminology and just think of &quot;units that develop an internal language, play in an internal economy and can have communication problems,&quot; that picks out the object of my discussion. So no, I don&#039;t think I am overstating the silo concept.

If new departments are created specifically to fill gaps, they just create new gaps. I am not convinced there are global gains to putting new &quot;interdisciplinary&quot; functions somewhere UNLESS you destroy some departments as well.

Essentially the only way to globally rationalize an organization is to refactor it the way s/w engineers refactor software. I&#039;ve seen/heard of that done a few times, so it can be done. Kinda the intra-economy equivalent of declaring a couple of monopolies to clean up the chaos.</description>
		<content:encoded><![CDATA[<p>Well, most departments are also silos, yes. But in matrix organizations (which I&#8217;ll talk about next in this theme), it is not clear how process and departmental structure interact.</p>
<p>But if you ignore terminology and just think of &#8220;units that develop an internal language, play in an internal economy and can have communication problems,&#8221; that picks out the object of my discussion. So no, I don&#8217;t think I am overstating the silo concept.</p>
<p>If new departments are created specifically to fill gaps, they just create new gaps. I am not convinced there are global gains to putting new &#8220;interdisciplinary&#8221; functions somewhere UNLESS you destroy some departments as well.</p>
<p>Essentially the only way to globally rationalize an organization is to refactor it the way s/w engineers refactor software. I&#8217;ve seen/heard of that done a few times, so it can be done. Kinda the intra-economy equivalent of declaring a couple of monopolies to clean up the chaos.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Torp</title>
		<link>http://www.ribbonfarm.com/2007/07/08/silos-and-the-art-of-empirical-theology/#comment-239</link>
		<dc:creator>Torp</dc:creator>
		<pubDate>Sun, 15 Jul 2007 20:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.ribbonfarm.com/2007/07/08/silos-and-the-art-of-empirical-theology/#comment-239</guid>
		<description>Whew! I ran out of breath reading through, and could not keep the whole thing in my head coherently. Taking a step back... I am forced to ask... what is the real difference between &quot;silo&quot; as you like to call it, and the concept of a &quot;department&quot; that all general managers recognize. A department is MEANT to be self-interested, coherently focused on one mission (which maybe different from the mission of the overall organization, but is FULL WELL expected to contriibute to creating more shareholder value, even if it erodes value creation in sister departments). IN fact - the only reason a new department is EVER created, is to generate more focus and energy on an issue that would &quot;fall between the cracks&quot; if it were left in the purview of other departments. So a department creates some siloing.. and is done in a desirable situation. Of course, down the line a department accretes its own management, becomes a fiefdom, may underperform both on its own local goal and its more global corporate role... but that is how human organizations work. CEOs are EXPECTED to break through this quagmire, and get everyone on the same page, by making tradeoffs at a corporate level that may displease individual departments. Are we overstating the &quot;silo&quot; concept?</description>
		<content:encoded><![CDATA[<p>Whew! I ran out of breath reading through, and could not keep the whole thing in my head coherently. Taking a step back&#8230; I am forced to ask&#8230; what is the real difference between &#8220;silo&#8221; as you like to call it, and the concept of a &#8220;department&#8221; that all general managers recognize. A department is MEANT to be self-interested, coherently focused on one mission (which maybe different from the mission of the overall organization, but is FULL WELL expected to contriibute to creating more shareholder value, even if it erodes value creation in sister departments). IN fact &#8211; the only reason a new department is EVER created, is to generate more focus and energy on an issue that would &#8220;fall between the cracks&#8221; if it were left in the purview of other departments. So a department creates some siloing.. and is done in a desirable situation. Of course, down the line a department accretes its own management, becomes a fiefdom, may underperform both on its own local goal and its more global corporate role&#8230; but that is how human organizations work. CEOs are EXPECTED to break through this quagmire, and get everyone on the same page, by making tradeoffs at a corporate level that may displease individual departments. Are we overstating the &#8220;silo&#8221; concept?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

