Stage-Gate
5 min read · 4 principles · apply it by lunch
Morning. Every project your business has ever started is still technically alive. That’s the problem.
Of everything your business has started in the last two years, how many were formally stopped at a meeting where stopping was one of the options on the table — and how many just thinned out until nobody could say when they’d ended? The difference between those two numbers is money you no longer have.
Robert G. Cooper, a professor at McMaster University’s DeGroote School of Business in Ontario, spent years studying hundreds of new-product launches to find what separated the successes from the failures, first put the result into print as Stage-Gate in 1988, and set it out for managers in Business Horizons in 1990. The structure is deliberately dull. Work is divided into stages — scoping, business case, development, testing, launch — and between every pair sits a gate: a meeting with named attendees, a fixed set of deliverables due beforehand, criteria agreed in advance, and an output that is more than a verdict. Cooper split those criteria in two. Must-meet criteria form a checklist that removes misfits quickly. Should-meet criteria are scored, so projects can be ranked against one another instead of each being judged alone. And a gate has four available verdicts rather than two: go, kill, hold, recycle. The trap is the gate that has only ever said go. Cooper has returned to that failure for decades since — his own name for the remedy is gates with teeth — because a gate where nothing has ever been stopped isn’t a decision any more. It’s a milestone with catering, and the pipeline behind it fills up with work everybody privately knows is finished.
Stage-Gate is Day 313 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee