Stage gate new product development

New-product development turns uncertain ideas into progressively stronger investment cases. A stage-gate process divides that work into stages separated by decision points. During each stage, a cross-functional team gathers evidence and reduces a defined set of uncertainties. At each gate, authorised decision-makers review the evidence, decide whether the opportunity still deserves investment and allocate the resources required for the next stage.

When to use it

Use a stage-gate process to manage the development and launch of products, services, technologies or substantial product changes when:

• investment and uncertainty increase as development proceeds;
• technical, customer, commercial, operational and regulatory evidence must be integrated;
• several opportunities compete for limited resources;
• explicit go, hold, recycle or stop decisions are needed; or
• senior sponsors need a consistent governance view across an innovation portfolio.

Tailor the process to the risk and novelty of the project. A minor packaging change should not carry the same evidence burden as a new medical device, industrial platform or business model. For highly uncertain digital work, stages can include rapid experiments and agile delivery; governance does not require a slow, linear waterfall.

Origins

Phased project reviews existed before the modern new-product model, including staged investment decisions in large engineering and chemical projects. Robert G. Cooper developed the best-known Stage-Gate® system from empirical research comparing successful and unsuccessful product-development projects. He introduced the model publicly in nineteen eighty-six, and the name Stage-Gate came into use in the late 1980s. Cooper and Scott J. Edgett subsequently refined the approach through several generations, adding portfolio management, differentiated pathways and more adaptive execution.

Stage-Gate® is a registered system associated with Stage-Gate International. “Phase-gate” and “gated development” are also used more generally for related staged-governance processes.

What it is

A conventional process begins with discovery and an initial idea screen, followed by five stages. Each stage contains work; each gate is a governance decision.

Idea screen

Ideas may come from customer research, employees, partners, technology development, competitors, service failures or changes in regulation. The initial screen asks whether the opportunity is strategically relevant, plausibly valuable and worth a small amount of investigation. It should remove obvious mismatches without demanding the evidence that only later work can create.

Stage 1: concept creation

Conduct a preliminary technical and market assessment. Clarify the customer problem, target segment, existing alternatives, strategic fit, rough feasibility and major uncertainties. The output is a concise opportunity statement and a recommendation for deeper investigation.

Stage 2: business case

Define the product or service concept, value proposition, target market, requirements, route to market, development plan and financial case. Test the assumptions behind demand, price, cost, capability and risk. The business case is a living hypothesis set, not a promise disguised as a forecast.

Stage 3: product development

Design and build the product, service and associated operating system. Development includes more than the technical artefact: manufacturing or delivery processes, supply, data, support, compliance, sales enablement and launch preparation must progress together.

Stage 4: test and validation

Verify technical performance, safety, quality, customer acceptance, operational readiness and commercial assumptions. Testing may include prototypes, pilots, controlled market trials, pre-production runs and validation of the economics at realistic scale.

Stage 5: launch and monitor

Move into full production or service delivery, execute the go-to-market plan and monitor adoption, quality, economics and customer outcomes. A post-launch review compares results with the decision assumptions and captures lessons for the portfolio and process.

Developments of the model

A useful gate has four elements:

1. Defined deliverables: the evidence the project team brings.
2. Explicit criteria: the strategic, customer, technical, financial and risk tests used to judge it.
3. A decision: go, conditional go, hold, recycle for more work, or stop.
4. Resource commitment: people, money and sponsor support for the next stage.

A gate is not a presentation ritual. If every project passes regardless of evidence, the organisation has stages but no gates.