Key takeaways
  • PO and PM share letters, not jobs: the PO owns backlog, sprint discipline and delivery flow.
  • Startups rarely need a separate PO; scaleups often need one urgently.
  • Enterprises need PO depth. It isn't the same seat as the PM.

Half the teams we diagnose can't articulate the difference between their PMs and their POs, and the people in those seats often can't either. The result is a function where one person does both jobs badly, or two people do both jobs with overlap, friction, and missed work falling between them. Neither is what you want.

Following on from N°26 on the CPO and N°27 on the PM, this one is about where the line falls between PM and PO, and when a PO Piece is the right answer.

What the PO Piece actually does.

A Product Owner is the seat that owns the backlog. Not the strategy. Not the bet. The backlog — the ordered list of work the engineering team is going to do, the definition of ready for it to enter a sprint, and the definition of done for it to leave one. The PO is the seat that makes sure engineering never waits on product to make a call.

In origin (Scrum), the PO was the only product seat. They owned the backlog AND the strategy. In practice, at any team beyond a single squad, those two jobs are too different to live in one person. The PO ends up either doing strategy and neglecting the backlog, or running the backlog and never thinking strategically. The split, PM for strategy and PO for backlog flow, is the modern compromise.

Diagram · From strategy to ship — where the PO Piece lives
From strategy to ship — where the PO Piece lives A horizontal flow of seven nodes showing the path from product strategy to a shipped feature. From left to right: Strategy owned by CPO, Outcome owned by PM, Epic owned by PM, Feature owned by PO, Story owned by PO, Sprint owned by PO with engineering, Ship. A marigold band highlights the Feature-Story-Sprint section as "The PO's Zone". A dashed vertical line separates the left half (strategy altitude, measured in quarters) from the right half (delivery altitude, measured in sprints). The Product Owner owns the flow of work from Feature down through Sprint execution. — THE PO'S ZONE — CPO Strategy PM Outcome PM Epic PO Feature PO Story PO + ENG Sprint SHIP Strategy altitude (quarters) Delivery altitude (sprints) FROM HERE TO SHIP — THE PO OWNS FLOW Definition of ready · sprint cadence · definition of done · blockers removed
The PM zone runs from Outcome to Epic. The PO zone runs from Feature to Sprint. The handover is where most under-resourced functions break — and where the PO Piece adds the most leverage.

Day to day, the PO does: backlog grooming (continually), story writing (the actual stories engineering will pick up), refinement sessions (with engineering), sprint planning, daily ceremonies, removing blockers, accepting work as done, and quarterly cadence with the PM. Their measure is delivery flow — predictable velocity, fewer surprises, less wasted engineering time.

The PM owns the bet. The PO owns the flow. Confuse them and you'll either ship the wrong thing fast, or the right thing too slowly.

Why startup founders rarely need a separate PO.

At one squad and one PM (or one founder-as-PM), the PO role lives inside the PM. You don't need a dedicated PO until you have enough delivery work that the strategic thinking is being crowded out. That usually means two-plus engineering teams or a complex regulated build. Pre-then, one strong PM Piece covers both seats well enough.

The exception: a regulated platform build where the backlog complexity is enormous (think wealth management, healthtech, fintech-with-compliance). At that point, the PO Piece earns its keep from day one because the cost of mis-sequencing work is high: both compliance and engineering.

Why scaleups often need a PO Piece urgently.

Most common shape: you have one stretched PM (or two), they're trying to do strategy AND backlog, and one or the other is leaking. The tell: engineering keeps pinging product for "which one of these should I pick up next?" and stories are showing up half-formed at refinement. The PM is firefighting tactical questions instead of doing discovery and stakeholder work.

The PO Piece, embedded full-time on a team, takes that delivery flow off the PM's plate. Sprint cadence stabilises within weeks. Engineering velocity becomes predictable. Stories arrive at refinement ready. The PM gets back to PM work.

Common entry point: The Backlog — a one-to-two-week Set Piece that reshapes the backlog, defines ready/done, and proposes a sprint cadence. Often a doorway to an embedded PO Piece thereafter.

Why enterprises need PO depth.

At scale, the PO becomes a specialist role. Regulated platforms need POs who can write stories that survive an audit. Multi-team programmes need POs who can coordinate cross-team dependencies. AI-product builds need POs who can articulate "done" for non-deterministic systems. In each case, the PO Piece is brought in as a specialist with the right scars. Not a generalist.

Adjacent use: programme-level PO cover during a large platform migration. The PO Piece holds the seat while the function transforms.

What the PO Piece isn't.

  • It isn't a PM. If you only have one person, they're a PM-doing-PO-work, not the other way around. Strategy doesn't follow from backlog hygiene.
  • It isn't a scrum master. The PO owns the backlog; the scrum master owns the process. Two different seats; sometimes one person, often not.
  • It isn't a Business Analyst. Closer than PM, further than scrum master. A BA documents requirements; a PO owns the queue and the priority.
  • It isn't optional past a certain scale. One PM cannot run discovery, strategy, stakeholders and a multi-squad backlog. Something gives.

How to plug one in.

Start with the Diagnostic. If sprints are slipping, stories are half-formed at refinement, and your PM is in firefighting mode, the answer is usually a PO Piece. The Backlog Set Piece (1–2 weeks) is the fastest way to feel the difference. An embedded PO Piece (3–12 months) is the durable answer.

Next issue: the Quality Piece. What happens when "we'll add tests later" was the call eighteen months ago. Published 25 June.