Product Development
A 19-stage framework for new product development that separates in-life management from genuine innovation, enforces mission governance at every gate, and calibrates measures to lifecycle stage.
Most software organisations have no structural separation between managing what exists and developing what must exist. Everything is treated as delivery. The board watches velocity and calls it governance.
The NPD Framework enforces the separation structurally. The moment you have a stage address for every item in the portfolio, you have two distinct populations with different measures, different investment logic, different authority levels, and different board-level reporting.
The stage does not determine what must be measured. The mission does that. The stage determines the instruments appropriate to measuring it.
PLM — In-Life Management
Governs what already exists.
Delivery speed. Velocity. Feature enhancement. Release cadence. Cycle time. These are legitimate measures for the in-life population. They tell the board whether what exists is being managed well.
NPD — New Product Development
Governs what must exist.
Stage-gate progression. Mission gap closure. Investment thesis validation. Gate authority. These govern the new product population. They tell the board whether what is being built serves the mission.
Mission
Defines the destination. Fixed, enduring, independent of market conditions. The mission is not reviewed at sprint planning. It governs from above the product.
The Mission Gap
The gap between where the organisation currently is and where the mission requires it to be. This gap determines what must be measured. Not the OKR framework. Not the sprint review. The mission gap.
The Stage
The lifecycle and maturity stage of each product calibrates how the mission gap is measured. A concept-stage initiative is measured differently from a late-stage NPD programme. The stage determines the instruments; the mission determines what they are measuring.
The Gate
Uses all three to decide whether anything moves. An initiative passes a gate not by delivering well but by demonstrating that what is being built advances the mission at an appropriate stage of development.
Nokia
Excellent delivery metrics. Handsets shipped. Cycle times strong. No board-level measure ever asked whether the development pipeline still served why the business existed. When it did not, there was nothing to replace it.
Apple
Ran a fifteen-year chip programme no PLM metric would have approved. At every stage gate: does this advance our capacity to create tools that extend human capability? Mission measure. Gate-governed. Fifteen-year return.
Velocity is a legitimate PLM measure.
It is an actively dangerous NPD measure — it tells the board that things are moving without telling them whether what moves serves the mission.
© John Bowers 2026. The NPD Framework is a proprietary 19-stage methodology. Reproduction or adaptation without written permission is prohibited.