Unorthodox PM tips: Automating user insights, unselling candidates, decision logs, more | Kevin Yien
Kevin Yien (guest), Lenny Rachitsky (host), Christina (OneSchema) (guest)
In this episode of Lenny's Podcast, featuring Kevin Yien and Lenny Rachitsky, Unorthodox PM tips: Automating user insights, unselling candidates, decision logs, more | Kevin Yien explores unorthodox PM tactics: decision logs, unsell emails, automated research, more Stripe product leader Kevin Yien shares unconventional but highly practical approaches to product management, hiring, and personal growth. He argues aspiring PMs should first build foundational experience in adjacent roles (engineering, design, sales), and insists great PMs must be great writers who create clarity at scale for both teams and customers. Yien details tactics like keeping a personal decision log, sending "unsell" emails to candidates, and automating user research via sales tools and workflows. He also discusses failure, AI’s impact on younger generations, and how to build healthier perspectives on career setbacks.
Unorthodox PM tactics: decision logs, unsell emails, automated research, more
Stripe product leader Kevin Yien shares unconventional but highly practical approaches to product management, hiring, and personal growth. He argues aspiring PMs should first build foundational experience in adjacent roles (engineering, design, sales), and insists great PMs must be great writers who create clarity at scale for both teams and customers. Yien details tactics like keeping a personal decision log, sending "unsell" emails to candidates, and automating user research via sales tools and workflows. He also discusses failure, AI’s impact on younger generations, and how to build healthier perspectives on career setbacks.
Key Takeaways
Treat PM as converting team potential into customer value, not as a default role every team needs.
Yien frames product management as turning the potential energy of engineers, designers, and others into real customer value with minimal loss. ...
Get the full analysis with uListen AI
Build PM foundations by first doing adjacent roles like engineering, design, or sales.
Rather than jumping directly into PM, Yien recommends starting where you’d otherwise “delegate” PM work—from shipping code, designing experiences, or selling/supporting customers—to gain firsthand understanding of building and serving products, then layering PM responsibilities on top.
Get the full analysis with uListen AI
Great PMs must be strong writers because writing is “clarity at scale.”
Writing sharp PRDs, user messaging, and internal docs clarifies thinking and aligns teams and customers. ...
Get the full analysis with uListen AI
Draw tight constraints (“the perimeter”) and still own product quality down to tiny details.
PMs should define constraints like target user, jobs-to-be-done, platforms, and key principles (e. ...
Get the full analysis with uListen AI
Use a personal decision log to deliberately build product sense.
Yien defines product sense as making good decisions with insufficient data. ...
Get the full analysis with uListen AI
Improve hiring quality with an “unsell” email that front-loads the hard truths.
At offer stage, he sends a concise list of the job’s toughest realities tailored to each candidate’s fears (e. ...
Get the full analysis with uListen AI
Automate user research by tapping sales calls and customer intent signals.
Yien treats sales as a research function and uses tools like Gong and Zapier to trigger alerts on key terms, capture contact details, and auto-send calendar links for interviews. ...
Get the full analysis with uListen AI
Reframe layoffs and mismatches as fit problems, not proof of personal inadequacy.
After being laid off while his wife was nine months pregnant, Yien wrestled with the belief he “wasn’t a real PM. ...
Get the full analysis with uListen AI
Notable Quotes
“Writing is clarity at scale.”
— Kevin Yien
“If you can't sell or support your own product, I don't trust you to build the product.”
— Kevin Yien
“We all talk about product sense. To me, it's just a fancy way of saying you can make good decisions with insufficient data.”
— Kevin Yien
“PMs need as many reps as possible in making decisions, documenting the rationale behind those decisions, and then crucially, seeing the outcome of them.”
— Kevin Yien
“We are not even beneath the dust on the surface when it comes to what's gonna change.”
— Kevin Yien (on AI)
Questions Answered in This Episode
How might your product decisions change if you rigorously logged and later reviewed the rationale and outcomes behind them for a full year?
Stripe product leader Kevin Yien shares unconventional but highly practical approaches to product management, hiring, and personal growth. ...
Get the full analysis with uListen AI
In your current company, are PMs truly converting team potential into customer value—or are they mostly operating internally, and what would it take to change that?
Get the full analysis with uListen AI
What would an honest ‘unsell’ email look like for your team or company, and how might sending it change the type of people who join and stay?
Get the full analysis with uListen AI
If you automated a stream of customer conversations tomorrow (via sales calls, site prompts, or community monitoring), what specific questions would you ask to sharpen your mental model of users?
Get the full analysis with uListen AI
Looking at your last major career setback or rejection, how much of it was about your skills versus a mismatch with the environment—and what kind of habitat would let you be at your best?
Get the full analysis with uListen AI
Transcript Preview
... the PM job can become a little too internal. Influencing my stakeholders, and getting alignment, and all these things. But if you can't sell or support your own product, I don't trust you to build the product.
You think every PM should keep a decision log.
We all talk about product sense. To me, it's just a fancy way of saying you can make good decisions with insufficient data. PMs need as many reps as possible in making decisions, documenting the rationale behind those decisions, and then crucially, seeing the outcome of them.
You have a lot of interesting approaches to hiring, including this idea of a unsell email.
When you get to offer stage, I send an email and I say all the terrible things that are probably going to reinforce their fears. If you can tell them that upfront and they can read that whole email and still be equally excited to join, you found yourself an A+ hire.
I'm curious if you found any interesting uses of AI in your work.
We are not even beneath the dust on the surface when it comes to what's gonna change.
Today my guest is Kevin Yien. Kevin leads product for merchant experiences at Stripe. Before that, he built a restaurant business and the ecosystem teams at Square, and most recently was head of product and design at Mutiny. He also makes ice cream, and as you'll hear in their conversation, was a pretty competitive eater for some part of his life. In our conversation, Kevin shares a ton of unique and insightful perspectives on how to be a successful product manager, including how to get into product management, how to improve your relationship with your engineers and designers, bunch of advice on hiring, why you should keep a decision log, how to automate your customer research, plus a ton of really powerful stories around failure and AI and career. This episode is for anyone looking to become a better leader, thinker, and builder of products. If you enjoy this podcast, don't forget to subscribe and follow it in your favorite podcasting app or YouTube. It's the best way to avoid missing future episodes, and it helps the podcast tremendously. With that, I bring you Kevin Yien. Kevin, thank you so much for being here and welcome to the podcast.
Thanks, Lenny. I am humbled to be here.
I've been a big fan of yours from afar. I've been following you on Twitter for a long time. You have a very distinct profile photo that I feel like you maybe not, haven't changed for a long time. How long have you had this, this profile?
Oh, gosh. Probably 2011 or 2012. The story behind that is-
Mm-hmm.
... I was inspired actually by Chris Dixon's avatar at the time, and I wanted something really similar to it, but I couldn't figure out how to. Luckily, I was dating a designer at the time, uh, and so she made me that sort of custom pic-
Install uListen to search the full transcript and get AI-powered insights
Get Full TranscriptGet more from every podcast
AI summaries, searchable transcripts, and fact-checking. Free forever.
Add to Chrome