Showing posts with label Innovation. Show all posts
Showing posts with label Innovation. Show all posts

Saturday, March 16, 2013

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

Thursday, February 28, 2013

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

Wednesday, February 27, 2013

Innovation Technique: JTBD (Jobs To Be Done)

Jobs To Be Done: Instead of focusing on what you are doing, focus on the jobs your customers (internal or external) are trying to accomplish. Instead of improving the lawnmowers you are manufacturing, maybe you should genetically engineer grass? (the job to be done: keep lawn looking tidy). Software industry relevance: similar to User Stories, but much more higher level than most people use User Stories. Based in part on The Innovators Toolkit