Product managers spend 38% of their time on documentation and communication — and only 18% on strategy and discovery. That ratio is backwards for most orgs, and fixing it is the most direct lever on PM impact (Scriptonia, 2026 internal data).
"The job is to make sure the right thing gets built, built right. Everything else is overhead. The question is how much overhead your processes require."
— Alex J., Principal PM at a growth-stage SaaS company
What a PM actually does (time breakdown)
| Activity | % of time (average PM) | % of time (high-impact PM) |
|---|---|---|
| Writing PRDs and specs | 22% | 9% |
| Meetings (sync, planning, review) | 31% | 28% |
| Stakeholder communication | 16% | 12% |
| Customer discovery / research | 12% | 24% |
| Data analysis | 8% | 16% |
| Strategy and roadmapping | 6% | 18% |
| Unplanned / reactive | 5% | 3% |
The five core PM responsibilities
1. Define what to build and why. This is the core job. It requires customer interviews, behavioral data analysis, competitive positioning, and strategic judgment. Most PMs don't spend enough time here.
2. Specify how to build it. PRDs, user stories, acceptance criteria. The goal is to transfer context from your head into the engineering team's understanding with zero ambiguity. 68% of engineering re-requests come from this step failing (Scriptonia, 2026).
3. Prioritize ruthlessly. There are always more ideas than capacity. The PM's job is to sequence work so the team delivers maximum value in minimum time. This requires a prioritization framework (RICE, ICE, MoSCoW) and the judgment to override the framework when necessary.
4. Align stakeholders. Sales wants feature X. Customer Success wants feature Y. The CEO wants feature Z. The PM synthesizes these inputs, makes a decision, and communicates it with enough context that people can disagree but commit.
5. Measure what shipped. Defining success metrics before launch and reviewing them 30/90 days post-launch. Most PMs define metrics but rarely do the 90-day review.
What PMs don't do (but people think they do)
PMs don't manage engineers. PMs don't make final design decisions. PMs don't own sprint velocity. PMs don't write code. PMs don't set architecture decisions (that's the tech lead's job). The common thread: PMs have authority on what gets built, not how it gets built.