Research from Products That Count and Capgemini established that 30% of Fortune 1000 CEOs will be former CPOs by 2027 — up from 5% today. Egon Zehnder calls it the new pipeline.
Nobody asks why software is failing.
The previous two modules established mission and measures as the first two disciplines. Both are irreducibly dependent on a third thing that almost no software organisation has formalised.
The Dependency Chain
The Four Ms are not four parallel disciplines. They are a chain. Each depends on the one before it.
| Module | Discipline | What it governs | What depends on it |
|---|---|---|---|
| M1a | Mission | Why the organisation exists | Measures, NPD Framework, empowerment, management |
| M1b | Measures | Whether the mission is being served | NPD Framework stages, gate criteria, investment logic |
| M1c | NPD Framework | How a mission becomes a legally operable product | Empowerment (the structural prerequisite), management |
| M1d | Manpower & Empowerment | What people can do within a defined operating space | Management (becomes lightweight coordination) |
| M1e | Management | Alignment and obstacle removal | Compounds into the Architectural Formula |
What the NPD Framework Is
The NPD Framework is not a product methodology. It is not Agile. It is not a roadmap process. It is not a discovery framework.
It is the governance architecture connecting mission-derived intent to a legally operable product in users’ hands — cradle to grave.
Every mature product organisation has this knowledge. Almost none have written it down. It exists in the heads of experienced practitioners — the product directors, the general counsels, the heads of commercial who have built things before and carry the accumulated scar tissue of doing it without a map. It dies when they leave.
The closest analogy in the industry is ISO 20000:01 for IT service management — the standard that made the dark arts of service delivery transmissible, auditable, and organisationally independent of the individuals who once held it all in memory. The NPD Framework is that standard for product governance. Nobody has written it yet. Every organisation that has survived long enough has reinvented it privately.
Stage, Not Step
The critical distinction is between a step and a stage.
A step asks
Have we done the work?
A stage asks
Are we ready to proceed?
A team can complete every task on a project plan, tick every box on a RACI, and still not be at the maturity required to proceed to the next stage. The gate tests readiness. Readiness is a function of the mission, the measures at that stage, and the cross-functional sign-off from every contributing owner. Not just product.
The Six Stages
A full NPD Framework runs from Strategic Intent to Market Operation. Each stage has defined entry criteria, defined contributing owners, and a defined gate that must be passed before the next stage begins. The stages describe maturity levels, not activities.
Stage 01 — Strategic Intent. Mission alignment confirmed. The concept has a right to exist against the mission. A business case hypothesis is formed but not yet sanctioned.
Stage 02 — Business Case. Commercial viability and investment logic are sanctioned by the appropriate governance body. This is not a pitch — it is a gate with defined criteria and defined authority.
Stage 03 — Design & Build. Architecture, standard operating procedures, and the cross-functional RACI are defined. Every contributing function is engaged at this stage, not discovered at Stage 05.
Stage 04 — Legal & Compliance. Regulatory approval and licensing policy are confirmed. In insurance, this is the stage most organisations reach last and treat as a blocker. In a functioning NPD Framework, Legal is a contributing owner from Stage 01 and a gate authority at Stage 04. The difference is structural.
Stage 05 — Commercial Approval. Pricing, distribution, and partner governance are confirmed. The commercial model is sanctioned. No product goes to market without this gate.
Stage 06 — Market Operation. The product is handed to Product Lifecycle Management. The NPD cycle is complete. In-life governance begins.
The Cross-Functional Architecture
The NPD Framework resolves a confusion that has cost the software industry an extraordinary amount of value: who owns the product lifecycle.
The answer is product. Not Legal. Not Commercial. Not Technology. Not Operations. Product is the chief owner of the NPD Framework and responsible for its integrity from Stage 01 to Stage 06.
Every other function is a contributing owner at defined stages with defined authority. Legal does not block at Stage 05 because Legal had a defined role at Stage 01 and gate authority at Stage 04. Commercial does not discover the product at launch because Commercial had a seat at Stage 03 and gate authority at Stage 05.
Engineer
Job role, RACI, delivery stage, technical gate. Governed by NPD Framework at Stage 03.
Legal input
Contributing owner at Stage 01, gate authority at Stage 04. Not a late blocker.
Third-party data
Commercial approval, legal sign-off, usage policy. Governed identically to any other resource.
AI capability
SOP, licensing, usage policy, output standards. Governed at Stage 03 by the same framework. Not a special governance event.
That last point matters. The conversation about AI governance in product organisations is, almost without exception, a conversation about the absence of any governance framework at all. AI is not a special resource requiring a special governance structure. It is a resource like any other — engineer, legal input, third-party data — that requires the same things any resource requires: defined contribution, defined authority, defined stage, defined gate. The chaos is not an AI problem. It is a pre-existing governance vacancy that AI has made visible.
The CPO-to-CEO Trajectory Is Structural
Egon Zehnder’s framing of the CPO-to-CEO pipeline as a career story misses the more important structural point. The CPO who has built and operated a functioning NPD Framework has already been doing the CEO’s job in the only way that matters. They have connected mission-derived intent to a legally operable product. They have owned the lifecycle through which the business generates value. They have defined accountability across every function at every stage. They have made the outcome repeatable and independent of the individuals who happened to be in the room.
The title is the formal recognition of a responsibility already carried.
The Evidence in Real Time
The SaaSpocalypse was not a technology event. It was a value event — capital interrogating the defensibility of the moat and finding nothing behind it. The indictment is precise: product development was treated as a backlog, governed by product vision rather than business mission. No NPD Framework separated in-life enhancement from genuine new product development. No gate structure gave the board two populations with different measures and different investment logic. Everything looked like delivery. Velocity was the proxy for strategic progress.
Formalise the dark arts. That is the work.
You can resolve the mission. Build accurate measures. Deploy the best people. And still fail — because there is no transmissible, auditable architecture governing the translation of all three into a product that compounds.
#ProductLeadership #CPO #ProductStrategy #ProductManagement #NPD #NPDFramework #ProductGovernance #SaaSpocalypse #AI #EnterpriseTransformation
LinkedIn Carousel
M1c — The Governance Nobody Formalised — 10-slide summary
© John Bowers 2026. All rights reserved. The Four Ms operating model, the New Product Development Framework, and the Architectural Formula (X×Y×Z×WN) are proprietary methodologies. The Product Leader’s Playbook is an original work in progress. Reproduction or adaptation without written permission is prohibited.