The Foundational Three Entry Path
Don't start in PM. Start as the person you'd be taking PM responsibilities from — engineer, designer, or seller.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 88%
Kevin Yien discourages people from entering product management directly. His model: product management (the practice, not the person) exists to convert a team's potential energy into realized customer value with minimum loss. In a new product, the people best placed to do that are the ones actually building and selling it. So the entry path is to first do one of the three jobs whose responsibilities you'd later take on — engineer, designer, or salesperson — and only then step into PM carrying a genuinely unique perspective.
Origin
Kevin Yien's own framing, built on a potential/kinetic energy analogy from high-school physics; he arrived at PM via engineering himself. He cites Stripe, Twilio, Figma and Snap (which waited until ~200 people to hire its first PM) as evidence that PM activities get done by builders long before a PM exists.
Core principles
- 01Product management is a practice, not a person — the activities must happen whether or not the title exists.
- 02Companies building for themselves (designers for designers, engineers for engineers) genuinely need no PM; you delegate to a PM only when you are not your own customer.
- 03The PM's job is to convert the team's potential energy into realized customer value with minimum loss.
- 04The best salespeople are the best listeners — sales is an underrated PM feeder role, not a quota job.
- 05Do not frame the move as settling; frame it as doubling down on where you might be world-class.
How to run it
- 1
Identify whose responsibilities you'd be taking
Ask who currently does the PM activities on a team that has no PM. Those are the roles to learn: engineer, designer, or salesperson — the foundational three.
- 2
Do one of those jobs for real
Take the role and work inside the smallest possible loop of building and shipping. This gives you the maximum exposure to what it actually takes to build a good product.
Pro tip If you choose sales, treat it as listening reps: getting told no a lot and learning to translate a customer's problem into what you can do for them is direct PM training.
- 3
Notice the ceiling, and reframe it correctly
At some point you'll realize you'll never be a world-class engineer or designer. The wrong conclusion is 'so I'll settle for PM'. The right one is: 'I'm okay at those things, I'm potentially world class at this other thing — let me double down.'
Watch out The settling frame poisons the transition; you will carry it into how you show up with your engineers and designers.
- 4
Move into PM carrying the craft as your edge
Enter product management with the foundational craft as your unique perspective — the thing that lets you draw useful constraints and earn the trust of the people you now work with.
Pro tip Also build the writing muscle: writing is clarity at scale, and if you can't sell or support your own product, you shouldn't be trusted to build it.
In the wild
Stripe, Twilio, and Figma are the standard 'we never needed PMs' references — and all were building for themselves: designers for designers, engineers for engineers. Snap waited until roughly 200 people before hiring its first PM.
→ The PM activities were being done all along by builders who were also the customer. The role becomes necessary when you are not the customer, the space is complex, or the builders don't want to do the PM work.
Lenny started as an engineer, realized he'd never be an amazing engineer but was good enough, and noticed he was better at the adjacent product work.
→ The transition worked — but Yien's correction is the framing: not 'I couldn't be world class at engineering' but 'I might be world class here, let me find out.'
Common mistakes
Jumping straight into PM
Without a foundational craft you have no unique perspective to bring, and no basis for the engineers and designers you work with to trust your opinion.
Framing the move as settling
'I'll never be world class at engineering so I'll be a PM' is a corrosive narrative. The productive version is doubling down on a potential strength, not retreating from a ceiling.
Dismissing sales as a feeder role
Sales gets a misrepresented reputation as a quota job. The best salespeople are the best listeners and best problem-translators — precisely the PM skillset, learned under pressure.
Is it for you?
Best for
Students, career-changers, and early-career people who want to become product managers and are deciding what job to take first.
Not ideal for
Experienced PMs already in the role, or people at companies where they themselves are the target customer and can skip the intermediary entirely.
From the transcript
“who are the people that you would be sort of taking the PM responsibilities from and then do those jobs and so for me the…”
“the purpose of product management not the person but the practice is to convert that potential into as much realized value for someone as possible”
“I'm okay at those things I'm potentially world class at this other thing let me see what it feels like to double down in this…”
From the episode
Unorthodox PM wisdom: Automating user insights, unselling job candidates, logging every decision, more
Kevin Yien (Stripe, Square, Mutiny)