First PM hires at startups, founders transitioning PM duties, PMs joining early-stage companies
Learning Path: Founding PM
Who This Is For
You're the first PM hire at a startup, taking over product responsibilities from founders. Or you're a founder who needs to build PM capabilities. Or you're a PM joining an early-stage company where "scrappy" is the only option. This path covers finding product-market fit, building without resources, working with founders, and eventually scaling the PM function.
What You'll Learn
- Understand the unique role of a founding PM and what success looks like
- Find and validate product-market fit through systematic discovery
- Build products with minimal resources by doing things that don't scale
- Work effectively with founders while maintaining your own judgment
- Know when and how to scale from 1 PM to a PM team
Time Commitment
- Total Estimated Time: 15-18 hours
- Recommended Pace: 3-4 hours/week over 5 weeks
- Can Be Compressed: Yes, to 3 weeks for intensive study
Module 1: The Founding PM Role
Estimated Time: 3-4 hours
Learning Objectives
- Understand what makes the founding PM role unique
- Identify the skills and mindset needed to succeed
- Navigate the relationship between PM and founder(s)
Core Episodes
| Guest | Episode Focus | Key Insight |
|---|---|---|
| Todd Jackson | Product-market fit framework | What founding PMs need to nail |
| Dalton Caldwell | YC and startup advice | The startup mindset |
| Nabeel S. Qureshi | Palantir founder factory | Operating in high-ambiguity environments |
| Claire Butler | Early-stage marketing | Being a generalist at early stage |
Key Frameworks
- First PM from Within - First PMs often come from within the team
- Radical Accountability - Every problem is your problem
- Generalist Product Teams - Maximize skills per person
Exercises
Role Definition: Write a job description for your founding PM role. What will you own? What will you not own? Get founder alignment.
Skills Inventory: Map your skills against what the company needs. Where are you strong? Where will you need to grow or find help?
Decision Rights: Clarify with founders: What decisions can you make alone? What needs their input? What do they decide?
Reflection Questions
- What's the difference between being a founding PM and being a PM at a larger company?
- How do you add value when founders already have strong product intuition?
- What should you prioritize in your first 30 days?
Module 2: Finding Product-Market Fit
Estimated Time: 3-4 hours
Learning Objectives
- Recognize the signs of product-market fit (and lack thereof)
- Build systems to measure and track PMF progress
- Iterate rapidly when PMF isn't there yet
Core Episodes
| Guest | Episode Focus | Key Insight |
|---|---|---|
| Rahul Vohra | Superhuman's success | The PMF survey and methodology |
| Eric Ries | Lean Startup methodology | Validated learning over vanity metrics |
| Mike Maples Jr | Pattern Breakers startup ideas | Finding inflections and insights |
| Todd Jackson | Product-market fit framework | Signs you've found (or haven't found) PMF |
Key Frameworks
- Reference Customer Development - Find customers who stake their reputation on you
- Co-Creation Product Development - Build with alpha users, not just for them
- PMF Survey - "How would you feel if you could no longer use this product?"
Exercises
PMF Survey: Run a PMF survey with your users. What percentage say they'd be "very disappointed" without your product?
Reference Customer Identification: Identify 5 customers who might become reference customers. What would it take to get them there?
Pivot Signals: Define 3 signals that would tell you PMF isn't working and you need to change direction.
Reflection Questions
- How do you know if you have PMF vs. just enthusiastic early adopters?
- When do you keep iterating vs. pivot to something new?
- What's the role of intuition vs. data in finding PMF?
Module 3: Building Without Resources
Estimated Time: 3-4 hours
Learning Objectives
- Do things that don't scale to learn faster
- Test ideas with minimal engineering investment
- Build scrappy solutions that validate before you invest
Core Episodes
| Guest | Episode Focus | Key Insight |
|---|---|---|
| Brian Chesky | Founder mode and Airbnb | Do things that don't scale |
| Dalton Caldwell | YC and startup advice | The scrappy startup playbook |
| Nikita Bier | Consumer app building | Rapid iteration in consumer |
| Ryan Hoover | Product Hunt story | Building with community |
Key Frameworks
- Do Things That Don't Scale, Then Scale Them - Start manual, identify what works, then automate
- Wizard of Oz Testing - Fake the product with manual processes
- Build the Scooter, Not the Axle - Build a complete small thing first
Exercises
Manual Process Audit: Identify 3 things in your product that could be done manually instead of built. Try one for a week.
Wizard of Oz Experiment: Design a Wizard of Oz test for a feature you're considering. What would you learn?
Time-to-Value Compression: Map your onboarding flow. How could you get users to value 10x faster if engineering wasn't a constraint?
Reflection Questions
- What's the minimum you could build to test your biggest assumption?
- When does "scrappy" become "crappy"?
- How do you balance learning speed with user experience?
Module 4: Working with Founders
Estimated Time: 3-4 hours
Learning Objectives
- Understand founder psychology and how to work within it
- Know when to push back and when to defer
- Capture and codify founder intuition
Core Episodes
| Guest | Episode Focus | Key Insight |
|---|---|---|
| Brian Chesky | Founder mode and Airbnb | Why founders stay deeply involved |
| Tobi Lutke | Energy source and building | The founder's relationship to product |
| Stewart Butterfield | Mental models for products | How founders think about product |
| Shishir Mehrotra | Rituals of great teams | Mechanisms for founder-team alignment |
Key Frameworks
- Founder Mode - Why founders stay deeply involved in product
- Context Not Control - Share information so people can decide well
- Flash Tags - Signal conviction level to prevent over-indexing on founder opinions
Exercises
Founder Interview: Have a structured conversation with your founder(s). What's their product vision? What are their non-negotiables? What do they most want to delegate?
Design Tenets: Work with founders to document the product's design tenets—the principles that guide decisions when opinions differ.
Decision Log: For the next month, track major product decisions. Who made them? How did founder input flow?
Reflection Questions
- How do you add value when the founder has stronger product intuition than you?
- When should you fight for your position vs. defer to founder judgment?
- How do you prevent "founder mode" from becoming micromanagement?
Module 5: Scaling the PM Function
Estimated Time: 2-3 hours
Learning Objectives
- Recognize when it's time to hire more PMs
- Structure the team as it grows
- Avoid common scaling mistakes
Core Episodes
| Guest | Episode Focus | Key Insight |
|---|---|---|
| Lane Shackleton | What sets great teams apart | Team structure at scale |
| Adam Fishman | Building high-performing growth teams | Growing a product/growth team |
| Molly Graham | Rapid career growth frameworks | Scaling yourself and your team |
| Claire Vo | Product management growth | Growing PM capabilities |
Key Frameworks
- First 10 Hires Discipline - Be patient early, accelerate after PMF
- Title Delay Strategy - Delay senior titles to enable future flexibility
- Product Talent Portfolio - Balance skillsets rather than hiring in your image
Exercises
Hiring Trigger: Define the signals that would tell you it's time to hire your second PM. What would they own?
Org Structure Draft: If you had 3 PMs, how would you structure responsibilities? What would you own vs. delegate?
Onboarding Design: Design the onboarding you wish you'd had. This becomes the template for your next hire.
Reflection Questions
- What's more important: hiring fast or hiring right?
- How do you maintain startup culture as the PM team grows?
- What should you keep doing yourself even as you scale?
Customization Notes
By Company Stage
- Pre-PMF: Focus on Modules 2-3. Finding PMF is your only job.
- Post-PMF, Pre-Scale: Modules 4-5 become important as you systematize and grow.
- With Technical Founders: Module 4 is critical—navigating the founder relationship is nuanced.
By Your Background
- From Big Company PM: Module 3 (scrappy building) requires the biggest mindset shift.
- From Engineering: Module 4 (founder dynamics) may be new territory.
- From Non-PM: Combine with First PM Role for fundamentals.
Next Steps After Completion
- User Research Skills: Deep dive with User Research
- Strategic Foundation: Build with Product Strategy
- Interactive Learning: Run
/learn product-market-fitor/learn startup-pm - Test Knowledge: Run
/quiz founding-pmto validate understanding - Growth Skills: When ready, progress to Growth Fundamentals