Why Good Ideas Fail

http://www.forbes.com/sites/ciocentral/2012/04/30/why-great-ideas-fail/Generating good ideas is one thing, but gaining the required support within a corporation is quite another.
In most organization, you'd have to 'run the gauntlet' to get your idea accepted.
 Some ideas to make this more likely:

• Let your opposition speak. They will anyhow. Show respect for their dissenting voice.
• Do not attack back
• Expect the common ways your ideas will be attacked
  • Fear-mongering
  • Delay
  • Confusion
  • Ridicule
• Expect the common not-so-innocent questions meant to derail you, including:
  • Another Problem: "Money is the only real issue"; "What about ?";
  • Inertia: "We're successful, why change?";"The problem is not that bad";"You're implying we've been failing"
  • Solution: "Your proposal goes too far/doesn’t go far enough.";"You’re abandoning our core values.";"No one else does this.";"People have too many concerns.";" It puts us on a slippery slope."
  • and more...
• Be prepared!

 Interesting read @HBR @Forbes @cbsnews

Innovation technique: Nine Windows

consider the matrix {past,present,future}x{supersystem,system,subsystem}. Fill in center(present,system). Complete the grid. Observe for insights.

Innovation Technique: Outcome Expectation

1. Identify Jobs To Be Done 2. Identify 4 quadrants: desired/undesired outcomes to client/provider 3. Create outcome statement: include the direction of action (minimize/maximize), unit (time/cost/etc.) object, and context. e.g.: "Decrease the likelihood of delayed customer orders" Software Industry Relevance: Often there are 3 players: the end user (functionality), the provider as a financial entity (monitezation) and the provider as a technical entity (design integrity). You need to recognize those disparate needs and identify what each role/entity preferences are. Based in part on The Innovator Toolkit