Product manager — tasks, one by one

Writing the requirement down

This is the most visible output of the role and the one generation handles most convincingly — a structured document produced from a description is close to the ideal case. It is also a large share of how the job is judged from outside, which is why the exposure feels larger than it is.

A well-written spec for the wrong thing is worse than a rough one for the right thing. Producing the document was never the scarce part; knowing which document to write is.

Deciding what not to build

A model can rank a backlog against stated criteria. It cannot absorb the political cost of a refusal, and the refusal is the decision — everything a team does not do is decided by whoever is willing to be the person who said no.

This is a judgement about the nature of the work rather than a measured one. Nothing here says organisations value it correctly, and many measure product managers on output rather than on what they prevented.

Finding out what is actually wrong

Tools now summarise interviews and cluster feedback competently, which helps. The part that does not transfer is the live judgement in the room — noticing the hesitation, asking the follow-up that was not on the list, and knowing that what someone does contradicts what they just said.

Says nothing about how many product managers actually do this. In a great many companies the role never talks to a user, and for those roles this task is theoretical.

Getting three teams to move together

This is influence without authority, conducted in meetings and corridors, and it is most of what the job actually consists of. There is nothing here for a tool to take, because the medium is other people's willingness.

A description of where the work sits, not a measurement. It also does not say this is done well — coordination failure is among the most common reasons products ship late.

Being wrong in public

Accountability for a bet is the core of this role and it cannot be delegated to a system, because the point of it is that a person's judgement is on the line. Where organisations remove this, the role degrades into writing tickets — which is the half that is exposed.

Whether this is real depends entirely on the company. Many product managers have responsibility without the authority that would make it meaningful, and this page cannot tell you which kind a given job is.

Specifying what a generative feature may do to a user

This is new work with no settled practice, and it is landing on product rather than engineering because the questions are about acceptable harm and user expectation rather than about the model. In several markets it is also becoming a documented obligation rather than a preference.

New work appearing is not new headcount, and nothing here says companies are staffing it. In most teams it is currently absorbed by whoever owns the feature.