Stage-Gate Is Not Dead, It Just Needs a Portfolio Layer

Karthick Nethaji Kaleeswaran
Director of Products | Strategy Consultant

---

Published Date: March 30, 2026

TL;DR

Stage-gate is still the most widely used New Product Development (NPD) framework in enterprise organizations and it remains genuinely valuable for governing how a product is developed. The problem is it was never designed to answer the portfolio question: given everything else competing for resources right now, should this idea proceed at all? That question requires a portfolio governance layer above stage-gate, not a replacement for it.

Every few years, someone publishes an article declaring stage-gate dead. Agile killed it. Lean startup made it obsolete. Digital product development moved too fast for it to keep up. The arguments change. The declaration stays the same.

And yet stage-gate remains the most widely implemented NPD framework in enterprise organizations worldwide. Manufacturing companies use it. Technology firms use it. Consumer goods companies use it. Pharmaceutical organizations have built entire regulatory workflows around it. It is not dead. But it is being asked to do something it was never designed to do. And that mismatch — between what stage-gate can govern and what enterprise NPD actually requires — is where most product pipelines quietly break down.

What Stage-Gate Was Built to Do

Robert Cooper’s foundational stage-gate research in the 1980s addressed a specific problem: manufacturing companies were launching products without sufficient discipline in the development process. Ideas moved from concept to market without structured evaluation at key decision points. The result was waste — products that were technically completed but commercially wrong.

Stage-gate solved that problem by introducing sequential development stages with formal review gates between them. Each gate required specific deliverables before the project could advance. The model brought discipline to product development at a time when it was badly needed. It still brings that discipline today.

Stage-gate creates structure where there would otherwise be chaos. It forces articulation of the product concept, the market case, the development plan, and the commercial strategy at the right points in the process. Those are not small things. The criticism of stage-gate is not that it does these things poorly. It is that it was never designed to do something else entirely — something that enterprise portfolios now desperately need.

The Question Stage-Gate Cannot Answer

Here is the question that determines whether an NPD idea should proceed: Given our declared strategic priorities, our current resource commitments, and everything else already approved in the portfolio, should this idea proceed now? Stage-gate cannot answer that question. It was not built to. Stage-gate operates within a project. It governs the stages of development from concept to launch. It assesses whether the idea is ready to advance to the next stage. What it does not do — what it has never done — is evaluate the idea against the rest of the portfolio simultaneously.

To answer the portfolio question, you need information that sits outside the stage-gate model:

• What is currently consuming engineering capacity across all active projects?
• Which strategic objectives have been declared for the current planning period, and which ideas directly advance them?
• What is the risk-adjusted return of this idea relative to the next-best alternative use of the same capital?
• Which existing commitments would need to be deferred to create the capacity this idea requires?

None of that data lives inside a stage-gate process. All of it is essential to making a sound investment decision for a portfolio. Stage-gate reviews without portfolio data miss the fundamental gate question: given everything else competing right now, should this idea proceed? That question cannot be answered solely by the product function.

Why the Confusion Happens

The reason stage-gate gets blamed for portfolio failures it didn’t cause is understandable. In most organizations, the stage-gate is the only formal NPD governance mechanism. So when the portfolio produces wrong results — too many half-executed projects, strategic misalignment, resource conflicts at kickoff — the natural instinct is to fix or replace the thing that’s visible. But this problem is not caused by the stage-gate. It is caused by the absence of a portfolio layer above it.

The distinction matters because it changes the solution. If stage-gate is broken, replace it. If stage-gate is complete but missing a governance layer above it, add the layer and keep the discipline stage-gate provides.

“We cannot solve our problems with the same thinking. We used when we created them.”

Albert Einstein

 

What the Portfolio Layer Actually Does

The portfolio layer sits above stage-gate. It does not replace any of the development stages or gate reviews. It adds three capabilities that stage-gate structurally cannot provide.

1. Strategic Alignment Before the First Gate

Before an idea enters the stage-gate process, it should be evaluated against the organization’s current strategic priorities. This means structured scoring against the active OKR tree or strategic objective framework for the current planning period — not a self-reported alignment. Ideas that don’t connect to strategic priorities aren’t necessarily rejected. But they require an explicit rationale from a named portfolio owner before they consume gate review time. This is the filter that prevents the pipeline from filling with strategically disconnected work.

2. Resource Availability as a Gate Condition

At every gate where significant resource commitment is required — particularly the gate that moves an idea from approved concept to active development — the portfolio layer checks current capacity against the active project portfolio. If required resources are fully committed, the gate has three options: defer the idea to a specific future window, approve with an explicit reprioritization of a lower-priority existing project, or hold. What it cannot do is approve with an informal “we’ll sort resources out at kickoff.” That single governance rule eliminates the most common cause of post-approval NPD failure.

3. Portfolio-Level Comparative Evaluation

Individual stage-gate reviews evaluate whether an idea is good enough to proceed. The portfolio layer asks a different question: is this idea the best use of the capacity it requires, relative to everything else in the pipeline? That comparative evaluation requires a 2×2 value-effort prioritization model — scoring all active submissions on the same criteria simultaneously, so gate decisions are made with visibility into the full pipeline, not just the idea being presented.

The Architecture: Stage-Gate Plus Portfolio Layer

The two systems are not alternatives. They are complementary layers operating at different levels of the organization. The portfolio governance layer handles strategic alignment, resource availability, comparative scoring, investment merit, gate approval, and capacity confirmation. Only approved ideas enter the stage-gate process, which then governs concept, development, testing, launch, and post-launch review.

The portfolio layer determines which ideas deserve to enter the stage-gate process. The stage-gate process governs how approved ideas are developed through to launch. Neither layer can do the other’s job. Both are necessary. According to PMI’s Pulse of the Profession, organizations that undervalue project management as a strategic competency experience 67% more project failures than those that treat governance as a core discipline.

Where Each Layer Begins and Ends

• Stage-Gate governs the how of product development. It evaluates whether an idea can be built, whether the plan is robust, and whether the execution path is sound.
• Portfolio management governs the what and why. It evaluates whether an idea should be pursued at all, based on strategic alignment, capacity constraints, comparative value, and risk-adjusted return.

Both questions matter. Only one of them is currently being asked in most enterprise NPD processes.

Quick Audit: Do You Have a Portfolio Layer Above Stage-Gate?

Three or more “No / Partial” answers mean your stage-gate process is running without a portfolio layer. The development discipline exists. Investment governance does not.