Key takeaways
  • The PM owns what to build next, at the intersection of users, business and engineering.
  • Engineering shipping while nobody decides next is the signal you need a PM Piece.
  • Each stage needs it differently, and it isn't a project-manager role.

Most growing teams think a PM is somewhere between a project manager and a junior CPO. They are neither. The PM Piece is the connective tissue between why and what: the seat that takes strategy and turns it into things a team can ship. Misjudge the role and you'll either underhire (and the function leaks) or overhire (and you've bought a seat above its skis).

Last issue we covered the CPO Piece, strategic ownership at altitude. This one is about the seat directly underneath: the one that takes the strategy and makes a product team productive.

What the PM Piece actually does.

A Product Manager sits at the intersection of three constituencies, and their job is to make decisions that all three would accept as defensible. Users care about the problem being solved. Business cares about the outcome being moved. Engineering cares about what's actually shippable, in what order, at what cost.

The PM is the only seat that holds all three at once. The first job of a strong PM isn't to "build features". It's to surface the right problems to solve and bring the right evidence into every decision. Everything else (discovery work, roadmaps, user stories, stakeholder management, the metrics) is downstream of that.

Diagram · The PM triangle
The PM triangle — three constituencies a Product Manager balances A triangle with three corner circles, each labelled at the same size: Users at the top, Business at the bottom-left, Engineering at the bottom-right. In the centre of the triangle, a larger marigold circle outlined in ink, labelled PM with the italic caption "holds all three" beneath. The diagram shows that the Product Manager is the only seat that simultaneously represents users, business and engineering in every product decision — pull too hard towards one and the other two start losing trust. USERS BUSINESS ENGINEERING PM holds all three
The PM is the only seat that simultaneously represents all three constituencies in every decision. Pull too hard toward one and the other two start losing trust.

Day-to-day, that means: continuous discovery (interviews, instrumentation, prototype tests), prioritisation (what we ship and what we don't, with clear logic), stakeholder craft (saying no to a louder voice without breaking the relationship), and shipping discipline (the thing actually goes out, measured, and learned from).

The first job of a strong PM isn't to build features. It's to surface the right problems — and bring the right evidence into every call.

Why startup founders need a PM Piece.

You're shipping. You're also doing sales calls, fundraising, hiring, and trying to read the market. The product decisions you're making in the spare moments aren't getting the discovery they deserve. And your one or two engineers are pinging you in Slack for direction every fifteen minutes.

You don't need a senior PM yet. You need someone who can take the product decisions off your plate with enough rigour that you trust them. A fractional PM Piece, embedded a few days a week, does that. You stay the visionary. The PM does the work of converting your vision into a shippable, evidence-backed plan the team can run with.

The strongest entry point at this stage: The MVP or The Roadmap Set Piece: a defined two-to-three-week engagement that gets the product function moving without locking you into a long contract.

Why scaleups need a PM Piece.

This is where the PM Piece is most often missed — and most often misjudged. You have engineering. You have one PM (or one-and-a-half). Sprints are happening. Things are shipping. But somewhere between the strategy and the sprint, decisions are getting made in the wrong rooms by the wrong people. Engineering is making product calls because no one else is. Marketing is promising features that aren't on the roadmap. Sales is committing dates the build team has never seen.

The fix isn't more engineers, or another sales hire. It's a second (or third) PM, but a senior one, because junior PMs in a function this stretched will drown. The PM Piece, embedded for three-to-twelve months, brings that seniority without the cost or risk of a permanent hire. The vetted bench means the person walking in has shipped this exact shape of problem before.

Common shapes: a senior PM owning one critical surface area (growth, onboarding, a key vertical), or a PM lead coordinating across two-to-three feature teams.

Why enterprises need a PM Piece.

Two scenarios. Specialist depth: you have PMs, but the regulated-platform or AI-product capability isn't sitting on the team yet. A PM Piece with the right scars (fintech, healthtech, machine-learning product) embeds for the duration of the bet and leaves the team upskilled. Interim cover: a senior PM leaves, the search will take months, and the gap can't run dark. The PM Piece holds the seat warm.

Enterprise also buys the PM Piece for transformation work: an existing PM team needs the discipline of evidence-led product. A senior practitioner embedded for six months can reset the rituals, raise the bar, and leave a function that runs better than it did when they arrived.

What the PM Piece isn't.

  • It isn't a project manager. PMs own outcomes, not Gantt charts.
  • It isn't a Product Owner. POs own the backlog day-to-day; PMs own the bet behind it. They overlap, but they aren't the same. More on that in N°16.
  • It isn't a junior CPO. A PM operates at sprint-to-quarter altitude; the CPO operates at quarter-to-board altitude. Asking a PM to be the strategist breaks them.
  • It isn't a UX designer. PMs partner with design; they don't replace it.

How to plug one in.

Start with the Diagnostic. If you've got engineering shipping but the product is being decided in too many rooms, the answer is usually a PM Piece. The next move is either The Roadmap (Set Piece, 2–3 weeks) for teams in the planning gap, or an embedded PM Piece (3–12 months) for teams in the doing gap.

Next issue: the PO Piece. Same letters, different job — and where the line actually falls. Published 11 June.