AIM Archives - Tag: kill project

Imagine two new-product project teams have gate reviews on the same day, and both projects are stopped. The first is stopped for the right reasons, e.g. smaller-than-expected market size or low customer interest… as evidenced by tiny Market Satisfaction Gaps. This is low Opportunity Quality. The second team is stopped due to sloppy work: skimpy customer interviews and much confirmation bias. This is low Execution Quality. Celebrate the first team. Train the second. For every project, make sure you know which is which.

More in article, 3 Problems with Innovation Metrics

This is what Astro Teller—the head of Google X—used to cheer with his teams. He went on to explain, “We spend most of our time trying to prove we’re wrong.” Is that how your company looks at big, transformational projects? Or do you associate a killed project with personal failure? Much better to lay out all the assumptions of “what must be true” for your project to succeed. Then go on a team “hunt” to find any that are not true. Find one? Celebrate and move on to the next project!

More in video at Project De-risking with Minesweeper