<?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"
	>
<channel>
	<title>Comments on: Your grandmother, the innovator, and second-order innovation</title>
	<atom:link href="http://www.sitsite.com/blog/2008/06/your-grandmother-the-innovator-and-second-order-innovation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitsite.com/blog/2008/06/your-grandmother-the-innovator-and-second-order-innovation/</link>
	<description></description>
	<pubDate>Thu, 17 May 2012 14:22:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Amnon Levav</title>
		<link>http://www.sitsite.com/blog/2008/06/your-grandmother-the-innovator-and-second-order-innovation/#comment-25</link>
		<dc:creator>Amnon Levav</dc:creator>
		<pubDate>Thu, 10 Jul 2008 02:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://breakingfixedness.easycgi.com/?p=37#comment-25</guid>
		<description>hola Fabian,

I agree. actuall, it is probably most useful to always combine the two, meaning, think about what you want to do and at the same time how, and let the how afeect the what.
Amnon</description>
		<content:encoded><![CDATA[<p>hola Fabian,</p>
<p>I agree. actuall, it is probably most useful to always combine the two, meaning, think about what you want to do and at the same time how, and let the how afeect the what.<br />
Amnon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fabian Szulanski</title>
		<link>http://www.sitsite.com/blog/2008/06/your-grandmother-the-innovator-and-second-order-innovation/#comment-21</link>
		<dc:creator>Fabian Szulanski</dc:creator>
		<pubDate>Sun, 06 Jul 2008 13:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://breakingfixedness.easycgi.com/?p=37#comment-21</guid>
		<description>Hi Amnon,

Let me add some twist in here.

In change processes, second order innovation could be (and I'm aware of many cases that have been done this way) ideated, designed and performed first. 

In that way, cultural change would preceed the "what" change, and it would prevent the "what" initiative to be considered "the flavor of the month" and the consequent archiving and non implementation.

Of course that the customer should be permeable to buy in this idea, which requires a longer time (and more money) investment as compared with ideating, designing and implementing the "what".

Saludos,

Fabian Szulanski</description>
		<content:encoded><![CDATA[<p>Hi Amnon,</p>
<p>Let me add some twist in here.</p>
<p>In change processes, second order innovation could be (and I&#8217;m aware of many cases that have been done this way) ideated, designed and performed first. </p>
<p>In that way, cultural change would preceed the &#8220;what&#8221; change, and it would prevent the &#8220;what&#8221; initiative to be considered &#8220;the flavor of the month&#8221; and the consequent archiving and non implementation.</p>
<p>Of course that the customer should be permeable to buy in this idea, which requires a longer time (and more money) investment as compared with ideating, designing and implementing the &#8220;what&#8221;.</p>
<p>Saludos,</p>
<p>Fabian Szulanski</p>
]]></content:encoded>
	</item>
</channel>
</rss>

