<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>niblettes &#187; resilient</title>
	<atom:link href="http://www.niblettes.com/blog/category/resilient/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.niblettes.com/blog</link>
	<description>Tasty Little Nuggets of Design and Innovation Goodness</description>
	<lastBuildDate>Mon, 13 Dec 2010 19:01:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Resilience</title>
		<link>http://www.niblettes.com/blog/2008/12/22/resilience/</link>
		<comments>http://www.niblettes.com/blog/2008/12/22/resilience/#comments</comments>
		<pubDate>Mon, 22 Dec 2008 21:06:58 +0000</pubDate>
		<dc:creator>niblettes</dc:creator>
				<category><![CDATA[resilient]]></category>

		<guid isPermaLink="false">http://www.niblettes.com/blog/?p=230</guid>
		<description><![CDATA[How much change can a system absorb and still remain viable and functional?  Resilient systems have a high threshold for functioning under change.  The internet is resilient.  It was designed to conitue working during war by instantly rerouting data traffic around damage anywhere in the overall system. The opposite of resilient is brittle.  General Motors is [...]]]></description>
			<content:encoded><![CDATA[<p><img class="inline_image" src="http://www.niblettes.com/blog/wp-images/inline/ants.jpg" alt="" /><br />
How much change can a system absorb and still remain viable and functional? </p>
<p>Resilient systems have a high threshold for functioning under change.  The internet is resilient.  It was designed to conitue working during war by instantly rerouting data traffic around damage anywhere in the overall system.</p>
<p>The opposite of resilient is brittle.  General Motors is brittle.  It is a centrally controlled corporation whose weakest link, its central control and management, is diseased killing the entire system.</p>
<p>To really oversimplify things, here&#8217;s a little free association:</p>
<table class="nib_table" border="0">
<tbody>
<tr>
<th>Brittle</th>
<th>Resilient</th>
</tr>
<tr>
<td>Large parts</td>
<td>Small parts</td>
</tr>
<tr>
<td>Complex parts</td>
<td>Simple parts</td>
</tr>
<tr>
<td>Small quantities</td>
<td>Enormous quanitites</td>
</tr>
<tr>
<td>Co-dependency</td>
<td>Independent interconnectedness</td>
</tr>
<tr>
<td>Specialization</td>
<td>Generalization</td>
</tr>
<tr>
<td>Low redundancy</td>
<td>High redundancy</td>
</tr>
<tr>
<td>Command and control</td>
<td>Evolutionary</td>
</tr>
<tr>
<td>Fewer but more vulnerable links</td>
<td>More but less vulnerable links</td>
</tr>
<tr>
<td>Rigid</td>
<td>Adaptable</td>
</tr>
<tr>
<td>Monolithic</td>
<td>Diverse</td>
</tr>
<tr>
<td>General Motors</td>
<td>The Internet</td>
</tr>
<tr>
<td>A cheetah</td>
<td>An ant colony</td>
</tr>
<tr>
<td>Lions</td>
<td>Hyenas</td>
</tr>
<tr>
<td>Ritual warfare</td>
<td>Guerrila warfare</td>
</tr>
<tr>
<td>Concentration</td>
<td>Distribution</td>
</tr>
<tr>
<td>Complicated</td>
<td>Simple</td>
</tr>
<tr>
<td>Easy short term profits</td>
<td>Long term sustainability</td>
</tr>
</tbody>
</table>
<p>Damage to brittle systems quickly matastasizes acrcoss the entire system leading to catastrophic disruptions and collapse.  Meanwhile resilient systems keep damage localized allowing the entire system to continue functioning normally while things either get repaired or culled.</p>
<p>The scope of our current economic troubles are I think a direct result of global financial systems that have become increasingly brittle over the past many years&#8211;making the entire system extremely vulnerable to what would have otherwise been local fraud and corruption. </p>
<p>Where did this brittleness come from?  Traditional business management sees redundancies as inefficiencies to be rooted out, strives to make small into large economies of scale, and fids distribution freightening due to a lack of control.  </p>
<p>When things are good business can realize greater profit from brittle economies of scale and centralization than it can from resilience.  Of course when thigs go bad and the brittleness shatters, business tries to hold a taxpayer stick-up.  Reach for the sky, suckers!</p>
<p>What does this mean for design?</p>
<p>Well, resilience (even more than simplicity, because it assumes simplicity) should be a primary design priniciple.  The more change our designs can withstand before they collapse the better.  And if that means less short term profits, fine because the long term benefits are greater.</p>
<p>To survive I think we need to leave behind industrial modes of thinking and begin to think small, think simple, think coordinated.</p>
<p>As Schumacher says, small is beautiful beacause that&#8217;s the scale on which we live our lives.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.niblettes.com/blog/2008/12/22/resilience/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Themes: Disposability and Resiliency</title>
		<link>http://www.niblettes.com/blog/2008/12/07/new-themes-disposability-and-resiliency/</link>
		<comments>http://www.niblettes.com/blog/2008/12/07/new-themes-disposability-and-resiliency/#comments</comments>
		<pubDate>Mon, 08 Dec 2008 03:06:35 +0000</pubDate>
		<dc:creator>niblettes</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[disposable]]></category>
		<category><![CDATA[economics]]></category>
		<category><![CDATA[innovation-theory]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[random-thoughts]]></category>
		<category><![CDATA[resilient]]></category>
		<category><![CDATA[strategy]]></category>

		<guid isPermaLink="false">http://www.niblettes.com/blog/?p=224</guid>
		<description><![CDATA[A couple themes have been perculating in my head over the past several months: disposability and resiliency.  While they may seem related, I don&#8217;t intend a connection&#8211;they&#8217;ve just bubbled to the surface at about the same time.  Here is the gist&#8230; 1. Designing disposable experiences may create more value than deeply transformative experiences. 2. Large [...]]]></description>
			<content:encoded><![CDATA[<p><img class="inline_image" src="http://www.niblettes.com/blog/wp-images/inline/disposable_resilient.jpg" alt="" /></p>
<p>A couple themes have been perculating in my head over the past several months: disposability and resiliency.  While they may seem related, I don&#8217;t intend a connection&#8211;they&#8217;ve just bubbled to the surface at about the same time.  Here is the gist&#8230;</p>
<p>1. Designing disposable experiences may create more value than deeply transformative experiences.</p>
<p>2. Large systems are brittle.  Small systems in large volumes are resilient.  We may be at the end of &#8220;economies of scale&#8221; and at the beginning of &#8220;resilient systems&#8221;</p>
<p>Just some stuff to kick around in the old brain pan.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.niblettes.com/blog/2008/12/07/new-themes-disposability-and-resiliency/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

