<?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>The Savvy Technologist &#187; culture</title>
	<atom:link href="http://technosavvy.org/tag/culture/feed/" rel="self" type="application/rss+xml" />
	<link>http://technosavvy.org</link>
	<description>Great teaching and learning with technology</description>
	<lastBuildDate>Sat, 07 May 2011 04:55:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Mismanaging for the status quo</title>
		<link>http://technosavvy.org/2009/03/17/mismanaging-for-the-status-quo/</link>
		<comments>http://technosavvy.org/2009/03/17/mismanaging-for-the-status-quo/#comments</comments>
		<pubDate>Tue, 17 Mar 2009 06:57:49 +0000</pubDate>
		<dc:creator>Tim Wilson</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[culture]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[nasa]]></category>

		<guid isPermaLink="false">http://technosavvy.org/?p=552</guid>
		<description><![CDATA[Government agencies don&#8217;t generally have an innovative reputation. But NASA? Come one. If any government entity would be likely to embrace innovation and creative problem solving, certainly the organization that said this (prepare your J.F.K. impersonation) would encourage critical thinking. &#8230; <a href="http://technosavvy.org/2009/03/17/mismanaging-for-the-status-quo/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Government agencies don&#8217;t generally have an innovative reputation. But NASA? Come one. If any government entity would be likely to embrace innovation and creative problem solving, certainly the organization that said this (prepare your J.F.K. impersonation) would encourage critical thinking.</p>
<blockquote><p>We choose to go to the moon. We choose to go to the moon in this decade and do the other things, not because they are easy, but because they are hard, because that goal will serve to organize and measure the best of our energies and skills, because that challenge is one that we are willing to accept, one we are unwilling to postpone, and one which we intend to win, and the others, too.
</p></blockquote>
<p>The NASA of today is probably at least 100&times; larger than the agile agency that launched those Apollo missions back in the 60&#8242;s, and, according to an <a href="http://www.npr.org/templates/story/story.php?storyId=100346538">article published by NPR</a>, their bureaucracy is employing a lot of &#8220;innovation-blocking behaviors.&#8221; Not satisfied with the status quo, a veteran astronaut created a satirical video intended to call out the problems he&#8217;d been seeing at the agency. Watch this video and see if any of it rings true for you.</p>
<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/_424YskAfew&#038;hl=en&#038;fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/_424YskAfew&#038;hl=en&#038;fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed></object></p>
<p>OK, so no one&#8217;s going to win an Oscar for their performance in this video. Here are the innovation-blocking behaviors I noted while watching the video:</p>
<ul>
<li>Blind adherence to existing procedures or specifications</li>
<li>Compartmentalization</li>
<li>Emphasis on employee roles in the organization rather than the quality of their ideas</li>
<li>Fear of challenging the status quo (and those who maintain it)</li>
<li>Too much reliance on the chain of command</li>
<li>Tendency to &#8220;shoot the messenger&#8221;</li>
<li>Premature acceptance of resource constraints</li>
<li>Overly complex processes</li>
<li>Too comfortable in &#8220;the comfort zone&#8221;</li>
<li>Valuing process over results</li>
<li>Too much emphasis on past experience</li>
</ul>
<p>It&#8217;s easy to criticize without suggesting solutions, so I was impressed to see Part II posted 10 days ago.</p>
<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/b5nA8LX7TMw&#038;hl=en&#038;fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/b5nA8LX7TMw&#038;hl=en&#038;fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed></object></p>
<p>I think you can summarize Part II pretty easily. <em>Build innovation into your organization&#8217;s processes intentionally.</em> When the innovation is &#8220;baked in&#8221; to the structure of an organization it sends a message to all employees that the organization is keenly interesting in what they have to say. And that is an crucial step in building an innovative culture.</p>
]]></content:encoded>
			<wfw:commentRss>http://technosavvy.org/2009/03/17/mismanaging-for-the-status-quo/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

