Stage Gate Process: Why Most Product Launches Fail Before They Start

The stage gate process is a structured framework for new product development that divides the work into discrete stages separated by decision points, called gates, where a project is either advanced, revised, or killed. It gives marketing and commercial teams a disciplined way to allocate resources, manage risk, and avoid the single most expensive mistake in product development: launching something the market does not want.

Most product launches do not fail at launch. They fail six months earlier, when someone with seniority overrode a gate decision because they were excited about the idea. The process exists precisely to prevent that.

What Is the Stage Gate Process and Where Did It Come From?

The framework was formalised by Robert Cooper in the 1980s and published in detail through his work on product innovation management. The core idea is straightforward: break a complex, uncertain process into manageable stages, and at the end of each stage, make a deliberate decision about whether to continue. Each gate has defined deliverables, criteria, and decision-makers. Nothing moves forward without passing through.

The original model had five stages: scoping, building the business case, development, testing and validation, and launch. Most organisations adapt this to fit their own structure, industry, and risk tolerance. A fast-moving consumer goods company will run a different version than a pharmaceutical business, but the underlying logic is the same.

What makes the model durable is not its elegance. It is the fact that it solves a real problem: organisations consistently over-invest in bad ideas because they lack a formal mechanism to stop them. Without gates, projects accumulate momentum, political capital, and sunk cost. By the time the flaws become obvious, too many people have too much invested to call it off.

If you are thinking about how stage gate fits within a broader commercial growth framework, the Go-To-Market and Growth Strategy hub covers the wider set of decisions that sit around it, from market entry to scaling.

What Happens at Each Stage?

Stage one is discovery or scoping. This is where you define the opportunity: what problem are you solving, for whom, and why now. The output is not a product spec. It is a clear articulation of the market problem and a preliminary view on commercial viability. Marketing should be doing real work here, not just attending meetings. Customer interviews, market sizing, competitive mapping, and early positioning hypotheses all belong at this stage.

Stage two is building the business case. This is where the idea gets stress-tested properly. You are modelling revenue scenarios, costing the development, defining the target customer with specificity, and producing a go-to-market outline. The gate at the end of this stage is often the most important in the entire process. If the numbers do not work here, they will not work at launch. I have sat in enough agency pitches and client planning sessions to know that the business case stage is where wishful thinking either gets corrected or gets locked in.

Stage three is development. The product gets built. Marketing’s role here is often underestimated. This is when you should be developing your channel strategy, building your launch assets, testing messaging with real customers, and validating your pricing assumptions. Waiting until stage four to start this work is one of the most common and most avoidable mistakes in product development.

Stage four is testing and validation. The product is tested in controlled conditions, whether that is a pilot market, a beta programme, or a limited release. The commercial assumptions from stage two get tested against reality. This is where you find out whether your customer acquisition cost assumptions were optimistic and whether your conversion rates hold up outside a spreadsheet.

Stage five is launch. Full commercialisation. By this point, if the process has been followed properly, there should be very few surprises. The launch plan should already exist in a near-final state, the channel economics should be understood, and the team should be executing against a plan that has been refined through four prior stages of learning.

What Makes a Gate Decision Meaningful?

Gates are only useful if they have teeth. A gate that always says yes is not a gate. It is a calendar event with a slide deck.

I ran a turnaround at a mid-size agency where one of the structural problems was exactly this. Projects moved through internal approval stages without anyone genuinely challenging the commercial assumptions. The result was a pipeline full of work that was either under-priced, poorly scoped, or built on client briefs that had not been interrogated. The fix was not complicated. We defined what each approval stage required, who had authority to kill a project, and what criteria had to be met. The discomfort of killing a few projects early was nothing compared to the cost of delivering them badly.

For gate decisions to mean something, three things need to be true. First, the criteria must be defined in advance. If you write the success criteria after seeing the results, you are not running a gate process, you are running a rationalisation process. Second, the gatekeepers must have genuine authority to say no. If every gate decision escalates to the same senior person who always says yes, the gates are decorative. Third, the decision must be documented. What was decided, on what basis, and by whom. This matters not just for governance but for organisational learning.

Where Does Marketing Fit in Stage Gate?

Marketing’s role in stage gate is frequently misunderstood, even by marketers. The default assumption in many organisations is that marketing shows up at stage five to execute the launch. This is wrong, and it is expensive.

Marketing should be embedded from stage one. The reason is simple: most of the decisions that determine whether a product succeeds commercially are made in the first two stages, not the last one. Market sizing, customer segmentation, positioning, pricing strategy, channel selection, and competitive differentiation are all stage one and two questions. If marketing is not in the room when those decisions are made, the launch team inherits a set of assumptions they had no hand in validating.

I spent a period judging the Effie Awards, which are specifically focused on marketing effectiveness rather than creative craft. What separated the winning entries from the also-rans was almost never the quality of the creative execution. It was the quality of the thinking that happened before any creative work started. The briefs were sharper. The market understanding was deeper. The commercial objectives were clearer. That kind of thinking does not happen in a three-week pre-launch sprint. It happens across the full development cycle.

Specifically, marketing’s contribution across stages looks like this. In discovery: customer research, market sizing, initial positioning hypotheses. In business case: go-to-market outline, channel economics, pricing research, competitive analysis. In development: messaging testing, channel strategy, asset development, early audience building. In testing: campaign pilots, conversion rate validation, channel mix optimisation. In launch: full execution against a plan that has been refined through the prior four stages.

How Does Stage Gate Interact With Agile Development?

This is where a lot of the debate in product and marketing circles sits. Agile methodologies emphasise speed, iteration, and continuous delivery. Stage gate emphasises structured decision-making and risk management. On the surface they look like opposites. In practice, they are complementary.

The most functional approach I have seen is to run agile sprints within stages, and gate reviews at the boundaries between stages. The agile process handles the day-to-day development work: the iterations, the user stories, the sprint reviews. The gate process handles the bigger commercial questions: are we still solving the right problem, do the numbers still work, should we continue.

Forrester’s research on agile scaling points to the tension many organisations face when trying to apply agile principles at scale without losing governance and commercial rigour. Stage gate provides that governance layer without disrupting the iterative work happening inside each stage.

The failure mode to avoid is treating the two frameworks as mutually exclusive. Some product teams adopt agile and then abandon any form of structured gate review, which removes the commercial discipline from the process entirely. Others maintain rigid stage gate without any iterative flexibility inside stages, which slows development and prevents learning. Neither extreme serves the business well.

What Are the Most Common Failure Modes?

The first and most common failure mode is the zombie project. This is a product development effort that has failed its gate criteria but continues anyway because someone senior wants it to. The project shuffles forward, consuming resources, blocking better opportunities, and eventually launching into the market without the commercial foundations it needs. I have seen this in agency contexts and in client-side organisations. The fix is not process. It is culture. Senior leaders have to be willing to kill their own ideas when the evidence says to.

The second failure mode is treating the business case as a one-time exercise. Market conditions change. Customer behaviour shifts. Competitive dynamics evolve. A business case written in stage two should be revisited at every subsequent gate. If the assumptions that justified the project no longer hold, that is a gate decision, not an inconvenient footnote.

The third failure mode is under-resourcing the early stages. Discovery and business case development are often treated as cheap, fast activities because no product is being built yet. This is a false economy. The quality of the work done in stages one and two determines the quality of every decision that follows. Cutting corners here is where most product failures actually begin, not at launch.

The fourth failure mode is confusing activity with progress. Stage gate can become a bureaucratic exercise where teams produce the required deliverables without genuinely engaging with the questions those deliverables are supposed to answer. A customer research report that confirms the assumptions the team already had is not validation. It is comfort-seeking dressed up as diligence.

Understanding how stage gate connects to broader market entry decisions is worth exploring. Semrush’s overview of market penetration strategy covers the commercial mechanics of entering an existing market, which often runs in parallel with late-stage product development decisions.

How Should Marketing Teams Use Stage Gate to Improve Launch Performance?

The practical answer is to treat the stage gate process as a brief-building exercise as much as a project management tool. Every stage should produce sharper answers to the fundamental marketing questions: who is the customer, what problem are we solving for them, why should they choose us, and how will we reach them at scale.

By the time you reach stage five, you should have a launch brief that has been tested, revised, and validated across four prior stages of customer and commercial learning. That brief should be specific about target audience, channel mix, messaging hierarchy, pricing rationale, and success metrics. If it is not, the process has not been working properly.

One practical tool worth building into the stage gate process is a structured assumption log. At each gate, document the key assumptions the project is resting on, the evidence for and against each one, and the conditions under which you would revise or abandon the assumption. This creates a live record of the commercial logic underpinning the project and forces the team to confront disconfirming evidence rather than ignore it.

Channel strategy deserves particular attention at the testing stage. Growth tools and channel testing frameworks can help teams move quickly through channel validation without waiting for a full launch to find out what works. The goal at stage four is not to achieve scale. It is to validate the unit economics before committing to full commercialisation.

For consumer-facing products, creator and influencer channels are increasingly part of the validation toolkit. Later’s work on creator-led go-to-market is a useful reference for teams building that channel into their launch strategy, particularly for testing message resonance before committing to paid media at scale.

BCG’s writing on go-to-market strategy and brand alignment makes a related point about the importance of cross-functional coherence in commercial launches. Stage gate provides the structural mechanism for that coherence, but only if the right people are in the room at each gate.

How Do You Adapt Stage Gate for Smaller Teams?

The honest answer is that you compress it, but you do not skip it. Smaller teams often resist stage gate because it feels like a large-company process. The paperwork, the governance structures, the cross-functional review committees. None of that is essential to the underlying logic. What is essential is the discipline of making explicit decisions at defined points, rather than letting projects drift forward on momentum.

For a small product team, a compressed stage gate might look like this: a one-page discovery summary reviewed by the founding team, a two-page business case with three financial scenarios reviewed before any development starts, a mid-development review at the halfway point, a structured pilot with defined success criteria, and a launch readiness review before full go-live. The documents are lighter. The decisions are the same.

What you cannot compress is the quality of thinking. A one-page business case that genuinely stress-tests the commercial assumptions is more valuable than a twenty-page document that papers over the uncertainties with optimistic projections. I have seen both. The length is not the point.

The growth strategy thinking that informs how you scale after a successful gate process is covered in more depth across the Go-To-Market and Growth Strategy hub, including how to think about channel selection, market entry sequencing, and the commercial decisions that sit between a validated product and a scaled business.

BCG’s analysis of evolving go-to-market models is worth reading for teams thinking about how commercial strategy needs to adapt as a product moves from validation to scale. The stage gate process gets you to launch. What happens after launch is a different set of decisions.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions