Learning Path: Your First PM Role

Who This Is For

You're transitioning into product management from engineering, design, marketing, or another function. Or you've just landed your first PM job and want to build a strong foundation. This path covers the fundamentals every PM needs to succeed in their first 6 months.

What You'll Learn

Understand what a PM actually does day-to-day and what success looks like
Master the core skill of understanding users and identifying problems worth solving
Learn to prioritize ruthlessly and create roadmaps that drive alignment
Build effective working relationships with engineering teams
Navigate your first 90 days with confidence and impact

Time Commitment

Total Estimated Time: 15-20 hours
Recommended Pace: 3-4 hours/week over 5 weeks
Can Be Compressed: Yes, to 2-3 weeks for intensive study

Module 1: What Does a PM Actually Do?

Estimated Time: 3-4 hours

Learning Objectives

Understand the PM role across different company types and stages
Identify the core competencies that separate great PMs from good ones
Recognize different paths into product management

Core Episodes

Guest	Episode Focus	Key Insight
Ken Norton	Product leadership skills	The skills and mindset that define great PMs
Shreyas Doshi	Art of product management	PM mastery across strategy, execution, and craft
Annie Pearl	Product management excellence	How to build PM skills at every level
Claire Vo	Product management growth	Navigating PM career progression

Key Frameworks

PM Core Competencies (Sharps, Drive, Influence) - Three essential traits for PM success
Paths to Product Management - Four distinct routes into PM
Full-Stack PM - Own outcomes end-to-end, not just features

Exercises

Role Definition: Write a 1-page document describing what PM means at your company. Interview 2-3 engineers and designers to understand their expectations.
Skills Assessment: Rate yourself on the PM core competencies (sharps, drive, influence). Identify your top 2 strengths and 2 areas for growth.
PM Shadowing: If possible, shadow a senior PM for a day. Document their activities and the decisions they made.

Reflection Questions

What drew you to product management? How does that motivation align with what the role actually entails?
Which PM competency feels most natural to you? Which will require the most deliberate practice?
Based on what you've learned, what's one misconception you had about the PM role?

Module 2: Understanding Users and Problems

Estimated Time: 3-4 hours

Learning Objectives

Conduct effective user interviews using Jobs to Be Done methodology
Identify the "struggling moments" where customers need help
Distinguish between what customers say and what they actually need

Core Episodes

Guest	Episode Focus	Key Insight
Bob Moesta	Jobs to Be Done	People hire products to make progress in their life
Teresa Torres	Continuous product discovery	Build a habit of weekly customer conversations
Kristen Berman	Behavioral science in product	Why users don't always do what they say
Kevin Yien	Unorthodox PM tips	Practical discovery techniques

Key Frameworks

Jobs to Be Done (JTBD) - Understand the progress customers are trying to make
Four Forces of Progress - What drives and blocks behavior change
Friction Logging - Systematically identify UX issues

Exercises

First JTBD Interview: Conduct 3 interviews with recent customers/users. Focus on understanding the "struggling moment" that led them to your product.
Friction Log: Walk through your product as a new user. Document every moment of confusion, friction, or delight.
Assumption Mapping: List your top 5 assumptions about what users want. Mark each as "validated," "invalidated," or "unknown."

Reflection Questions

What surprised you most about what users actually struggle with versus what you assumed?
How might your product's "job" be different from what the company thinks it is?
When have you personally "hired" a product to solve a struggling moment?

Module 3: Prioritization and Roadmapping

Estimated Time: 3-4 hours

Learning Objectives

Create a prioritization framework that drives clear decisions
Build roadmaps that align stakeholders without over-committing
Balance short-term execution with long-term vision

Core Episodes

Guest	Episode Focus	Key Insight
Christina Wodtke	OKRs and execution	Set goals that drive focus and accountability
Ravi Mehta	Product strategy stack	Build strategy from mission to metrics
Shreyas Doshi	Art of product management	The LNO framework for prioritization
Ben Williams	Product management craft	Practical roadmapping techniques

Key Frameworks

Radical Focus / OKRs - Quarterly goal-setting for focus and learning
Four Types of Product Work - Balance feature, growth, PMF expansion, and scaling work
70-20-10 Investment Split - Allocate resources across core, strategic, and bets

Exercises

Prioritization Framework: Create a prioritization rubric for your current backlog. Use it to stack-rank your top 10 items.
Roadmap Draft: Create a 3-month roadmap for your product area. Include 1-2 objectives and the key initiatives under each.
Stakeholder Alignment: Present your roadmap to a peer or mentor. Practice explaining the "why" behind your prioritization.

Reflection Questions

What's the hardest "no" you'll have to say with your current prioritization? How will you communicate it?
How do you balance confidence in your roadmap with the flexibility to adapt?
What's the biggest risk if your prioritization is wrong?

Module 4: Working with Engineering

Estimated Time: 3-4 hours

Learning Objectives

Build trust and credibility with engineering teams
Write specs and requirements that enable great execution
Navigate the tension between shipping fast and building right

Core Episodes

Guest	Episode Focus	Key Insight
Marty Cagan	Product management excellence	The difference between empowered teams and feature teams
Brandon Chu	Product management insights	PM-engineering partnership principles
Will Larson	Engineering mindset	Understanding how engineers think
Karri Saarinen	Building with taste and craft	The role of craft in product building

Key Frameworks

Help Teams Ship the Right Thing - The PM job is enabling teams, not directing them
Clarity and Conviction - The two core PM skills
Problem-First Approach - Start with problems, not solutions

Exercises

Engineer 1:1s: Schedule 30-minute conversations with 3 engineers. Ask: "What could I do differently to make your work easier?"
Spec Review: Take a recent spec you wrote and ask an engineer to critique it. What was unclear? What was missing?
Tech Debt Inventory: Work with engineering to identify the top 3 pieces of tech debt affecting velocity. Understand the trade-offs involved.

Reflection Questions

What's the difference between telling engineers what to build versus empowering them to solve problems?
How do you balance pushing for speed with respecting engineering's concerns about quality?
When is it appropriate to override an engineering recommendation? When is it not?

Module 5: Your First 90 Days

Estimated Time: 3-4 hours

Learning Objectives

Create a structured plan for your first 30, 60, and 90 days
Build relationships and credibility quickly
Identify early wins that demonstrate your value

Core Episodes

Guest	Episode Focus	Key Insight
Nikhyl Singhal	Long and meaningful career	Career strategy and transitions
Claire Vo	Product management growth	Growing in your PM role
Petra Wille	Coaching product people	Getting support as a new PM
Ethan Evans	Career growth at Amazon	The Magic Loop for career advancement

Key Frameworks

30-60-90 Day Plan - Structure your first months around listening, aligning, executing
Scrape Your Knees - Accept that painful learning is part of the journey
Optimize for Learning - Early career, prioritize learning velocity

Exercises

90-Day Plan: Write your 30-60-90 day plan. Share it with your manager for feedback.
Stakeholder Map: Identify the 10 most important relationships for your success. Rate each relationship 1-5 and create a plan to strengthen weak ones.
First Win: Identify one small, achievable win you can deliver in your first 30 days. Execute on it.

Reflection Questions

What does "success" look like for you at the 90-day mark? How will you know if you're on track?
What's the biggest knowledge gap you need to close in your first month?
Who are the 3 people whose trust you most need to earn? How will you do it?

Customization Notes

By Company Stage

Startup (< 50 people): Focus more on Module 2 (user research) and Module 4 (working with small teams). You'll likely need to be more hands-on and scrappy.
Growth (50-500): All modules apply. Pay extra attention to Module 3 (prioritization) as you'll face more stakeholder pressure.
Enterprise (500+): Module 4 (working with engineering) becomes critical as you navigate larger, more complex teams.

By Background

From Engineering: Module 2 (user research) may be the biggest growth area. Don't skip the JTBD exercises.
From Design: Module 3 (prioritization/roadmapping) and Module 4 (engineering relationships) deserve extra attention.
From Marketing/Business: Module 4 is crucial. Building credibility with engineers takes deliberate effort.

Next Steps After Completion

Deepen User Research: Take the User Research learning path
Build Strategic Skills: Progress to Product Strategy
Practice with /learn: Run /learn prioritization or /learn user interviews for interactive deep dives
Test Your Knowledge: Run /quiz first-pm-role to check your understanding