<?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: Top ten tips for preventing innovation</title>
	<atom:link href="http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/</link>
	<description>Software product success.</description>
	<lastBuildDate>Fri, 12 Mar 2010 01:42:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-88921</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Thu, 19 Apr 2007 16:44:13 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-88921</guid>
		<description>If I respond to that, does it create an expectation that I am supposed to reply to all the comments?

[This reply generated by a bot.  Please do not expect &lt;del&gt;Wally&lt;/del&gt; Scott to reply in the future.]</description>
		<content:encoded><![CDATA[<p>If I respond to that, does it create an expectation that I am supposed to reply to all the comments?</p>
<p>[This reply generated by a bot.  Please do not expect <del>Wally</del> Scott to reply in the future.]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-88885</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Thu, 19 Apr 2007 11:10:54 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-88885</guid>
		<description>You&#039;ve got a &quot;Wally&quot; (dilbert) coffee mug don&#039;t you.</description>
		<content:encoded><![CDATA[<p>You&#8217;ve got a &#8220;Wally&#8221; (dilbert) coffee mug don&#8217;t you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sjt Rants... &#183; links for 2006-12-28</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-59684</link>
		<dc:creator>sjt Rants... &#183; links for 2006-12-28</dc:creator>
		<pubDate>Thu, 28 Dec 2006 15:02:07 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-59684</guid>
		<description>[...] Top ten tips for preventing innovation -Tyner Blain (tags: Entrepreneurship Humor Sarcasm) [...]</description>
		<content:encoded><![CDATA[<p>[...] Top ten tips for preventing innovation -Tyner Blain (tags: Entrepreneurship Humor Sarcasm) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-59610</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 27 Dec 2006 03:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-59610</guid>
		<description>&lt;blockquote&gt;I have seen the enemy and the enemy is us.
&lt;cite&gt;An reader who has requested anonymity&lt;/cite&gt;&lt;/blockquote&gt;
One commenter emailed me privately, and told me that as much as he/she would like to share the following, he/she believed that his/her coworkers would take offense.  So, with the protection of discretion, here&#039;s an essay sent from the field, on this very topic.  Thanks unknown reader/writer!
&lt;p class=&quot;Body&quot;&gt;So you want to be part of an innovative team, huh? You hear about these groups that just do these cool things and wonder “why not us?” I dunno what to tell you. I’ve decided if you can’t beat ‘em, join ‘em. Here’s my 10 things to do to avoid having to work for one of this fairy weird innovating teams.&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;1.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Find a Safe Niche&lt;/strong&gt; - What you want is a zone, an area, where no one else comes. At least, not without your control. It’s all yours. If you own it, then no one’s the wiser for what to expect. The last thing you want is someone in your area. They might suggest different ways of doing things. New and improved. That could lead to change and that would mean: i-n-n-o-v-a-t-i-o-n. &lt;em&gt;That&lt;/em&gt; = Bad&lt;sup&gt;(tm)&lt;/sup&gt;. The best way for to be granted solitude in your niche, is to grant, yay, even encourage, others to do the same. Influence any process you can  to drive niche ownership as far as you can. Authority is good. Free thinking is bad. Use words like “lead”, “in charge of”, “not my area”, “don’t want to step on toes”, and my favorite: “czar”.&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;2.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Make New Hires Feel Incompetent&lt;/strong&gt; - When someone joins your team, that’s fertile ground for change. That’s bad. Remember that. Often, management may have even hired them with the idea of “new blood” in mind. Resist this. With all your might. You fought long and hard to get things the way they are. The best way is to break them down swiftly and brutally. My favorite technique is the “Cat and Mouse” strategy. Give your new peer quite a bit of latitude. Don’t tell her your full expectations. Give them latitude, encourage them to explore and make the decisions. Then when they bring the result back, pounce on them for little things you purposefully left out. Belittle or deprecate any hints of innovation. Quietly approve the acts of StatusQuo. Make sure that you treat “old blood” deferentially. Make sure the “new blood” sees that. &lt;strong&gt;Never&lt;/strong&gt; ask the new hire what he thinks of... anything. Tell him (partially) how it is. One way communication. He’s learning the ropes. You know them. He has nothing to offer. “Offering” would be innovative. Some “new blood” types are persistent. Be patient. Put off their ideas or minimize their dreams with statements like “maybe in time” or remind them that these things should be done with “baby steps.”&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;3.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Whine About Salary&lt;/strong&gt; - It’s all about money. OK? Keep that in mind. What you do puts bread on the table. Nothing more. Nothing less. Keep your mind focused on that green stuff and how you can get more of it. Remind teammates to do the same. If you begin to waver, you run the risk of developing a passion for the actual thing you do. That cannot happen. That kind of thing leads to innovation. Queue chorus line: “That is Bad!”&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;4.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Read Things Like&lt;/strong&gt; &lt;a href=&quot;http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/&quot;&gt;&lt;span style=&quot;color: #1b00a8&quot;&gt;Top ten tips for preventing innovation -Tyner Blain&lt;/span&gt;&lt;/a&gt; - Blame management. Foster a brotherhood of This Company Sucks. Repeat the tenets to each other often. Blame the Information Technology group. Blame the shareholders. The board. Blame the janitor. The important part, is that you find blame for the lack of innovation on your team somewhere &lt;em&gt;outside&lt;/em&gt; of the team. As long as you can keep yourself and teammates facing outward, angry about a group of people you can do &lt;em&gt;nothing&lt;/em&gt; about, you’ll never have to worry about looking inside and changing for “the better.” Genghis Khan understood this principle very well. Look how far he got!&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;5.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Treat Each Other Like Garbage&lt;/strong&gt; - Innovation flourishes in an environment where people are excited about each other and what each has to offer. Positive feedback cycles. You do not want some sort of “look at this cool stuff I did” followed by “yeah, that is cool, look at this cool thing I did.” That could lead to a chain reaction of back-slapping feel-good group-innovation. Keep your peers at a distance. Go dark if you can. Comment, preach, lecture on others’ ideas and projects. If you ask a question, it should be of the challenge format. Just remember OJ Simpson in the court room and you’ll do OK. Never act as if you have something to learn from your team mates. You’re all professionals, well paid ones, you don’t need to really talk to each other. Never bounce ideas off of others. Present your near finished concepts to them. Avoid honest open ended together brainstorming. If someone gets excited, minimize with phrases like “I wanna think about that”, “let’s talk about this after this release”, or “write that idea up, huh?” (you can let it sit in limbo for ever). When you do have meetings (in person or on the phone) make sure you don’t have much to say to each other. None of you really need each other. And no one else has anything to offer you. Team mates should either never be sure of where you will stand on an idea or know that you’ll eternally oppose some of their favorite themes.&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;6.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Incremental Improvement&lt;/strong&gt; - Slow and steady wins the race. Concentrate on the task at hand. Never refactor a sub system. New ways of looking at the problem lurk in there. A stable API is everything. You have to keep each other in check here. When you review/approve changes from teammates, always choose the more-hacky-less-code-rewriteing approach. If they propose replacement modules, remind them about customer commitments to backwards compatibility (this is the unbeatable trump card). Use comforting phrases like “just for now”, “just for the release”, and “lets wait until we’re in the next release cycle to look at that.”&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;7.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Manage Your Process&lt;/strong&gt; - Process is good for killing innovation. Process is safe. Create lots of it. Leap on every single failure as an opportunity to add checks, balances, form signing, and tools. Whenever you have a meeting, if you must talk, dominate it with ideas about process. You can’t go wrong suggesting more process. Anyone who resists you will be seen as dangerous or risky. Point out how well you jump through hoops. You can create a team spirit of hoop jumping by doing this. Never add your support to any effort to remove an element of process. Defend process with all your might. It was put in place for a good reason! Don’t let history repeat itself!&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;8.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Ignore The Customer&lt;/strong&gt; - Stick to your own ideas. Stick to your own agenda. Keep things stable. You really have to watch out for &lt;em&gt;outsiders&lt;/em&gt; who write 3rd party extensions to your stuff.They have new ways of looking at things, and that might spark some innovation. Do everything you can to ignore customer mailing lists. Go long periods ignoring things that you could obviously answer. It might lead to a discussion that might lead to a break through. Defer customer suggested feature requests repeatedly. Elevate your own meager ideas repeatedly.&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;9.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt;      &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Never Peer Review&lt;/strong&gt; - Never ask your peers to give you constructive feedback on how your work affects the work they do. Figuring out how to do better could threaten your niche ownership by exposing your weak points. It would jeopardize your right to do what you want; it might lead to you doing something that made others happy. People who make stuff that other people like are often labeled innovative. And never never never introspect about the group with each other. At least, not seriously.&lt;/p&gt;
&lt;p style=&quot;margin-left: 0.25in; text-indent: -0.25in&quot; class=&quot;Body&quot;&gt;&lt;!--[if !supportLists]--&gt;10.&lt;span style=&quot;font-family: &quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal&quot;&gt; &lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;Build A Culture&lt;/strong&gt; - Culture is everything. It governs how people think and act in your group. Make sure your culture comes first. You admittedly might see a good idea from time to time. It happens. Just remember, it is more important that your culture stay in tact. Protect that first. If there’s room left over (there won’t be), you can give credence to the idea. If your culture is strong, revolutionaries and their innovative ideas will struggle to gain footing.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<blockquote><p>I have seen the enemy and the enemy is us.<br />
<cite>An reader who has requested anonymity</cite></p></blockquote>
<p>One commenter emailed me privately, and told me that as much as he/she would like to share the following, he/she believed that his/her coworkers would take offense.  So, with the protection of discretion, here&#8217;s an essay sent from the field, on this very topic.  Thanks unknown reader/writer!</p>
<p class="Body">So you want to be part of an innovative team, huh? You hear about these groups that just do these cool things and wonder “why not us?” I dunno what to tell you. I’ve decided if you can’t beat ‘em, join ‘em. Here’s my 10 things to do to avoid having to work for one of this fairy weird innovating teams.</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->1.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Find a Safe Niche</strong> &#8211; What you want is a zone, an area, where no one else comes. At least, not without your control. It’s all yours. If you own it, then no one’s the wiser for what to expect. The last thing you want is someone in your area. They might suggest different ways of doing things. New and improved. That could lead to change and that would mean: i-n-n-o-v-a-t-i-o-n. <em>That</em> = Bad<sup>(tm)</sup>. The best way for to be granted solitude in your niche, is to grant, yay, even encourage, others to do the same. Influence any process you can  to drive niche ownership as far as you can. Authority is good. Free thinking is bad. Use words like “lead”, “in charge of”, “not my area”, “don’t want to step on toes”, and my favorite: “czar”.</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->2.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Make New Hires Feel Incompetent</strong> &#8211; When someone joins your team, that’s fertile ground for change. That’s bad. Remember that. Often, management may have even hired them with the idea of “new blood” in mind. Resist this. With all your might. You fought long and hard to get things the way they are. The best way is to break them down swiftly and brutally. My favorite technique is the “Cat and Mouse” strategy. Give your new peer quite a bit of latitude. Don’t tell her your full expectations. Give them latitude, encourage them to explore and make the decisions. Then when they bring the result back, pounce on them for little things you purposefully left out. Belittle or deprecate any hints of innovation. Quietly approve the acts of StatusQuo. Make sure that you treat “old blood” deferentially. Make sure the “new blood” sees that. <strong>Never</strong> ask the new hire what he thinks of&#8230; anything. Tell him (partially) how it is. One way communication. He’s learning the ropes. You know them. He has nothing to offer. “Offering” would be innovative. Some “new blood” types are persistent. Be patient. Put off their ideas or minimize their dreams with statements like “maybe in time” or remind them that these things should be done with “baby steps.”</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->3.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Whine About Salary</strong> &#8211; It’s all about money. OK? Keep that in mind. What you do puts bread on the table. Nothing more. Nothing less. Keep your mind focused on that green stuff and how you can get more of it. Remind teammates to do the same. If you begin to waver, you run the risk of developing a passion for the actual thing you do. That cannot happen. That kind of thing leads to innovation. Queue chorus line: “That is Bad!”</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->4.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Read Things Like</strong> <a href="http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/"><span style="color: #1b00a8">Top ten tips for preventing innovation -Tyner Blain</span></a> &#8211; Blame management. Foster a brotherhood of This Company Sucks. Repeat the tenets to each other often. Blame the Information Technology group. Blame the shareholders. The board. Blame the janitor. The important part, is that you find blame for the lack of innovation on your team somewhere <em>outside</em> of the team. As long as you can keep yourself and teammates facing outward, angry about a group of people you can do <em>nothing</em> about, you’ll never have to worry about looking inside and changing for “the better.” Genghis Khan understood this principle very well. Look how far he got!</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->5.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Treat Each Other Like Garbage</strong> &#8211; Innovation flourishes in an environment where people are excited about each other and what each has to offer. Positive feedback cycles. You do not want some sort of “look at this cool stuff I did” followed by “yeah, that is cool, look at this cool thing I did.” That could lead to a chain reaction of back-slapping feel-good group-innovation. Keep your peers at a distance. Go dark if you can. Comment, preach, lecture on others’ ideas and projects. If you ask a question, it should be of the challenge format. Just remember OJ Simpson in the court room and you’ll do OK. Never act as if you have something to learn from your team mates. You’re all professionals, well paid ones, you don’t need to really talk to each other. Never bounce ideas off of others. Present your near finished concepts to them. Avoid honest open ended together brainstorming. If someone gets excited, minimize with phrases like “I wanna think about that”, “let’s talk about this after this release”, or “write that idea up, huh?” (you can let it sit in limbo for ever). When you do have meetings (in person or on the phone) make sure you don’t have much to say to each other. None of you really need each other. And no one else has anything to offer you. Team mates should either never be sure of where you will stand on an idea or know that you’ll eternally oppose some of their favorite themes.</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->6.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Incremental Improvement</strong> &#8211; Slow and steady wins the race. Concentrate on the task at hand. Never refactor a sub system. New ways of looking at the problem lurk in there. A stable API is everything. You have to keep each other in check here. When you review/approve changes from teammates, always choose the more-hacky-less-code-rewriteing approach. If they propose replacement modules, remind them about customer commitments to backwards compatibility (this is the unbeatable trump card). Use comforting phrases like “just for now”, “just for the release”, and “lets wait until we’re in the next release cycle to look at that.”</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->7.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Manage Your Process</strong> &#8211; Process is good for killing innovation. Process is safe. Create lots of it. Leap on every single failure as an opportunity to add checks, balances, form signing, and tools. Whenever you have a meeting, if you must talk, dominate it with ideas about process. You can’t go wrong suggesting more process. Anyone who resists you will be seen as dangerous or risky. Point out how well you jump through hoops. You can create a team spirit of hoop jumping by doing this. Never add your support to any effort to remove an element of process. Defend process with all your might. It was put in place for a good reason! Don’t let history repeat itself!</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->8.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Ignore The Customer</strong> &#8211; Stick to your own ideas. Stick to your own agenda. Keep things stable. You really have to watch out for <em>outsiders</em> who write 3rd party extensions to your stuff.They have new ways of looking at things, and that might spark some innovation. Do everything you can to ignore customer mailing lists. Go long periods ignoring things that you could obviously answer. It might lead to a discussion that might lead to a break through. Defer customer suggested feature requests repeatedly. Elevate your own meager ideas repeatedly.</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->9.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal">      </span><!--[endif]--><strong>Never Peer Review</strong> &#8211; Never ask your peers to give you constructive feedback on how your work affects the work they do. Figuring out how to do better could threaten your niche ownership by exposing your weak points. It would jeopardize your right to do what you want; it might lead to you doing something that made others happy. People who make stuff that other people like are often labeled innovative. And never never never introspect about the group with each other. At least, not seriously.</p>
<p style="margin-left: 0.25in; text-indent: -0.25in" class="Body"><!--[if !supportLists]-->10.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal"> </span><!--[endif]--><strong>Build A Culture</strong> &#8211; Culture is everything. It governs how people think and act in your group. Make sure your culture comes first. You admittedly might see a good idea from time to time. It happens. Just remember, it is more important that your culture stay in tact. Protect that first. If there’s room left over (there won’t be), you can give credence to the idea. If your culture is strong, revolutionaries and their innovative ideas will struggle to gain footing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KnowHR Blog &#187; Blog Archive &#187; How to Squelch Innovation</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-59003</link>
		<dc:creator>KnowHR Blog &#187; Blog Archive &#187; How to Squelch Innovation</dc:creator>
		<pubDate>Thu, 21 Dec 2006 12:24:53 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-59003</guid>
		<description>[...] Tyler Blain&#8217;s Top Ten Tips for Preventing Innovation is brilliant. It should be required reading for everyone in the people business (which is all of us). Three nuggets: Keep salaries below the 75th percentile. Innovators know their value - and when they aren’t applying for jobs with intrinsic utility to them, they are commanding higher salaries. If we keep our salaries low, there’s much less risk of one of these innovators sneaking into our organization. As a bonus, we’ll save a fortune! [...]</description>
		<content:encoded><![CDATA[<p>[...] Tyler Blain&#8217;s Top Ten Tips for Preventing Innovation is brilliant. It should be required reading for everyone in the people business (which is all of us). Three nuggets: Keep salaries below the 75th percentile. Innovators know their value &#8211; and when they aren’t applying for jobs with intrinsic utility to them, they are commanding higher salaries. If we keep our salaries low, there’s much less risk of one of these innovators sneaking into our organization. As a bonus, we’ll save a fortune! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alfredo reino &#187; Blog Archive &#187; links for 2006-12-20</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58999</link>
		<dc:creator>alfredo reino &#187; Blog Archive &#187; links for 2006-12-20</dc:creator>
		<pubDate>Thu, 21 Dec 2006 10:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58999</guid>
		<description>[...] Top ten tips for preventing innovation (tags: humor fun management creativity) [...]</description>
		<content:encoded><![CDATA[<p>[...] Top ten tips for preventing innovation (tags: humor fun management creativity) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curious Cat Management Improvement Blog</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58885</link>
		<dc:creator>Curious Cat Management Improvement Blog</dc:creator>
		<pubDate>Tue, 19 Dec 2006 13:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58885</guid>
		<description>&lt;strong&gt;How to Prevent Innovation...&lt;/strong&gt;

Top ten tips for preventing innovation give some great ideas many companies are already doing but you may find some your company hasn&#8217;t mastered    For example:
Make performance reviews easy. Create some easy-to-measure metrics (like # of sick-da...</description>
		<content:encoded><![CDATA[<p><strong>How to Prevent Innovation&#8230;</strong></p>
<p>Top ten tips for preventing innovation give some great ideas many companies are already doing but you may find some your company hasn&#8217;t mastered    For example:<br />
Make performance reviews easy. Create some easy-to-measure metrics (like # of sick-da&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top 10 Tips for Preventing Innovation at jimmyblake.com</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58883</link>
		<dc:creator>Top 10 Tips for Preventing Innovation at jimmyblake.com</dc:creator>
		<pubDate>Tue, 19 Dec 2006 12:52:40 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58883</guid>
		<description>[...] The Tyner Blaine Website has a list of 10 common mistakes companies make that stiffle their create processes. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Tyner Blaine Website has a list of 10 common mistakes companies make that stiffle their create processes. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joob</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58880</link>
		<dc:creator>joob</dc:creator>
		<pubDate>Tue, 19 Dec 2006 11:51:29 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58880</guid>
		<description>well this was a disappointingly obvious post. 
i.e. hire stupid people and/or convince them to want to do nothing.
i guess this means one can just copy an innovative company to be
innovative oneself.</description>
		<content:encoded><![CDATA[<p>well this was a disappointingly obvious post.<br />
i.e. hire stupid people and/or convince them to want to do nothing.<br />
i guess this means one can just copy an innovative company to be<br />
innovative oneself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: regeya</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58859</link>
		<dc:creator>regeya</dc:creator>
		<pubDate>Tue, 19 Dec 2006 05:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58859</guid>
		<description>I could add much more, but I think I&#039;d get found out awful quick. :-&gt;</description>
		<content:encoded><![CDATA[<p>I could add much more, but I think I&#8217;d get found out awful quick. :-&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ideal Mechanism Blog &#187; Blog Archive &#187; Preventing Innovation - Some Good Bad Advice</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58846</link>
		<dc:creator>Ideal Mechanism Blog &#187; Blog Archive &#187; Preventing Innovation - Some Good Bad Advice</dc:creator>
		<pubDate>Tue, 19 Dec 2006 00:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58846</guid>
		<description>[...] Tyner Blain breaks down how companies can prevent innovation into 10 easy steps.  If these sound familiar, you may have a problem. [...]</description>
		<content:encoded><![CDATA[<p>[...] Tyner Blain breaks down how companies can prevent innovation into 10 easy steps.  If these sound familiar, you may have a problem. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58838</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Mon, 18 Dec 2006 22:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58838</guid>
		<description>Thanks Macz - fixed the typo.

Welcome Reddit readers.  You&#039;re doing a great job of stress-testing Yahoo (our host) today.  

Richard - Legal department is a great idea.  Consider this a bonus 11th tip for the folks who read the comments!

Scott</description>
		<content:encoded><![CDATA[<p>Thanks Macz &#8211; fixed the typo.</p>
<p>Welcome Reddit readers.  You&#8217;re doing a great job of stress-testing Yahoo (our host) today.  </p>
<p>Richard &#8211; Legal department is a great idea.  Consider this a bonus 11th tip for the folks who read the comments!</p>
<p>Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58836</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Mon, 18 Dec 2006 21:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58836</guid>
		<description>I would suggest swapping &quot;start a legal department&quot; for &quot;easy evaluations&quot;</description>
		<content:encoded><![CDATA[<p>I would suggest swapping &#8220;start a legal department&#8221; for &#8220;easy evaluations&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to stop innovation : Pensieri di un lunatico minore</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58829</link>
		<dc:creator>How to stop innovation : Pensieri di un lunatico minore</dc:creator>
		<pubDate>Mon, 18 Dec 2006 18:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58829</guid>
		<description>[...] A great post on how to prevent innovation. How many does your organization practice? [...]</description>
		<content:encoded><![CDATA[<p>[...] A great post on how to prevent innovation. How many does your organization practice? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top ten tips for preventing innovation &#171; Alt-Ctrl-Del</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58828</link>
		<dc:creator>Top ten tips for preventing innovation &#171; Alt-Ctrl-Del</dc:creator>
		<pubDate>Mon, 18 Dec 2006 18:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58828</guid>
		<description>[...] Top ten tips for preventing innovation [...]</description>
		<content:encoded><![CDATA[<p>[...] Top ten tips for preventing innovation [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Macz</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-58819</link>
		<dc:creator>Macz</dc:creator>
		<pubDate>Mon, 18 Dec 2006 15:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-58819</guid>
		<description>&quot;Google allows their employees to dedicate 20% of their time to whatever interests them - and Google’s employees innovative a lot.&quot;

Do you mean &quot;- Google&#039;s employees innovate a lot&quot; ?</description>
		<content:encoded><![CDATA[<p>&#8220;Google allows their employees to dedicate 20% of their time to whatever interests them &#8211; and Google’s employees innovative a lot.&#8221;</p>
<p>Do you mean &#8220;- Google&#8217;s employees innovate a lot&#8221; ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sameer</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-55377</link>
		<dc:creator>Sameer</dc:creator>
		<pubDate>Thu, 05 Oct 2006 13:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-55377</guid>
		<description>Excellent Article..</description>
		<content:encoded><![CDATA[<p>Excellent Article..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-54474</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 21 Jul 2006 04:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-54474</guid>
		<description>Thanks Timothy for reading and the very kind words!</description>
		<content:encoded><![CDATA[<p>Thanks Timothy for reading and the very kind words!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy Johnson</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-54469</link>
		<dc:creator>Timothy Johnson</dc:creator>
		<pubDate>Thu, 20 Jul 2006 20:47:46 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-54469</guid>
		<description>Brilliant and funny!  The great part is that you&#039;ve pegged the biggest point of innovation:  it doesn&#039;t act in a vacuum.  Systems, culture, HR, compensation, office politics, project structures, and --- oh yeah, people all &quot;conspire&quot; to make or break the innovative genes within the company.  Loved the post!</description>
		<content:encoded><![CDATA[<p>Brilliant and funny!  The great part is that you&#8217;ve pegged the biggest point of innovation:  it doesn&#8217;t act in a vacuum.  Systems, culture, HR, compensation, office politics, project structures, and &#8212; oh yeah, people all &#8220;conspire&#8221; to make or break the innovative genes within the company.  Loved the post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Design - standards based web design, development and training &#187; Blog Archive &#187; Some links for light reading (5/7/06)</title>
		<link>http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/comment-page-1/#comment-54457</link>
		<dc:creator>Max Design - standards based web design, development and training &#187; Blog Archive &#187; Some links for light reading (5/7/06)</dc:creator>
		<pubDate>Wed, 19 Jul 2006 23:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-54457</guid>
		<description>[...] Top ten tips for preventing innovation [...]</description>
		<content:encoded><![CDATA[<p>[...] Top ten tips for preventing innovation [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
