Stage 1 · Lesson 2 of 8
Product manager: deciding what gets built and why
A , or PM, makes sure a team builds the right things. That means solving problems users really have, in a way that also works for the business. On a normal day a PM talks to users and reads data.
They write short specs, documents that say what to build and why. They keep the backlog, the ranked list of work waiting to be done, in order. They answer engineers' questions and keep sales, support and leadership aligned.
PMs do not manage the engineers. They usually cannot order anyone to do anything, so they lead through evidence and trust. People who do well are curious about users and comfortable when answers are unclear. They write clearly and can say no politely.
Common trappicturing the PM as the "CEO of the product". The job is closer to a coordinator of good decisions, and much of it is unglamorous follow-up.
A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock
Resources for this stage
Start with
- GuideFreeWrite the Docs: Documentation Guide
Write the Docs · Beginner
The community guide to documentation work, starting with why docs matter and what the job covers