The PM as Editor
Product managers don't write code, but we edit reality — deciding what gets cut, what stays, and what gets rewritten entirely.
The best analogy I’ve found for what a product manager does isn’t project manager, or mini-CEO, or even strategist. It’s editor.
An editor doesn’t write the book. But they’re the one who tells you when chapter four needs to be cut entirely, when the voice drifts, when the ending doesn’t earn itself. They hold the coherent vision of what the thing should be against the messy reality of what it currently is.
That’s the job.
What editing looks like in product
Every sprint, you’re handed a draft. Feature requests from sales, bugs from support, speculative ideas from leadership, half-baked concepts from the design sprint last quarter. Your job isn’t to execute all of it. It’s to make the cuts.
The cuts are where the work lives.
Saying no — clearly, with reasoning, without hedging — is an editorial act. Reframing a request from “we need a toggle” to “we need users to feel in control” is an editorial act. Deciding that this quarter’s focus is depth, not breadth, is an editorial act.
Why PMs avoid it
Editing is uncomfortable because it requires conviction. Conviction requires being willing to be wrong publicly.
Most PMs hedge. They keep everything on the roadmap. They add “explore” to every item. They let stakeholders add scope without removing anything else. The result isn’t a product strategy — it’s a backlog.
A backlog isn’t a story. It’s a pile of drafts.
The practical discipline
Before any planning session, I try to answer one question: if we could only ship one thing this quarter, what would it be? Not because we’ll only ship one thing, but because the answer reveals what actually matters.
Everything else is negotiable. That one thing isn’t.
That’s where you put your conviction.