By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
Lenny's PodcastAn inside look at how Figma builds product | Yuhki Yamashita (CPO of Figma)
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
Inside Figma’s Playbook: Storytelling, Community, And Product-Led Growth
- In this episode, Figma CPO Yuhki Yamashita walks through his career from Microsoft, Google/YouTube, and Uber to Figma, and how those experiences shaped his product philosophy. He emphasizes storytelling, ownership of the “why,” and deep proximity to customers as core PM superpowers. Yuhki describes how Figma builds consistently high-quality products through obsessive dogfooding, tight feedback loops with a passionate design community, and a distinct approach to OKRs and goal-setting. He also explains Figma’s flavor of product-led, community-led growth and reflects on working with CEO Dylan Field and the potential future with Adobe.
IDEAS WORTH REMEMBERING
5 ideasGreat product managers are great storytellers and synthesizers.
Yuhki sees PM work as narrative-building: distilling many inputs into a clear thesis, making insights memorable (even “memefied”), and crafting stories that drive concrete action across distracted stakeholders.
PMs must uniquely own the “why,” not necessarily the ideas or the “what.”
Ideas can come from designers, engineers, or customers, but PMs are accountable for articulating why something matters, what problem it solves, and giving everyone enough context to make good local decisions at scale.
Proximity to customers must be continuous, multi-channel, and champion-led.
Figma leans heavily on Twitter/X, user feedback, support tickets, sales conversations, and programs like Friends of Figma, while recognizing the need to balance loud voices with research and data to avoid blind spots.
Internal dogfooding creates personal accountability and drives quality.
By forcing more of the company to work inside Figma/FigJam (e.g., switching from memos to decks, running performance calibrations in FigJam), problems become impossible to ignore and builders feel personally responsible to fix them.
OKRs are only useful if they’re legible, actionable, and authentic.
Figma has iterated through several goal-setting approaches, struggling with metrics that either don’t truly matter or that teams can’t realistically move; they now focus more on clear “headlines” and honest reflections than rigid metrics theater.
WORDS WORTH SAVING
5 quotesI actually think that a lot of being a great product manager is being a great storyteller.
— Yuhki Yamashita
The PM doesn’t have to come up with the idea, but they must own the why.
— Yuhki Yamashita
There has to be this almost irrational, emotional response to your product—this love for it.
— Yuhki Yamashita
It’s really easy to listen to some of these podcasts and feel like these people have everything figured out. The reality is, we haven’t.
— Yuhki Yamashita
If this is the future of design, I’m quitting… I’m changing careers.
— Yuhki Yamashita (quoting an early Figma user reaction)
High quality AI-generated summary created from speaker-labeled transcript.
