<?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>Tim KastelleThe Problem is Actually Making Something &#8211; Tim Kastelle</title>
	<atom:link href="https://timkastelle.org/blog/2010/10/the-problem-is-actually-making-something/feed/" rel="self" type="application/rss+xml" />
	<link>https://timkastelle.org</link>
	<description>Build Autonomy &#38; Impact With Ideas</description>
	<lastBuildDate>Tue, 08 Apr 2025 22:50:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">36782504</site>		<item>
		<title>The Problem is Actually Making Something</title>
		<link>https://timkastelle.org/blog/2010/10/the-problem-is-actually-making-something/</link>
		<comments>https://timkastelle.org/blog/2010/10/the-problem-is-actually-making-something/#comments</comments>
		<pubDate>Sun, 17 Oct 2010 10:06:01 +0000</pubDate>
		<dc:creator>Tim Kastelle</dc:creator>
				<category><![CDATA[book riffs]]></category>
		<category><![CDATA[innovation]]></category>
		<guid isPermaLink="false">https://timkastelle.org/blog/?p=2670</guid>

				<description><![CDATA[I had a chance to catch up with a friend last week who recently changed jobs. He is passionate about innovation, and his previous job title had been &#8220;Innovation Champion&#8221;, a position seemingly custom-designed for his skills and interests. So why did he switch jobs? That was one of the topics that we discussed. It [&#8230;]]]></description>
					<content:encoded><![CDATA[<p>I had a chance to catch up with a friend last week who recently changed jobs.  He is passionate about innovation, and his previous job title had been &#8220;Innovation Champion&#8221;, a position seemingly custom-designed for his skills and interests.</p>
<p>So why did he switch jobs?</p>
<p>That was one of the topics that we discussed.  It turns out that the day-to-day reality of the job was a lot more frustrating than the job title suggested, and the problems that he faced are actually very common.  There were two main obstacles that he ran into.  The first is that his firm made him an &#8220;Innovation Champion&#8221;, and then the senior managers acted as though that was all they had to do to make innovation happen.  There were no structures or processes in place to help him out.  There were other Innovation Champions throughout the firm, but they were widely distributed, and there was no coherent, co-ordinated approach to innovation.</p>
<p>This problem is surprisingly common.  There are two approaches to innovation that seem to work well in larger firms.  One is to have dedicated innovation teams that are given the task of making sure that new ideas are executed.  Sometimes they come up with the ideas as well, in other cases they manage ideas from the rest of the firm.  The recent version of Xerox&#8217;s PARC Labs is a good example of this approach.</p>
<p>The other option that works is to embed innovation throughout the entire organisation &#8211; make it everybody&#8217;s business to come up new ideas, and to execute them.  This is the approach that Proctor &#038; Gamble and Zappos Shoes have taken, and with enough top-level support, this can be a very successful way to manage innovation.</p>
<p>My friend&#8217;s firm didn&#8217;t do either of these &#8211; they ended up with a solution that was neither fish nor fowl.  It was stuck in the middle, and the Innovation Champions were left with all of the responsibility for making innovation happen, but no real resources to do so.</p>
<p>The second problem is that the corporate-level Innovation Champion saw innovation as primarily the act of generating new ideas.  If you read this blog with any kind of regularity, you&#8217;ll know how strongly we emphasize the idea that innovation is a process, and that in addition to generating ideas, organisations need to be good at selecting and executing new ideas, and at getting them to diffuse.  You must be good at all three steps to succeed at innovation over an extended period of time.</p>
<p>I sometimes think that I spend too much time making this point, and yet, the concept that innovation is only about ideas is distressingly widespread.  Scott Berkun recently addressed this issue as well, in a <a href="http://www.scottberkun.com/blog/2010/webcastqa/">Q&#038;A session supporting the launch</a> of the paperback version of his excellent book <strong>The Myths of Innovation</strong>:</p>
<blockquote><p>Naomi Maloney: Q. Aren’t we really talking about IDEAS?<br />
Sure. But that’s just more vocabulary. What is an idea? When you’re dead, is an idea you had in your mind more important than an idea manifested somehow in the world?<br />
You can spend weeks debating which vocabulary is best for thinking about creativity – it is fun to a point. But then you realize you haven’t done any real work towards solving any real problem. I’m happy to yield to other people’s vocabulary if it gets everyone to actually make or design a prototype for something sooner. Most people have an idea for a book / movie / company / product / thing, but never manifest in the world in any way. The hard part is rarely the idea. Or what vocabulary they’re using. The problem is asses in chairs, or at whiteboards, or in code, or in a lab, actually making something.</p></blockquote>
<p>This is consistent with my experience and observations as well &#8211; the hard part is not coming up with the ideas, the hard part is making them happen.</p>
<p>This is why I make an effort to get this message across &#8211; because if organisations don&#8217;t understand these two points, they will not be able to manage innovation effectively.  If they fail to do this, then they are at risk of falling behind their competitors, and they are also more likely to lose their most creative and innovative people.<br />
If they have a dominant position in a completely stable market, they can maybe afford these outcomes.  In any other case, though, it&#8217;s bad to lose people like this &#8211; and eventually it will lead to bad outcomes.</p>
<p>(By the way, all of the Berkun Q&#038;A post is worth reading &#8211; in particular check out the diagram showing the evolution of copyright protection.)  </p>

<div id='jp-relatedposts' class='jp-relatedposts' >
	<h3 class="jp-relatedposts-headline"><em>Related</em></h3>
</div>]]></content:encoded>
			

		<wfw:commentRss>https://timkastelle.org/blog/2010/10/the-problem-is-actually-making-something/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
				<post-id xmlns="com-wordpress:feed-additions:1">2670</post-id>	</item>
	</channel>
</rss>
<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced (SSL caching disabled) 

Served from: timkastelle.org @ 2026-06-11 22:09:13 by W3 Total Cache
-->