The PM Role for Product Managers
The PM role is the set of responsibilities that sit between users, business and engineering. A product manager defines the problem, sets priorities and keeps the team aligned on outcomes. Product thinking is the habit of starting from user value and evidence, and judging ideas by the result they create.
Stage: Product Foundations · Part of the Product Manager roadmap · Last reviewed 19 November 2026
What to learn in The PM Role
- Describe what a product manager decides and what they do not own
- Apply product thinking to turn a feature request into a problem statement
- Separate the roles of PM, designer, engineering lead and project manager
- Explain the product lifecycle from idea to growth and decline
- Use the user-problem-solution framing in a short brief
The PM Role interview questions
What is the difference between a product manager and a project manager?
A product manager decides what to build and why, owning outcomes for users and the business. A project manager plans and tracks how and when work is delivered, owning scope, schedule and risks. In small teams one person may do both.
Do product managers need to write code?
No, but they need enough technical understanding to discuss trade-offs, estimates, APIs and data with engineers. Knowing how the system works helps a PM judge feasibility and avoid asking for things that are cheap to ask for but costly to build.
Where The PM Role fits in the Product Manager roadmap
The PM Role belongs to the Product Foundations stage (beginner level), which takes about 4 hours. The role and the craft.
Other units in this stage
Back to the full Product Manager roadmap