Stage-gate processes were not invented for drug development. They were borrowed from manufacturing and product engineering — domains where the key assumptions hold: requirements are knowable in advance, specifications can be fixed early, and failure at a gate is avoidable with sufficient planning and rigour.
None of those assumptions hold in pharmaceutical R&D.
Drug development is defined by irreducible uncertainty. A compound that looks promising at Phase I may reveal unexpected toxicity in Phase II. A trial that is perfectly executed may fail to meet its primary endpoint for reasons that no amount of process rigour could have predicted. The science does not behave according to a Gantt chart.
"Stage-gate processes were designed for predictability. Drug development is not predictable. The organisations that outperform are those that have built governance frameworks light enough to move fast and robust enough to catch the things that matter."
Yet across the industry, I have repeatedly seen organisations treat stage gates as though predictability were the norm — building elaborate approval processes that add calendar time, governance overhead, and organisational friction without materially improving decision quality.
What Rigid Stage Gates Actually Cost
The direct cost of decision latency is well documented — my analysis of governance meeting cadence across pharma R&D suggests that 12 to 17 months of development time per programme is spent waiting for committees to meet, not waiting for science to resolve. But the indirect costs are equally significant and less frequently measured.
Rigid stage gates discourage the kind of adaptive, iterative decision-making that modern drug development requires. When a team knows that the next governance window is six weeks away, they optimise for the gate rather than for the science. They add data collection points "just in case," extend exploratory endpoints to ensure they have something to show, and delay escalating emerging risks because the escalation pathway is locked to the governance calendar.
The result is a system that is simultaneously too slow at the level of formal decisions and too fast at the level of scientific exploration — teams rushing science to hit artificial milestones while decisions queue behind calendar constraints.
The Origins Problem
Stage-gate methodology was formalised by Robert Cooper in the 1980s for new product development in manufacturing industries. Its core logic — define phases, set criteria, make go/no-go decisions at defined points — is sound when applied to systems where output can be specified and failure modes are known. In those contexts, gates genuinely add quality by preventing premature advancement of immature work.
The problem is not the concept of governance checkpoints. It is the rigidity with which they are applied in contexts they were never designed for. When a gene therapy programme is held to the same gate cadence and criteria as a small molecule programme, or when governance committees evaluate early discovery data using the same frameworks applied to regulatory submissions, the process has become the goal rather than the instrument.
What Adaptive Governance Looks Like
The organisations pulling ahead on development timelines have not abandoned governance. They have redesigned it around three principles:
The majority of development decisions should be made by the teams closest to the data — the scientists, clinicians, and programme managers running the programme. Governance committees should be reserved for decisions that genuinely require senior input: resource allocation, portfolio trade-offs, strategic pivots, and go/no-go decisions with material commercial consequences. Moving 60 to 70% of decisions to asset teams is not a reduction in governance quality. It is a concentration of governance attention on the decisions that actually warrant it.
Fixed monthly or quarterly governance cycles create artificial synchronisation between the calendar and the science. Leading organisations have moved to more frequent, shorter governance windows — bi-weekly or weekly — that allow decisions to be made when the data is ready, not when the calendar permits. Some have introduced dynamic or on-demand review mechanisms for time-sensitive decisions that cannot wait for the next scheduled session.
Rigid stage gates often apply fixed criteria across programmes regardless of their stage, therapeutic area, or modality. Adaptive governance sets criteria that reflect the specific uncertainty profile of each programme — what does the team need to know to make the next decision, and what is the minimum evidence required to make it with acceptable confidence? This is a fundamentally different question from "have we met the standard criteria for this gate?"
The Rigour Argument
The most common objection to adaptive governance is that faster decision-making sacrifices rigour. This objection assumes that the current model is rigorous — which it often is not.
Rigour comes from the quality of the decision process: the evidence considered, the expertise applied, the risks identified, and the accountability for outcomes. None of these are functions of how long a decision takes to reach a committee. A governance model that concentrates expert attention on genuinely difficult decisions, provides real-time visibility into programme risk, and holds teams accountable for outcomes is more rigorous — not less — than one that routes every decision through a monthly calendar.
The goal is not to abandon rigour. It is to direct rigour at the things that matter — scientific risk, regulatory readiness, portfolio value — and remove it from the things that do not: calendar dates, committee schedules, and the comfort of process for its own sake. The patients at the end of the development pipeline are not served by governance elegance. They are served by speed, decision quality, and the organisational courage to distinguish between the two.