New: Roadmaps ordered paths through our cheat sheets and flashcards, so you always know what to study next.
Explore themSee what's new on GitHubFrom your first user interview to a launch you can defend with data.
A 15-step learning path. Follow it in order, or jump to what you need.
For anyone moving into product management, from engineering, design, business analysis, or a first PM role, who wants a grounded set of practices instead of buzzwords. Plan on about 8 weeks at a few hours a week. This path stays on the discovery-to-strategy side of the job: it does not go deep on Scrum ceremonies and sprint mechanics (see Agile & Scrum in Practice) or on PMI-style scheduling, WBS, and earned value (see Project Management Fundamentals). By the end you can run a discovery process from a raw idea to a validated problem, write a PRD and a prioritized roadmap a team can actually execute against, and read product metrics well enough to know whether a launch worked.
Expected: comfort working with cross-functional teams in a professional job. Helpful but not required: prior experience in engineering, design, marketing, or business analysis.
Start here so you can talk about a product in the language the rest of this path assumes: discovery versus delivery, product-market fit, and the handful of prioritization frameworks step 10 goes deeper on.
Builds on the vocabulary from step 1 by putting you in front of real users: interviews, personas, and job stories that tell you what problem is actually worth solving.
This is where 'what feature should we build' turns into 'what problem are we solving', and it only sticks once you've run the interviews from step 2 through it; expect to circle back to this mindset on every new discovery.
You can frame a problem instead of jumping straight to a feature, and you know what a real discovery conversation looks like. Next up: turning what you heard into an actual strategy.
Finish this section to unlock.
+100 XP
Takes the raw user insight from step 2 and turns it into a vision, a competitive position, and a value proposition your team can actually rally around.
Converts the vision from step 4 into objectives and key results you can actually check progress against each quarter.
Gives you a five-day way to test a strategy call from step 4 against real customers before a single line of code gets written.
You can write a vision and a value proposition, set OKRs that track it, and put a rough idea in front of real users before writing a single spec. Next up: turning that validated idea into something a team can build.
Finish this section to unlock.
+100 XP
Turns a validated idea from step 6 into a document engineering and design can actually build from, not just a strategy slide.
Breaks the PRD from step 7 into a visual map of the user's journey, so the backlog reflects outcomes instead of a flat list of features.
Take this if your company blends the PM and Product Owner roles: it goes deeper on the backlog grooming and sprint-event mechanics that step 8's story map feeds into.
Goes deeper on the prioritization frameworks step 1 only sketched, and sequences the stories from step 8 into a roadmap stakeholders can actually read.
Shipping the roadmap from step 10 isn't the finish line; this is where you learn to tell a real signal like retention from a vanity number, and most PMs keep relearning that distinction their whole career.
You can turn a validated idea into a PRD and a prioritized roadmap, and you can tell a metric that means something from one that just looks good; a few minutes of due flashcards on strategy and OKRs keeps chapter 2 fresh while you build on it here. Next up: working like a professional.
Finish this section to unlock.
+100 XP
Puts the metrics from step 11 and the roadmap from step 10 into language executives, engineers, and sales will actually act on.
Aimed at PMs pitching a new initiative for funding: it formalizes the stakeholder framing from step 12 into a case leadership can approve.
Turns the positioning from step 4 into a real launch plan: timing, channels, and the metric from step 11 that tells you whether it worked.
Pulls every earlier step into the case-study format PM interviews actually use: product sense, the prioritization from step 10, and the metrics reasoning from step 11, all under one clock.
You can bring stakeholders along, defend a launch with real go-to-market thinking, and walk into a product manager interview with a portfolio of your own reasoning to show for it. That's what the Product Manager badge certifies: you can take a product from a raw problem to a launch you can defend with data.
Finish this section to unlock.
+100 XP
Finish every required step, at least 70% of them genuinely done (not skipped), to earn this badge and 500 XP.