Key takeaways
  • A CPO owns product strategy across three altitudes: board, org and product.
  • Startups, scaleups and enterprises each need the CPO Piece for different reasons.
  • It isn't a backlog-grooming or delivery role. That's the PM and PO.

Most teams who hire a fractional CPO do it because they think they need a roadmap. Most teams who actually need one do it because their function is leaking judgment at altitude. The roadmap is the symptom you can see. The judgment gap is the cause you can't.

This is the first of five field notes on the Core Pieces. We're starting with the CPO because nine out of ten functions we diagnose are short of one, and most don't know they are.

What the CPO Piece actually does.

A Chief Product Officer is the senior seat that owns the product narrative end-to-end: from the board's view of the bet, to the team's view of the next sprint. They don't write user stories. They don't ship code. What they do is set the conditions under which everyone else's work compounds.

Concretely, the CPO Piece operates at three altitudes simultaneously, and the failure mode of every weak CPO function is that one of the three is missing.

Diagram · The three altitudes of the CPO Piece
The three altitudes of the CPO Piece Three stacked horizontal bands representing the altitudes at which a Chief Product Officer operates simultaneously. From top to bottom: Altitude 03 — Board (narrative, OKRs, investment thesis, board confidence). Altitude 02 — Org (org design, hiring, process, levelling, scaling). Altitude 01 — Product (vision, sequencing, prioritisation, quality bar). A vertical marigold band on the left labelled "CPO Piece" spans all three, indicating that the seat operates across all three altitudes at once. CPO PIECE ALTITUDE 03 Board Narrative · OKRs · Investment thesis · Board confidence ALTITUDE 02 Org Org design · Hiring · Process · Levelling · Scaling ALTITUDE 01 Product Vision · Sequencing · Prioritisation · Quality bar
A CPO operates at all three altitudes simultaneously. Weak CPO functions show themselves by which altitude is dark.

Altitude 03: Board. Turning the product into the company's story. The investment thesis. The OKRs the board agrees to. The narrative that says this is the bet, this is the proof, this is the next chapter. Without it, every board meeting is a re-negotiation.

Altitude 02: Org. Designing the function that ships the product. Who reports to whom. How decisions get made. How PMs grow. Which rituals matter. How quality gets owned. Without it, the team can't scale beyond the founder's bandwidth.

Altitude 01: Product. Owning the actual thing being built. The vision, the sequencing, the prioritisation calls when two important features can't both ship this quarter. Without it, the roadmap is a wish list.

Weak CPO functions show themselves by which altitude is dark. Strong ones light all three.

Why startup founders need a CPO Piece.

You're the CEO. You're also the CPO, the head of marketing, and the person on the train writing next quarter's roadmap. The product narrative your investors want, the one that turns six features into a bet they can underwrite, is something you've been carrying in your head, not on a page anyone else can read.

You don't need a full-time CPO. Pre-Series A, you probably can't justify one. What you need is a senior call on the bet, the build, and the runway, just for a window. The CPO Piece, in fractional or advisory shape, gives you a vetted senior operator sitting alongside you for as long as you need them. The Fractional CPO (senior product leadership by the month) is the most common entry point: strategy owned, the roadmap set, and the team levelled up while it's in place.

For qualifying mandates, equity-friendly engagements are on the table. Skin in the game, lower cash burden, shared upside.

Why scaleups need a CPO Piece.

You found PMF. Engineering is shipping. You have one or two PMs. What you don't have is the seat above them: the seat that says no, not this quarter when the board wants to add a new vertical, or yes, but the roadmap moves when sales lands a whale.

Symptoms: the roadmap changes after every board meeting. The founder is still doing product strategy on the train (yes — even at Series B). The PM team is sharp on execution but can't tell you the strategic thesis underneath the next quarter. Two leaders in the same company describe a different "north star" without realising it.

The fix isn't another PM. It's the missing altitude. The CPO Piece, embedded for three-to-twelve months, restores the strategic spine. Once the function is upright, you can hire a full-time CPO with confidence (or extend the Piece, equally common).

Why enterprises need a CPO Piece.

You have a CPO. They left. Or they've been promoted out. Or they're on parental leave. The executive search will take six to nine months and the function can't run dark for that long without things calcifying.

That's interim cover. A defined three-to-nine-month engagement where the CPO Piece holds the seat, keeps the function moving, and hands over cleanly to your incoming hire. Enterprise interim is where seasoned operators earn their fee: senior, scarred, in the seat in days, not weeks.

Adjacent use: a specific transformation initiative. AI product capability stand-up. Regulated-platform overhaul. The CPO Piece as a sprint, scoped to the bet.

What the CPO Piece doesn't do.

  • It doesn't ship code or write user stories. That's the PM Piece and the PO Piece.
  • It doesn't run sprints. Strategic ownership is upstream of sprint discipline.
  • It doesn't replace your CTO. Two different seats. The CPO and CTO are peers; one doesn't subsume the other.
  • It doesn't make the calls you should be making. The CPO Piece frames the calls. The founder or CEO makes the bet.

How to plug one in.

Start with the Diagnostic. Twenty minutes, free. It'll tell you whether your function is short of a CPO Piece, or short of something else entirely (often the answer is "you have the strategy, you're missing a PM"). From there: a fractional CPO, an embedded engagement, or interim cover — sized to the stage.

Next issue: what a PM actually does, and why most growing teams misjudge the role. Published 28 May.