Roadmap
Product manager
Find problems worth solving, decide what to build, and get it shipped with a team.
Who it's for
Engineers, designers, analysts and MBA students moving into product, and new PMs.
Where it leads
- Associate product manager
- Product manager
- Product owner
By the end you can
- Run user interviews that reveal real problems
- Write a clear one-page product spec
- Prioritise with reasons people accept
- Define success metrics and read an experiment
- 1
What a PM actually does
Product is about outcomes, not features. Start with how the best teams work.
- 2
Understand users
Most failed products solved a problem nobody had. Interviews prevent that.
- BookThe Mom TestRob Fitzpatrick. How to ask questions people can't lie to you about.
- ArticleNielsen Norman Group: user interviewsNN/g
Do this: Interview five people about a problem you want to solve and write what you learned in one page.
- 3
Strategy and prioritisation
Saying no well is most of the job.
Do this: Write a one-page spec for one feature: problem, users, solution, metrics and what's out of scope.
- 4
Metrics and experiments
Know whether what you shipped worked.
- 5
Work with engineers and designers
Enough technical and design literacy to earn trust and make good trade-offs.
Learning this with others is easier.
Ask questions when you're stuck, find people on the same path, and track your progress on DevLearn.