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 a vague product problem to a design system and operating model a whole team can run.
A 12-step learning path. Follow it in order, or jump to what you need.
This path is for designers ready to own the whole product design process, not just the craft: the business alignment, systems, and operations work that separates a product designer from a UX designer. It runs about 6 weeks at a few hours a week, following the discovery-to-DesignOps arc of roadmap.sh's Product Design roadmap. It does not cover deep user research, wireframing, or usability testing, which the separate UX Designer path owns; this one picks up where that craft work ends. By the end you can prioritize a product backlog against real constraints, build a token-based design system in Figma, and hand engineering a spec they can build from without guessing.
Expected: no prior product design experience. Helpful but not required: some hands-on experience with a design tool like Figma or a UX background, since product design usually builds on UX craft.
Open this today and you already have a five-stage loop for turning a vague product problem into a tested idea, weighted here toward the feasible and viable checks a business-facing product designer leans on most.
Turns the fuzzy problem from step 1 into the vocabulary every roadmap meeting runs on: OKRs, prioritization frameworks, and the discovery-versus-delivery rhythm product teams use to decide what ships next.
This is where prioritization clicks: ranking ideas by RICE, Kano, or MoSCoW instead of gut feel, a call you'll keep revisiting whenever step 2's roadmap gets more requests than the team can build.
You can frame a fuzzy product problem, weigh it against feasible and viable, and rank it against a real roadmap instead of going with gut feel. Next up: getting the room aligned and turning that plan into real screens.
Finish this section to unlock.
+100 XP
Defends the prioritized backlog from step 3 in the room: reading who holds power, resetting expectations, and turning a skeptical exec into a supporter before a single screen gets designed.
Builds the actual screens once step 4's stakeholders are aligned, going deeper than a typical design-tool tour into Dev Mode, Code Connect, and the design-token machinery you'll systemize next.
Goes deeper on the tokens and libraries step 5 only sketched inside Figma, covering the naming, governance, and multi-brand theming that keep a hundred-screen product consistent without anyone eyeballing a hex code.
Feedback clicks here, not before: separating a critique of the work from a critique of yourself, and running every screen from step 6's system through a structured review before calling it done.
Hands the reviewed screens from step 7 to engineering the way a real handoff should work: annotated edge cases, a spec mapped to step 6's system, and a status of ready for dev instead of a link and a shrug.
You can get a room of stakeholders aligned, build a token-based Figma system instead of one-off screens, and hand engineering a spec they don't have to guess at, with a few minutes of due flashcards from chapter 1 keeping your prioritization frameworks sharp while you build. Next up: running this like an operation, not a one-off project.
Finish this section to unlock.
+100 XP
Reach for this if quarterly planning is yours to run: turns step 2's OKR table into objectives and key results specific enough to survive a real review instead of getting quietly abandoned.
Take this if a stakeholder readout or portfolio case study is coming up: turns the discovery-to-handoff story from steps 1 through 8 into a deck a business audience actually follows.
Line this up if you're about to start applying: product designer interviews probe the tradeoffs from step 4 as hard as craft, so get comfortable defending both out loud.
Ties every earlier step into an operating model: the system from step 6, the critique habit from step 7, and the handoff process from step 8 become practices a whole team can run without you in the room.
You can run product design as a business function: prioritized discovery, a design system engineering trusts, critiques that make the work better, and an operating model a whole team can follow without you in the room. That's the Product Designer badge, earned.
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.