VP/CPO-Level Strategy¶
Amara is promoted to CPO eighteen months after the org-design project in Level 3 closed. Meridian has grown past 40 product-eng headcount, added a second product line that's now real revenue (Marketplace), and CEO Lena wants a company-wide product strategy — not a portfolio allocation table, a document that says what Meridian's product organization believes about the market for the next three years and why, one the board will hold Amara accountable to. The jump from VP to CPO strategy work is the jump from "how do we allocate what we have" to "what should we even be building, and why will that still be true in three years."
What CPO-level strategy actually contains¶
| Section | VP-level portfolio review (Level 3) | CPO-level company strategy |
|---|---|---|
| Time horizon | This quarter, next quarter | 2-3 years, revisited annually |
| Unit of analysis | Product lines you already run | Markets you may or may not be in yet |
| Core question | How do we allocate capacity? | What bets deserve to exist at all? |
| Owner of the "why" | Inherited from company strategy | Co-authored with the CEO, sometimes originated by the CPO |
| Audience | Product Leads, occasionally the board | Board, investors, the whole company |
The strategy pyramid¶
A usable company-level product strategy has four layers, each constraining the one below it. Skipping straight to "roadmap" without the layers above is the single most common CPO-strategy failure — it produces a list of projects nobody can explain the purpose of a year later.
| Layer | Question it answers | Meridian example |
|---|---|---|
| Belief | What do we believe is true about the market that others don't (yet) act on? | "Freight brokerage is consolidating around software, not relationships — carriers who adopt matching software first will lock in volume" |
| Position | Where do we choose to compete, and where do we deliberately not? | Own the mid-market carrier segment end-to-end; do not compete for enterprise carriers who already have in-house tooling |
| Bets | What 2-4 multi-quarter investments follow from the position? | Marketplace standalone scale-up, carrier-journey unification, AI-assisted pricing (Level 4 Module 7) |
| Portfolio | How is capacity allocated across the bets this year? | Module-2-style allocation table, now spanning 3 bets instead of 3 lines |
Worked example: writing Meridian's belief statement¶
Amara's first draft of the belief layer was too broad to be falsifiable: "Logistics is becoming more digital." Lena pushes back — that's true of every industry and implies nothing about what Meridian should do differently. Amara rewrites it against a test: a good belief statement names something a competitor who disagrees would actually do differently.
Revised: "Mid-market carriers will consolidate their tooling around whichever platform handles onboarding, pricing, and matching as one system, rather than stitching together point solutions — the switching cost of a unified system beats any single best-of-breed feature." A competitor who disagreed with this would keep building isolated point-solution features instead of investing in the carrier-journey unification bet (the Level 3 project's structural motivation, now stated as strategy rather than an org-design footnote).
The three tests for a CPO-level bet¶
Before a bet earns space in the strategy (and therefore capacity in the portfolio), it has to clear three tests:
| Test | Question | Failure example |
|---|---|---|
| Belief alignment | Does this follow from a stated belief, or is it opportunistic? | Chasing a competitor's feature with no belief basis |
| Sizing | Is the addressable outcome big enough to justify multi-quarter dedicated capacity? | A bet that, even fully successful, moves a metric by an amount too small to matter at Meridian's scale |
| Reversibility window | Can we tell within 2-3 quarters whether it's working, or are we committing blind for years? | A bet with no interim signal, only a final outcome years out |
Strategy vs. roadmap: keeping the layers separate¶
A recurring failure mode as CPO is board members or Leads asking "what's the strategy" and getting handed a roadmap instead. Amara's fix is literally structural: the strategy document is one page per layer (belief, position, bets), capped at four pages total, with the portfolio/roadmap detail living in a separate, longer appendix that changes quarterly while the four-page core changes annually. If the core document needs rewriting every quarter, that's itself a signal — either the market genuinely shifted, or the "strategy" was actually a roadmap wearing a strategy's title.
How It Actually Works¶
At the VP/CPO level, strategy statements compete for organizational attention against every other executive's strategy statement, and the mechanism that determines which one actually shapes resource allocation is not clarity of the writing but how directly it resolves the specific tradeoffs the org is already fighting about. A strategy that avoids naming the hard tradeoff (we will lose at X to win at Y) reads as safe to write but gets ignored in practice, because every team below can interpret it as compatible with whatever they were already planning to do — a strategy compatible with everything commits the organization to nothing. The CPOs whose strategy actually redirects behavior are the ones willing to make it falsifiable: naming what would prove the bet wrong, and more importantly, naming what the org will stop doing, because "what we'll stop" is the only part of a strategy that actually reallocates scarce resources rather than just adding a new initiative on top of an unchanged workload — and it's also the part every subordinate quietly hopes gets left vague, because a named "stop" creates a losing team whose leader will resist it.
Exercise¶
Draft a one-paragraph belief statement for a market or product area you influence, and run it against the falsifiability test: what would someone who disagreed with you actually do differently? Then name one current initiative on your roadmap and check whether it traces cleanly back to a stated belief and position — or whether it's opportunistic work that happens to be getting done anyway.