They're about what you refuse to kill.
Every year, companies pour millions into products that everyone privately knows are already dead. The money keeps flowing. Not because the idea is good, but because no one wants to be the person who says "stop."
In 1988, Robert Cooper studied 60-plus product projects, half winners, half losers, to find what separated them. It wasn't budget. It wasn't talent. It was the discipline to make hard calls at fixed points.
He turned that into Stage-Gate.
The idea is simple. Split development into stages. Between each one, put a gate. At every gate, one honest decision: Go, Kill, or Hold. Does the evidence justify the next dollar, or not?
Scoping. Business case. Development. Testing. Launch.
It worked. Firms running a formal Stage-Gate process were 2.5 times more successful at launching new products. Time slippage dropped from 35% to 17%. Cycle times ran about 30% shorter. 3M built Post-it Notes through it. P&G, Exxon, Corning, DuPont and LEGO all run versions of it.
Then came the twist.
By 2014, Cooper was warning about his own creation. In too many companies, the gates had hardened into checklists. Discipline had become paperwork. The system built to protect good bets was now smothering them in compliance.
So he rebuilt it. In 2016, Cooper and Sommer kept the gates for governance but dropped fast, iterative sprints inside the stages. They called it Agile-Stage-Gate. LEGO became the case everyone copies. The logic is clean: irreversible, expensive bets go through a gate, reversible ones get a sprint.
But the framework was never the point.
The point is the question every gate forces you to answer out loud:
"On the evidence we have right now, would we still start this project today?"
Most products that die in the market failed that question long before launch. They were killed too late. Or never killed at all.
Look at your own pipeline.
Is there a project still alive only because no one wants to kill it: yes or no?
