<?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: Is improv the key to innovative teams?</title>
	<atom:link href="http://edgehopper.com/improv-the-key-to-innovation/feed/" rel="self" type="application/rss+xml" />
	<link>http://edgehopper.com/improv-the-key-to-innovation/</link>
	<description>Tales from the Edge of Technology</description>
	<lastBuildDate>Wed, 17 Feb 2010 17:06:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: How do we find game-changing strategies? &#124; Game-Changer</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-3049</link>
		<dc:creator>How do we find game-changing strategies? &#124; Game-Changer</dc:creator>
		<pubDate>Sat, 28 Nov 2009 06:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-3049</guid>
		<description>[...] It could’ve come from a major brainstorming session to spot game-changing ideas but most often game-changing strategy comes from an improvisational approach. [...]</description>
		<content:encoded><![CDATA[<p>[...] It could’ve come from a major brainstorming session to spot game-changing ideas but most often game-changing strategy comes from an improvisational approach. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Marino</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2679</link>
		<dc:creator>Joseph Marino</dc:creator>
		<pubDate>Thu, 12 Mar 2009 01:33:30 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2679</guid>
		<description>What exactly is meant by #8? Isn&#039;t it a good idea to do thorough analysis and approach any new idea with a full understanding of the downstream effects? I guess I come from a more analytical background and would be interested in hearing others&#039; thoughts on whether you can do proper analysis and still remain &quot;agile&quot;</description>
		<content:encoded><![CDATA[<p>What exactly is meant by #8? Isn&#8217;t it a good idea to do thorough analysis and approach any new idea with a full understanding of the downstream effects? I guess I come from a more analytical background and would be interested in hearing others&#8217; thoughts on whether you can do proper analysis and still remain &#8220;agile&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Sutton</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2676</link>
		<dc:creator>Mike Sutton</dc:creator>
		<pubDate>Wed, 11 Mar 2009 21:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2676</guid>
		<description>Chris you make an awesome point and you make it brilliantly and simply. Agile (IMHO) has forced us to confront what has always been the case - that software creation is an intensely creative process and its main ingredient is people. We now have to figure out how to help people collaborate in a creative and respectful way and I beleive improv is a vital part of this mental reeducation. Rock on.</description>
		<content:encoded><![CDATA[<p>Chris you make an awesome point and you make it brilliantly and simply. Agile (IMHO) has forced us to confront what has always been the case &#8211; that software creation is an intensely creative process and its main ingredient is people. We now have to figure out how to help people collaborate in a creative and respectful way and I beleive improv is a vital part of this mental reeducation. Rock on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael James</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2609</link>
		<dc:creator>Michael James</dc:creator>
		<pubDate>Thu, 05 Mar 2009 03:24:32 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2609</guid>
		<description>Yes, thanks for bringing this up. Theater improv directly exercises the skills we expect from high performing development teams. I&#039;ve been using elements of this when teaching Scrum to teams, and feel they&#039;d benefit from a lot more. Tobias Mayer and Matt Smith (the boss in the film &quot;Outsourced&quot;) are also doing work on this. 
 
 --mj</description>
		<content:encoded><![CDATA[<p>Yes, thanks for bringing this up. Theater improv directly exercises the skills we expect from high performing development teams. I&#8217;ve been using elements of this when teaching Scrum to teams, and feel they&#8217;d benefit from a lot more. Tobias Mayer and Matt Smith (the boss in the film &#8220;Outsourced&#8221;) are also doing work on this. </p>
<p> &#8211;mj</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: svilen dobrev</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2605</link>
		<dc:creator>svilen dobrev</dc:creator>
		<pubDate>Wed, 04 Mar 2009 18:37:34 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2605</guid>
		<description>except 1) about accepting anything, and the part saying that analyzis is bad, i think this is it.

IMO current (mental) crisis is about sitting too long on same brick in same pose, doing same things, specializing so narrow that it&#039;s close to nothing.
One has to be human, to move, improvise and error if it comes that way. Otherwise it&#039;s a dehumanizing 9-to-5 ticking clockwork. 
</description>
		<content:encoded><![CDATA[<p>except 1) about accepting anything, and the part saying that analyzis is bad, i think this is it.</p>
<p>IMO current (mental) crisis is about sitting too long on same brick in same pose, doing same things, specializing so narrow that it&#8217;s close to nothing.<br />
One has to be human, to move, improvise and error if it comes that way. Otherwise it&#8217;s a dehumanizing 9-to-5 ticking clockwork.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Martens</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2588</link>
		<dc:creator>Ryan Martens</dc:creator>
		<pubDate>Tue, 03 Mar 2009 13:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2588</guid>
		<description>Michael Bolton was good to link in Lee Devin&#039;s work.  Lee also has a paper on &quot;Planning to get lucky.&quot;  (&lt;a href=&quot;http://agilecommons.org/posts/6877a14060/comments&quot; rel=&quot;nofollow&quot;&gt;See related post in Agile Commons&lt;/a&gt;.)I think it is the combination of bottom-up improve plus a planning paradigm that keeps you from deciding on point-based designs too early that can combine to really drive innovation.  XP and 37Signals team would tell you to do the simplest thing and have the architecture emerge.  In large complex systems, that is a very hard concept to get across.  You have to have some way to open the space and mind to do improve.  I would like to collaborate with you this missing aspect to &quot;Innovation.&quot;</description>
		<content:encoded><![CDATA[<p>Michael Bolton was good to link in Lee Devin&#8217;s work.  Lee also has a paper on &#8220;Planning to get lucky.&#8221;  (<a href="http://agilecommons.org/posts/6877a14060/comments" rel="nofollow">See related post in Agile Commons</a>.)I think it is the combination of bottom-up improve plus a planning paradigm that keeps you from deciding on point-based designs too early that can combine to really drive innovation.  XP and 37Signals team would tell you to do the simplest thing and have the architecture emerge.  In large complex systems, that is a very hard concept to get across.  You have to have some way to open the space and mind to do improve.  I would like to collaborate with you this missing aspect to &#8220;Innovation.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fay Simcock</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2592</link>
		<dc:creator>Fay Simcock</dc:creator>
		<pubDate>Tue, 03 Mar 2009 11:45:50 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2592</guid>
		<description>My experience of improv is, like Dan&#039;s, not recent (in fact, from my student days) and I quickly learned that I was better behind the stage than in the footlights. But one thing I did learn could maybe be added to Chris&#039; list: for me the best approach was just to get on and do it and not sit on the sidelines and worry all the time about what the others would think. It&#039;s partly in Chris&#039; risk taking but it&#039;s also that doing adds value, if you just sit and agonize until the idea is clear or perfect, you&#039;re likely to be too late and the idea will need to be modified anyway.</description>
		<content:encoded><![CDATA[<p>My experience of improv is, like Dan&#8217;s, not recent (in fact, from my student days) and I quickly learned that I was better behind the stage than in the footlights. But one thing I did learn could maybe be added to Chris&#8217; list: for me the best approach was just to get on and do it and not sit on the sidelines and worry all the time about what the others would think. It&#8217;s partly in Chris&#8217; risk taking but it&#8217;s also that doing adds value, if you just sit and agonize until the idea is clear or perfect, you&#8217;re likely to be too late and the idea will need to be modified anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Lam</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2591</link>
		<dc:creator>Simon Lam</dc:creator>
		<pubDate>Tue, 03 Mar 2009 09:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2591</guid>
		<description>The context of improv in which decisions are made is often more political than technical. And the commonality solutions are most effective.</description>
		<content:encoded><![CDATA[<p>The context of improv in which decisions are made is often more political than technical. And the commonality solutions are most effective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Heffner</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2590</link>
		<dc:creator>Stephen Heffner</dc:creator>
		<pubDate>Tue, 03 Mar 2009 08:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2590</guid>
		<description>1. This puts you at the mercy of anyone who makes an offer. Many such offers will be wastes of time; some may be extremely valuable. Judging which is which is a matter of skill, experience, and of course some luck. But judge you must. 
 
2. I&#039;d rather say &quot;Make the team look good.&quot; That way you avoid questions of who looks better than whom. See comments below about ego. 
 
3. A non-sequitur? I agree with both sentiments, but I don&#039;t see how they&#039;re directly connected. If you question what works because you don&#039;t think it works well enough, that can be a good thing. If you do so because you don&#039;t think it will result in perfection, then the 2nd sentiment comes into play. 
 
4. Absolutely! But again, you must judge which risks to take. Too many, or the wrong ones, and you&#039;re needlessly reckless. Too few, and you&#039;re stuck in a rut. It&#039;s not an &quot;all or nothing&quot; or &quot;either/or&quot; proposition. 
 
IMHO, one secret of innovation (and, in fact of genius) is in seeing things in a different way. This is independent of taking risks, except that you risk being laughed at or derided. 
 
5. That&#039;s a good idea if what is said is profound and what happens is at least slightly momentous. Being changed by trivial utterances and happenings makes you fickle, weak, and easily manipulated. 
 
6. Yes! Communication and flexibility, respectively. But again, too much flexibility results in a failure of leadership. It&#039;s a judgment call. Too much communication bogs you down and means you don&#039;t trust your colleagues to do things right, so you can&#039;t delegate and wind up micromanaging. 
 
 7. No caveats on this one -- I heartily agree.  Be alive and focused! 
 
8. Of course you must analyze, in fact even more so when things are in flux; otherwise you become a victim of events, carried on the tide like flotsam. 
 
When you come to a branch in the road, &quot;keep moving forward&quot; just doesn&#039;t cut it. You must decide, and you&#039;d probably better take some time to do so, to ensure the best possible decision in the circumstances. 
 
And since when is analysis the enemy of creativity? Good analysis begets creativity! It&#039;s over-analysis that paralyzes and feeds into the perfect being the enemy of the good. 
 
9. I agree wholeheartedly. The most productive people I&#039;ve ever known combined craftsmanship at the detail level with a comprehensive understanding of the &quot;big picture&quot;. That&#039;s a powerful combination, but it&#039;s hard to find. 
 
10. Agreed again (barring OCD...). If you&#039;re not well organized, especially mentally, you can&#039;t create, or participate effectively in, a plan with others. 
 
 &gt; It emerged naturally on a team full of incredible talent with no egos... 
 
I disagree with this, as I did with the &quot;ego-less programming&quot; fad of years ago. Egos are a fact of human nature, and they support individuality. The trick is to engage your ego in the success of the team, so it serves the common goal. You can still express your individuality, but at a higher level of abstraction, so you don&#039;t insist on &quot;your way&quot; at the detail level where it really doesn&#039;t matter. 
 
One way to summarize that is &quot;what&#039;s right, not who&#039;s right&quot;. A healthy ego can handle being wrong, and can get satisfaction from its contribution to the team when it&#039;s right. 
 
Many of these questions are profound and strike at the heart of human nature, sociology, and politics. Please take my comments in the spirit in which I offer them, as a modest attempt to address these thorny issues.</description>
		<content:encoded><![CDATA[<p>1. This puts you at the mercy of anyone who makes an offer. Many such offers will be wastes of time; some may be extremely valuable. Judging which is which is a matter of skill, experience, and of course some luck. But judge you must. </p>
<p>2. I&#8217;d rather say &#8220;Make the team look good.&#8221; That way you avoid questions of who looks better than whom. See comments below about ego. </p>
<p>3. A non-sequitur? I agree with both sentiments, but I don&#8217;t see how they&#8217;re directly connected. If you question what works because you don&#8217;t think it works well enough, that can be a good thing. If you do so because you don&#8217;t think it will result in perfection, then the 2nd sentiment comes into play. </p>
<p>4. Absolutely! But again, you must judge which risks to take. Too many, or the wrong ones, and you&#8217;re needlessly reckless. Too few, and you&#8217;re stuck in a rut. It&#8217;s not an &#8220;all or nothing&#8221; or &#8220;either/or&#8221; proposition. </p>
<p>IMHO, one secret of innovation (and, in fact of genius) is in seeing things in a different way. This is independent of taking risks, except that you risk being laughed at or derided. </p>
<p>5. That&#8217;s a good idea if what is said is profound and what happens is at least slightly momentous. Being changed by trivial utterances and happenings makes you fickle, weak, and easily manipulated. </p>
<p>6. Yes! Communication and flexibility, respectively. But again, too much flexibility results in a failure of leadership. It&#8217;s a judgment call. Too much communication bogs you down and means you don&#8217;t trust your colleagues to do things right, so you can&#8217;t delegate and wind up micromanaging. </p>
<p> 7. No caveats on this one &#8212; I heartily agree.  Be alive and focused! </p>
<p>8. Of course you must analyze, in fact even more so when things are in flux; otherwise you become a victim of events, carried on the tide like flotsam. </p>
<p>When you come to a branch in the road, &#8220;keep moving forward&#8221; just doesn&#8217;t cut it. You must decide, and you&#8217;d probably better take some time to do so, to ensure the best possible decision in the circumstances. </p>
<p>And since when is analysis the enemy of creativity? Good analysis begets creativity! It&#8217;s over-analysis that paralyzes and feeds into the perfect being the enemy of the good. </p>
<p>9. I agree wholeheartedly. The most productive people I&#8217;ve ever known combined craftsmanship at the detail level with a comprehensive understanding of the &#8220;big picture&#8221;. That&#8217;s a powerful combination, but it&#8217;s hard to find. </p>
<p>10. Agreed again (barring OCD&#8230;). If you&#8217;re not well organized, especially mentally, you can&#8217;t create, or participate effectively in, a plan with others. </p>
<p> &gt; It emerged naturally on a team full of incredible talent with no egos&#8230; </p>
<p>I disagree with this, as I did with the &#8220;ego-less programming&#8221; fad of years ago. Egos are a fact of human nature, and they support individuality. The trick is to engage your ego in the success of the team, so it serves the common goal. You can still express your individuality, but at a higher level of abstraction, so you don&#8217;t insist on &#8220;your way&#8221; at the detail level where it really doesn&#8217;t matter. </p>
<p>One way to summarize that is &#8220;what&#8217;s right, not who&#8217;s right&#8221;. A healthy ego can handle being wrong, and can get satisfaction from its contribution to the team when it&#8217;s right. </p>
<p>Many of these questions are profound and strike at the heart of human nature, sociology, and politics. Please take my comments in the spirit in which I offer them, as a modest attempt to address these thorny issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Dawson</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2589</link>
		<dc:creator>Thomas Dawson</dc:creator>
		<pubDate>Tue, 03 Mar 2009 02:21:27 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2589</guid>
		<description>11. Don&#039;t be afraid to mold the process to fit the project. Improv applies to process as much as anything else.

12. A team that trusts each other is far more productive than one where people don&#039;t.</description>
		<content:encoded><![CDATA[<p>11. Don&#8217;t be afraid to mold the process to fit the project. Improv applies to process as much as anything else.</p>
<p>12. A team that trusts each other is far more productive than one where people don&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcos Orozco</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2583</link>
		<dc:creator>Marcos Orozco</dc:creator>
		<pubDate>Tue, 03 Mar 2009 00:38:29 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2583</guid>
		<description>From this perspective, I totally agree with you Dan</description>
		<content:encoded><![CDATA[<p>From this perspective, I totally agree with you Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bil Sherrin</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2580</link>
		<dc:creator>Bil Sherrin</dc:creator>
		<pubDate>Mon, 02 Mar 2009 22:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2580</guid>
		<description>As someone who has performed the comedy (well, ok, sometimes not so much) kind of improv off and on in 4 different cities since 1993... I could not agree more. Great thoughts, Chris. On a professional level, I think this is why I love Agile programming and having business and IT folk co-located during development. B I L</description>
		<content:encoded><![CDATA[<p>As someone who has performed the comedy (well, ok, sometimes not so much) kind of improv off and on in 4 different cities since 1993&#8230; I could not agree more. Great thoughts, Chris. On a professional level, I think this is why I love Agile programming and having business and IT folk co-located during development. B I L</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is improv the key to innovative teams? &#171; THEMdidit</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2579</link>
		<dc:creator>Is improv the key to innovative teams? &#171; THEMdidit</dc:creator>
		<pubDate>Mon, 02 Mar 2009 22:31:17 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2579</guid>
		<description>[...] is reposted with permission from Chris Spagnuolo. The original post can be found here.          0 [...]</description>
		<content:encoded><![CDATA[<p>[...] is reposted with permission from Chris Spagnuolo. The original post can be found here.          0 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Valade</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2578</link>
		<dc:creator>Roger Valade</dc:creator>
		<pubDate>Mon, 02 Mar 2009 22:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2578</guid>
		<description>Very interesting. I saw John Sweeney at a local tech conference and his presentation made me think along these same lines. Check out his site / book at &lt;a href=&quot;http://www.speedoflaughter.com&quot; rel=&quot;nofollow&quot;&gt;http://www.speedoflaughter.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Very interesting. I saw John Sweeney at a local tech conference and his presentation made me think along these same lines. Check out his site / book at <a href="http://www.speedoflaughter.com" rel="nofollow">http://www.speedoflaughter.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Bolton</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2577</link>
		<dc:creator>Michael Bolton</dc:creator>
		<pubDate>Mon, 02 Mar 2009 21:44:29 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2577</guid>
		<description>You might have enjoyed the presentation I did last year with Adam White and Adam Geras at Agile 2008. You might also have enjoyed even more Lee Devin&#039;s session, and his book (with Robert Austin) called Artful Making. In our session, we had lots of fun not only following improv principles but doing improv exercises. Improv is about awareness of yourself and others; valuable skills. ---Michael B</description>
		<content:encoded><![CDATA[<p>You might have enjoyed the presentation I did last year with Adam White and Adam Geras at Agile 2008. You might also have enjoyed even more Lee Devin&#8217;s session, and his book (with Robert Austin) called Artful Making. In our session, we had lots of fun not only following improv principles but doing improv exercises. Improv is about awareness of yourself and others; valuable skills. &#8212;Michael B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Breslau</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2576</link>
		<dc:creator>Dan Breslau</dc:creator>
		<pubDate>Mon, 02 Mar 2009 21:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2576</guid>
		<description>I think these fit well with the spirit of Agile. And #5 is self-fulfilling : I feel changed by that suggestion. Chris, have you considered improv as a team-building exercise for Agile teams? To Marcos re #1 (&quot;Accept every offer&quot;) : I have only a little experience with improv (and none that&#039;s recent), but I gather that &quot;Accept every offer&quot; refers to the practice of not rejecting an improv theme on stage. I think this works in the business world as: &quot;Consider every idea&quot;. That is, don&#039;t reject a new concept simply because it makes you uncomfortable. Follow it in your head and see where it takes you. Several of the ideas embodied by Agile (test-driven development and timeboxing come to mind) made me uncomfortable at first, but I&#039;ve come to see how to make them work for me.</description>
		<content:encoded><![CDATA[<p>I think these fit well with the spirit of Agile. And #5 is self-fulfilling : I feel changed by that suggestion. Chris, have you considered improv as a team-building exercise for Agile teams? To Marcos re #1 (&#8220;Accept every offer&#8221;) : I have only a little experience with improv (and none that&#8217;s recent), but I gather that &#8220;Accept every offer&#8221; refers to the practice of not rejecting an improv theme on stage. I think this works in the business world as: &#8220;Consider every idea&#8221;. That is, don&#8217;t reject a new concept simply because it makes you uncomfortable. Follow it in your head and see where it takes you. Several of the ideas embodied by Agile (test-driven development and timeboxing come to mind) made me uncomfortable at first, but I&#8217;ve come to see how to make them work for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcos Orozco</title>
		<link>http://edgehopper.com/improv-the-key-to-innovation/comment-page-1/#comment-2575</link>
		<dc:creator>Marcos Orozco</dc:creator>
		<pubDate>Mon, 02 Mar 2009 21:23:19 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/improv-the-key-to-innovation/#comment-2575</guid>
		<description>&quot;Interesting, I agree with you about improv as a skill relative to innovation, but I dude about your first point: Acept every offer??? mmm... even when the offer is out of you domain... I think &quot;caution&quot; is not the oposite to &quot;take a risk&quot;. I can take a risk with caution; totally agree with your point 4.&quot;</description>
		<content:encoded><![CDATA[<p>&#8220;Interesting, I agree with you about improv as a skill relative to innovation, but I dude about your first point: Acept every offer??? mmm&#8230; even when the offer is out of you domain&#8230; I think &#8220;caution&#8221; is not the oposite to &#8220;take a risk&#8221;. I can take a risk with caution; totally agree with your point 4.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
