The problem
Robert Cooper’s Stage-Gate, introduced in 1990, solved a real problem: without a forced decision point, a new-product project drifts on momentum long after the case for it has quietly stopped being true. The gate — a defined moment where someone actually decides go, kill, hold, or recycle — was the discipline. It worked, and companies that had nothing before it were right to adopt it.
What it became, in a lot of the rooms it was installed in, was something else: a binder. A status deck due the Tuesday before the gate meeting. A scramble to assemble a deliverable that existed mainly to be reviewed, not to be used. None of that was Cooper’s idea — it was a reasonable answer to a real constraint in 1990, when the analysis behind a gate genuinely took weeks of analyst time, worth managing formally. A process built to manage expensive analysis doesn’t get lighter just because the analysis it’s managing got cheap. It gets emptier.
A gate after every stage is stage-gate. Analysis that runs straight through to one decision is the lighter thing.
The three questions run back to back. There’s no review to book between them, no sign-off to wait for, no deliverable to assemble. Two typed lines and one press give you a first pass on all three: need, worth, win. Every answer stays editable, and every figure shows how it was built. When it’s time to decide, the case is already there to read.
Nothing between the questions
There is deliberately nothing between the three questions — is the need real, is it worth it, can we win it. Moving from one to the next spends nothing but time, so nothing sits there: no gate, no sign-off, no “proceed to stage two.” The product stops at the decision. What comes after it — funding R&D, booking capacity, a customer qualification, a launch — is where real money moves, and that belongs to the process your company already runs.
The posture that falls out of this, stated the way it’s meant to be said to a buyer who already runs a formal process: no new process. Nothing here invents a meeting or an approval — it arms the decisions your company already makes. If you run Stage-Gate, this feeds it. If you don’t, you’ll never need to. Not a replacement — the tool does no approvals or governance, so it structurally can’t be one. A standing case, continuously current, that turns the gate meeting into a fifteen-minute read instead of the reason the deliverable-scramble existed in the first place.
Sources
An argument is easy to agree with and hard to check. This one has an artefact behind it — a market sized twice, the needs scored, and the assumptions written down before anyone went looking.
See a worked example →