The Four Ms is a subset of The Product Leader’s Playbook — a series that surgically reviews the recent history of software valuation collapse, articulating what occurred, why it occurred, and how to ensure it does not happen to your business. In this series we explore four interconnected disciplines: Mission, Measures, Manpower & Empowerment, and Management. When structurally embedded and enforced through governance, they form the architecture that separates the companies compounding value from those watching it erode.
The series opens with a specific indictment. Most of the organisations caught in the $285 billion correction did not lack ambition, investment, or talented people. What they lacked was a mission. In its place, they had a product vision — a description of what they currently built, how it worked, and who it served. That description was placed on a strategy deck, given a name, and called a mission. It is what M1a called the vision wearing the mission’s crown: specific enough to feel purposeful, broad enough to sound strategic, but ultimately a workflow with a motivational poster on it.
The damage does not stop there — and this is what this module exists to explain. A workflow mission produces workflow governance: code velocity becomes the measure of progress, feature throughput becomes the definition of success, sprint completion becomes the evidence that the business is working. Workflow governance produces a workflow management cadence: backlog reviews, release planning, quarterly delivery milestones. And that cadence produces a product team that is genuinely, sincerely empowered — but empowered to ship faster, not to build anything that compounds. Every M multiplied the error of the one before it. The correction was not caused by a single broken thing. It was the structural consequence of four broken things cascading from one wrong starting point — and the financial metrics confirmed none of it until capital did.
That is what this series is correcting. Read the prior modules in sequence before continuing — the argument builds.
The argument so far
M0 established the scale of the correction and its cause. M1a named the upstream root: the mission was wrong before AI arrived. M1b followed the logic: if the mission is wrong, the measures derived from it cannot detect the structural decay beneath the strategy.
Which leaves a question these two pieces deliberately do not answer.
Inside every one of those $285 billion worth of businesses were talented, experienced, committed people. They knew the industry. Many of them could see problems forming. So why didn’t they do anything about it?
The answer is M1c. They could not act — not because they lacked ability, but because the structure they operated within gave them authority without orientation. They were empowered to do the wrong thing. Efficiently, sincerely, and with full conviction.
Before we talk about empowerment, look at who got it wrong
Chegg was a textbook rental and homework help platform. By 2022 it had fifteen years of student questions, worked solutions, and educational content. It had a large, capable team. It was hitting its targets. Every metric was green. Within twelve months of ChatGPT’s launch, it had lost half its subscribers and its market value had collapsed by over 90%.
The team hadn’t stopped working. They hadn’t suddenly become incompetent. They had been empowered — genuinely, sincerely — to build a content library. And they had built an excellent one. The problem was that a content library is something a competitor can replicate. What Chegg never built was something a competitor couldn’t: a system that got smarter from every student interaction. Every question answered, every worked solution completed, every learning outcome — none of it made the next answer better. The loop was open. The team were succeeding at the wrong thing, and the measures they were accountable to never told them otherwise.
Babylon Health had a genuinely ambitious mission: put an accessible and affordable health service in the hands of every person on Earth. The clinical engineering was real. The AI triage product was building genuine capability from patient interactions. The mission was pointing at the right destination.
But the measures the organisation ran on tracked appointment volumes, geographic expansion, and registered users. The clinical and governance talent inside the business knew what clinically meaningful progress looked like — they were not ignorant of the gap. They were empowered against expansion metrics. The authority they held was pointed at the commercial targets the investors required, not at the clinical intelligence the mission prescribed. When Babylon collapsed, it was not for want of talent or ambition. It was because the people best positioned to build the right thing were accountable to the wrong measures.
A strong mission failed to propagate because the empowerment structures beneath it were calibrated to the wrong destination.
Blockbuster held twenty years of rental transaction records. It knew what every customer had rented, when, and how often. That data existed in volume. What it never did was use it to get better. The next recommendation was not informed by the previous fifty million rentals. The late fee model — the thing the organisation was structured and empowered to protect — actively worked against the kind of customer intelligence Netflix was building simultaneously.
In 2008, Blockbuster was profitable. The financial metrics gave no warning. Netflix was already pulling away — not on product features, but on institutional intelligence. Blockbuster’s people were enforcing the revenue model. Netflix’s people were learning from every customer interaction. The divergence was architectural. The financial confirmation arrived three years later.
Management was the governing instrument. Revenue was the mission in practice, whatever the wall said. The cascade confirmed at full force — four Ms, all broken, all pointing in the same wrong direction.
The dependency chain nobody draws
The Four Ms are not a list. They are a sequence in which each stage is the enabling condition for the next. You cannot skip one and make the others work. You cannot reverse the order and reach the right destination. The sequence is invariant — it applies identically to a six-month startup and a sixty-year enterprise.
WeWork scored the minimum viable score across all four Ms. Management was built first — before mission, before measures, before empowerment had any structural content. The organisation was a management structure in search of a mission. At $47 billion peak valuation. The structural verdict was available at founding.
What empowerment actually requires
The mechanism that makes genuine empowerment possible is an NPD framework with governance gates. This is not a process document. It is the structural contract between the product function and every other part of the business — defining what each function is responsible for, at which stage of a product’s development, and to whose criteria they are accountable.
Product is the chief owner of the entire lifecycle — from strategic intent to market operation and beyond. Every contributing function holds a defined role within that framework. Not consulted. Not reviewed after the fact. Held.
- Product operates against a backlog disconnected from what the business needs to build
- People hit every target without building anything that compounds
- Legal surfaces at launch as a blocker rather than a defined stage participant
- Every real decision requires escalation — authority exists on paper only
- The gap between what is being built and what needs to be built widens invisibly
- Product managers pursue the mission without seeking permission — the framework defines what is expected at every stage
- Every function is accountable to product’s criteria, not its own interpretation
- Strategic intent is tested at every maturity gate, not reviewed after capital has priced the failure in
- Empowerment is structural — full authority within a defined space
How the framework sequences the business
At each governance gate, product defines the maturity criteria. Contributing functions are held to account against product’s definition. The sequence matters:
| Area | Their role within the framework |
|---|---|
| Product | Chief owner of the full lifecycle — from strategic intent to market operation and beyond. Sets the maturity criteria at every gate. Cradle to grave. |
| Build | Product owns build scope and acceptance criteria. Technology delivers within product’s defined boundary — not as a co-owner of scope. |
| Technology Operations | Product defines what operational readiness means before build completes. Technology Operations owns delivery of that definition — not the design of it. |
| Commercials | Product defines commercial readiness at each gate — economics, pricing, licensing structure, legal terms, and regulatory compliance. Commercial and Legal deliver against product’s definition. Not ahead of it. Not after it. |
Consultation produces opinions. Governance produces accountability.
The positioning of Legal inside the Commercials gate is deliberate. Legal that arrives at launch as an independent authority is not a governance feature — it is a governance failure that has been institutionalised. It belongs inside the Commercials stage, operating against product-defined criteria, not arriving at the launch meeting with a list of reasons why the product cannot ship.
What actually changes
Product managers pursue the mission without seeking permission — because the framework defines what is expected at every stage, and authority flows from that definition rather than from whoever is loudest in the room
People know if they are succeeding at the right thing — not just succeeding. The distinction is the difference between Chegg and Duolingo, between Blockbuster and Netflix, built over years before capital makes it visible
Leadership is engaged on genuinely hard problems — not on approvals the framework should already have resolved
The CPO operates as a strategic architect rather than a bottleneck — because the structure does the governing, not the individual
Innovation is the structural consequence of doing the job correctly — not a programme, an initiative, or a value on a wall
The competitive advantage, when it arrives, is the trailing indicator of mission and governance quality over time — not a feature you build, a position you earn
Mission tells the team where to go. Measures confirm they are moving in the right direction. Manpower & Empowerment enforces the structural interlock — at every gate, for every function, accountable to a definition they did not write themselves.
The moat is what you have after that architecture has been running correctly for long enough. Management — the final M — is what becomes possible once the other three are operational. That is next.
#ProductLeadership #CPO #ProductStrategy #NPDFramework #ProductGovernance #BusinessStrategy #SaaS
© 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.
First Comment
The governance argument in M1c connects directly to M2 — the NPD Framework — which covers what the framework looks like in practice: the stages, the gates, what is expected at each, and how the wider business is held structurally rather than consulted informally.
M1d closes the Four Ms series first. Management is the only M that cannot function without the other three already operational. That sequencing is the point.
Thirteen frameworks at johnbowers.pro/frameworks — the Architectural Formula covers the same argument at investment and portfolio analytics grade if that is the level of rigour you need.