What does a product manager actually do?
A product manager decides what gets built and why, then makes sure it happens. Day to day that means research, prioritisation, writing, and a lot of alignment across engineering, design and the business. The role has no authority attached — influence comes from judgment and evidence.
The job in one sentence
Figure out which problem is most worth solving, make sure it's solved well, and keep everyone pointed in the same direction while it happens.
Everything on a PM's calendar is downstream of that. Research exists to find the problem. Writing exists to make the decision legible. The meetings exist because a decision that only lives in your head hasn't been made.
What a week actually contains
Talking to customers — support tickets, sales calls, scheduled interviews. Cut first when things get busy, and consistently regretted.
Deciding and defending — what's next, what's not, and why. This produces the documents.
Unblocking — the ambiguity that surfaces mid-build. Should this edge case error or degrade? Is this scope creep or the actual requirement? Someone has to answer within hours, not days.
Communicating outward — sales, support and leadership all need to know what's coming and what changed.
Looking at data — did the last thing work, and is the current thing working.
What it isn't
Not project management, though there's scheduling in it. Not design, though there's judgment about experience. Not a mini-CEO — the phrase does real damage, because it implies authority the job doesn't have and rarely survives contact with an engineering team.
The Amazon working-backwards method captures the actual core: the PM's distinctive contribution is deciding what's worth building and articulating it clearly enough that others can build it well. Linear's team demonstrates the same thing through what they refuse — a coherent product is mostly a record of decisions not taken.
The uncomfortable truth
Most of the role is judgment under uncertainty, and judgment can't be delegated to a framework. The frameworks organise the thinking; they don't do it. That's why the job is hard to teach and why two PMs with identical processes produce completely different products.
Seen in practice
Case studies where this shows up as a real decision, not a definition.
Related questions
Do product managers write code?
Almost never as part of the job. Technical understanding matters — enough to have credible conversations about trade-offs and feasibility — but writing production code is not the role, and a PM who spends their time coding is usually neglecting the part nobody else covers.
Who does a product manager manage?
Usually nobody. It's a leadership role without reporting lines, which is why the job is often described as influence without authority. Engineers and designers are peers, not reports.
What's the hardest part of the job?
Deciding with incomplete information and living with it. Most of the visible work — meetings, documents, tickets — is downstream of a small number of judgment calls made without enough data, and those calls are what the role is actually accountable for.
More on role
Last reviewed 2026-09-07