When Stage-Gate Helps, and When It Kills Good Ideas

What stage-gate was built to solve — and when the trade reverses

Every organisation that commits capital to new products, capital projects or operational changes faces two different costs: the cost of backing the wrong thing, and the cost of moving too slowly on the right one. Transforming legacy processes begins by recognising which of those two costs your current approval process was built to prevent.

A stage-gate process separates development phases with formal decision points at which a project team must present evidence before receiving the next tranche of funding. Robert G. Cooper developed the discipline in the mid-1980s from studies of industrial product launches; Stage-Gate® is his named methodology and a registered trademark of Stage-Gate Inc. Each gate exists to stop a weak proposition before it consumes the heavier capital of the next stage. That protection is genuinely needed: in Cooper’s 2024 review of new-product development performance, only about 30% of projects approved to enter development ultimately succeed commercially.

In stable, capital-intensive environments where a mistaken build is ruinous and a six-month delay is survivable, that trade-off is sound. It reverses when being slow costs more than a bounded test — and the structure never notices, because nothing in a gate review measures the delay the gate itself adds.

Three ways a legacy gate process quietly becomes the bottleneck

When a stage-gate system ages without being redesigned, it slows execution through three mechanisms that look like prudence from inside the committee room:

1. Decisions become calendar events rather than readiness triggers.When funding is released only at scheduled monthly or quarterly gates, a project ready in week three waits until week nine for permission to proceed. The waiting develops nothing, and no management report records it as a cost.
2. Gate reviews inspect document completion rather than risk reduction.Over time, each past mistake adds a mandatory template to the gate pack. A project team can pass every gate on schedule by completing the paperwork while the underlying commercial proposition weakens.
3. The “Sand Trap”: demanding certainty where only assumptions exist.As Rita Gunther McGrath and Ian C. MacMillan showed in their work on discovery-driven planning (Harvard Business Review, 1995), a line extension has a low assumption-to-knowledge ratio because historical data exists; a novel proposition has a high ratio because the data cannot exist yet. When Gate 1 demands a five-year financial forecast from both, teams either retreat to safe line extensions or fabricate spreadsheets out of guesses just to clear the gate. (Field note 04 covers that strategic drift.)

How to keep the financial control and remove the constraint

Organisations that abolish their gates in the name of speed usually rediscover why they existed. Cooper has not abolished them either: his later work describes scaled-down tracks for smaller projects and, from 2016, Agile–Stage-Gate hybrids that run short sprints inside the stages; in six manufacturers using the hybrid, interviewees estimated about 30% faster time to market. Those are management estimates, not audited trials, but the direction is clear.

1. Match the evidence bar to the size of the commitment.A small, bounded test does not need the governance pack of a full launch. Set the bar by what is financially at risk in the next stage, not by the stage number.
2. Decide when the work is ready, not when the calendar turns.If the agreed test evidence exists, waiting four weeks for a scheduled committee adds cost and zero information.
3. Invert the early gate question from “Prove it will work” to “What would have to be true?”Replace five-year forecasts at Gates 1 and 2 with a one-page assumption card: which assumption could kill this idea, what is the cheapest way to test it in four to six weeks, and what result will make us stop?

What transforming legacy processes looks like in practice: three cases

A process constraint is not always a committee meeting. Sometimes the check itself sits in the wrong place in a physical workflow, sometimes stages wait on an inherited serial order, and sometimes a long R&D cycle can be bypassed by adapting a mechanism another industry has already proved.

1. When the checkpoint sits after the irreversible step (Case 06 · Client-measured).A gate asks whether a stage is complete, never whether the check itself is in the right place. Our client, an automotive plastic-injection plant (Case 06), inspected parts at the end of its line, after colouring — the one step that cannot be undone — so every reject was found after the material had become unrecyclable waste. Following a line walk-through with Bold Group, the client added an inspection gate immediately before colouring. Rejected pre-colour pieces now return to the melt, and the client’s own accounting shows the annual cost of waste down by about 75%, from about ฿180 million to ฿45 million (50% colouring avoided plus 25% raw-material buy-back).
2. When stages wait on an inherited serial sequence (Case 02 · Client-measured).At our client, an industrial turbine-maintenance business (Case 02), revenue was capped by the length of the overhaul window. Disassembly, inspection, sign-offs, permits and reassembly ran strictly in series. Challenging which steps genuinely depended on the physical completion of the stage before them showed that the serial order had been inherited rather than dictated by the machine. The client now runs the revised sequence with the crews and equipment it already had.
3. When cross-industry transfer bypasses a long R&D cycle (Case 05 · Client-implemented).Our client, a prefabricated wooden staircase manufacturer supported under an NSTDA / I-TAP programme grant (Case 05), was paying to replace stair panels scratched by subcontractors and visitors during the exposure window between installation and homeowner handover. Rather than entering a long product or coatings R&D cycle, the design adapted a proven mechanism from the automotive industry — paint-protection film — into a polymer wrap applied at the factory and peeled off at final handover.

What this looks like in Thailand

In our work with Thai conglomerates and listed groups, the gate is almost always the monthly management or board committee, and the meeting calendar sets the pace far more than the evidence does. A proposal that misses one monthly cut-off waits four to six weeks. Furthermore, because having a proposal rejected in a formal committee can be experienced as a loss of face for the team and its sponsor, managers over-prepare paperwork for months beforehand, and committees rarely issue clean stops — asking teams instead to “come back next month with more data.” Separating small discovery approvals from full committee sittings removes both the queue and the defensive paperwork.

Where to start on Monday

Run three diagnostic checks on your current process this week:

1. Split elapsed time on your last five projects into working versus waiting.Count how many calendar days each project spent executing tests versus waiting for a pre-read, a committee date, or a sign-off.
2. Audit Gate 1 and Gate 2 templates for premature certainty.Remove five-year financial spreadsheets from early discovery gates and replace them with a one-page assumption test card.
3. Check whether operational gates sit ahead of the irreversible cost.Identify the exact step in your production or purchasing flow where cost cannot be undone, and verify that your quality or approval gate sits immediately ahead of it.

Where this does not apply

Where regulation, clinical safety certification or a customer contract sets the mandatory sequence, the gate cannot be designed away. The useful test is which gates are genuine external requirements and which are internal habits that hardened into rules over time.