Ask ten people what a product manager does and you’ll get ten answers: “mini-CEO,” “the person who writes tickets,” “the one in all the meetings.” Most of them are wrong. Here’s the honest version.
The one-sentence job description
A product manager decides what to build next and why — and then makes sure everyone agrees, everyone knows their part, and everyone finds out whether it worked.
Notice what’s not in that sentence: coding, designing, managing people. PMs typically have no direct authority over anyone. Everything gets done through clarity and persuasion, which is why writing and communication matter more in this job than any technical skill.
What a real week looks like
- Deciding: reviewing data and user feedback to choose what matters most; saying “no” (kindly) to most requests
- Writing: PRDs, user stories, stakeholder updates, decision docs — a clear document ends arguments that meetings can’t
- Talking to users: the best PMs talk to real users every week; not surveys — conversations
- Unblocking: answering the engineering team’s edge-case questions fast, so building never stalls
- Aligning: keeping sales, marketing, support and leadership informed so nobody is surprised at launch
What you own vs. what you don’t
You own the problem: which user pain to solve, in what order, and how success is measured. Engineering owns how it’s built. Design owns how it works and feels. The fastest way to lose a team’s trust is to confuse these lanes.
Product manager vs. product owner
In many companies they’re the same job. Where they differ: “product owner” is a Scrum-framework role focused on backlog and sprint-level decisions, while “product manager” usually implies more strategy — market analysis, roadmaps, business outcomes. Starting out, don’t stress the distinction; the skills transfer completely.
Signs the job would suit you
- You like understanding why people do things, not just what they do
- You can hold opinions strongly but change them when the evidence changes
- You’d rather write one clear page than sit through three alignment meetings
- You’re comfortable being responsible for outcomes you don’t fully control
Do this today
Pick an app you use daily and write one paragraph: what user problem does its newest feature solve, and how would you measure whether it worked? Congratulations — that’s product thinking. Next, learn to write your first PRD.