What is a Product Manager?
A product manager (PM) is responsible for a product’s success. They understand users and the market, decide what to build, set priorities and work with design and engineering teams to deliver it.
Product managers work in tech companies, startups, banks, e-commerce and many other industries. The role combines business sense, user empathy and enough technical knowledge to work well with engineers.
How to use this product manager roadmap
Follow this product manager roadmap in order. Each step adds a skill PMs use every week.
Choose one product you use daily and practise every step on it: research its users, write its strategy and plan its next features.
1Step 1: Product management basics
Understand the role, the product life cycle and how PMs work with teams.
What is it?
Product managers focus on outcomes, the change for users and the business, rather than just shipping features.
What to learn
A PM does not need to be the expert in everything. Your job is to help the team make good decisions.
Example
text
Output: "Launch new search filter"
Outcome: "Increase users who find a product
within 1 minute from 40% to 60%"Outcome goals tell the team why the work matters.
Helpful resource: SVPG articles
2Step 2: Understanding users and the market
Discover problems worth solving.
What is it?
Jobs to be done describes what a user is really trying to achieve, which helps you see beyond feature requests.
What to learn
Talk to users every week if you can. Small, regular conversations keep you close to real needs.
Example
text
Job story
When I am planning a weekend trip,
I want to compare total trip prices quickly,
so I can stay within my budget.Job stories focus on the situation and goal, not a specific feature.
Helpful resource: Product Talk
3Step 3: Product strategy and vision
Set a clear direction for the product.
What is it?
OKRs (objectives and key results) turn strategy into measurable goals for a quarter.
What to learn
A good strategy says what you will not do as clearly as what you will do.
Example
text
Objective: Make booking effortless for new users
KR1: Raise first-week booking rate from 20% to 30%
KR2: Cut average booking time from 4 min to 2 min
KR3: Reduce booking support tickets by 25%The objective is inspiring; the key results are measurable.
Helpful resource: What Matters: OKRs
4Step 4: Prioritisation and roadmaps
Decide what to build first and communicate the plan.
What is it?
RICE scores ideas by Reach, Impact, Confidence and Effort to compare them fairly.
What to learn
Roadmaps should show problems and goals, not a long list of features with fixed dates.
Example
excel
RICE = (Reach * Impact * Confidence) / Effort
=(B2*C2*D2)/E2
Example: (2,000 * 2 * 0.8) / 4 = 800Higher scores suggest more value for the effort, but use judgement too.
Helpful resource: Intercom: RICE prioritisation
5Step 5: Writing requirements and working with design
Explain problems and solutions clearly to the team.
What is it?
A PRD (product requirements document) describes the problem, goals, users, requirements and how success will be measured.
What to learn
Explain the problem and the goal well, then let designers and engineers propose solutions.
Example
text
PRD: One-tap reorder
Problem: Repeat customers take 4 min to reorder
Goal: Reorder in under 30 seconds
Users: Customers with 2+ past orders
Must: "Order again" on home screen
Metric: Reorder rate +15% in 60 daysA short PRD gives the team clarity without blocking creativity.
Helpful resource: Atlassian: Product requirements
6Step 6: Agile delivery with engineering
Ship work in small steps with your development team.
What is it?
Agile teams deliver small pieces of value often, learn from feedback and adjust.
What to learn
Learn enough technical basics to understand trade-offs. Our backend developer roadmap gives a useful overview.
Example
text
Sprint goal: Users can reorder from home screen
Stories:
- Show last 3 orders on home (5 pts)
- Reorder button adds items to cart (3 pts)
- Track reorder event in analytics (2 pts)A sprint goal ties all the work together around one outcome.
Helpful resource: Scrum.org: What is Scrum
7Step 7: Metrics and experimentation
Measure product success and test ideas with data.
What is it?
Retention shows how many users come back over time. It is one of the strongest signs that a product is useful.
What to learn
Pick a few key metrics and check them every week. Basic SQL helps a lot; see the SQL roadmap.
Example
sql
SELECT signup_week,
COUNT(DISTINCT user_id) AS users,
COUNT(DISTINCT CASE WHEN active_week = signup_week + 4
THEN user_id END) AS retained_week4
FROM user_activity
GROUP BY signup_week;This query compares how many users from each sign-up week were still active four weeks later.
Helpful resource: Amplitude blog
8Step 8: Leadership, communication and career
Lead without authority and grow as a PM.
What is it?
PMs rarely manage people directly, so they lead by building trust and sharing clear reasons for decisions.
What to learn
Clear writing is a PM superpower. Practise short updates that state the decision, the reason and the next step.
Example
text
Weekly update
Decision: We will launch reorder to 20% of users Monday
Why: Test results show +12% reorders, no errors
Risks: Slight increase in support questions
Next: Full rollout if metrics hold for 1 weekShort updates like this keep stakeholders informed and aligned.
Helpful resource: Lenny’s Newsletter
Product Manager roadmap project ideas
Projects turn what you learn into real skills. Build at least one project from each level below, and put every finished project on GitHub with a clear README.
Product teardown
Analyse a popular app’s users, value and business model.
User interviews
Five interviews with jobs-to-be-done summary.
Strategy and OKRs
Vision, strategy and quarterly OKRs for a product.
Prioritised roadmap
RICE scores and a now-next-later roadmap.
PRD and prototype
Complete PRD with a clickable prototype.
Metrics dashboard
Key metrics, funnel and one A/B test plan.
Tips to finish this product manager roadmap
- Learn by doing. Put every step into practice with a real or sample case. Practical work teaches far more than reading alone.
- Be consistent. One focused hour every day beats a long session once a week. Small daily progress adds up quickly.
- Build a portfolio. Save your best work, reports and case studies. A portfolio proves your skills to employers and clients.
- Find a mentor and a community. Talk to people already working in the field. Their advice saves you time and opens doors.
- Master the basics first. The fundamentals in this product manager roadmap change slowly. Learn them well before chasing new tools and trends.
Career paths and next steps
After this product manager roadmap, you can apply for associate product manager, product owner or junior PM roles. Experienced PMs grow into senior PM, group PM, head of product or chief product officer.
Strengthen your design side with the UX designer roadmap, or your analysis skills with the business analyst roadmap.
Related roadmaps
Product Manager Roadmap FAQs
Do product managers need to code?
No, but understanding how software is built helps you work well with engineers and make better trade-offs.
How do I become a product manager with no experience?
Many PMs move from roles such as BA, design, engineering, marketing or customer success. Side projects and case studies help show your skills.
What is the difference between a product manager and a project manager?
A product manager decides what to build and why. A project manager focuses on delivering a defined project on time and budget.
Which skills matter most for PMs?
Customer understanding, prioritisation, clear communication and data-driven decision making.