Jan 8, 2023 · 1h 8m · lennys-podcast
An inside look at how Figma builds product | Yuhki Yamashita (CPO of Figma)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview, Figma Chief Product Officer Yuhki Yamashita breaks down how Figma builds software, fosters community-led growth, and cultivates high-quality user experiences. He shares actionable frameworks on product craft, covering storytelling, internal dogfooding, the evolution of goal-setting, and hiring top product managers.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 26.1% of the talking time here. How this is scored →
Lenny as informed peer 2.6 Guest teaching 2.2 Guest disagreement 0.2 Lenny pushing back 0.2
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 39:50 Rejecting conventional OKR dogma
Yuhki candidly calls OKRs the bane of his existence and critiques how teams default to performative secondary metrics or unmovable top-line metrics.
Hardest push from Lenny ▶ 38:48 Pushing on engineer autonomy versus roadmap commitmentsLenny challenges the bottom-up model by asking how PMs avoid conflict when engineers go rogue fixing bugs instead of delivering prioritized roadmap goals.
Biggest teaching moment ▶ 40:50 The three principles of effective goal settingYuhki educates the audience and host on why OKRs fail without legibility, actionability, and authenticity, detailing Figma's iterative trial of headline goals.
Lenny holds their own ▶ 58:35 Airbnb's 'Love drives growth' insightLenny reinforces and elevates Yuhki's community-led growth thesis by citing Airbnb growth team's foundational principle that genuine product love drives sustainable scale.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| The Power of Championing a New Way of Working | 0 | 0 | 0 | 0 | Introductory teaser and host monologue introducing Yuhki Yamashita and the episode themes. No host-guest interactive debate takes place. | |
| Sponsor Messages: Notion and Vanta Compliance Solutions | 0 | 0 | 0 | 0 | Host sponsor read for Notion and Vanta. Monologue ad read with no guest interaction. | |
| Yuhki Yamashita’s Journey from Microsoft to Figma | 2 | 1 | 0 | 0 | Lenny welcomes Yuhki and asks for his career journey. Yuhki shares his trajectory across Microsoft, YouTube, Uber, and Figma in a collaborative manner. | |
| Navigating the Boundaries Between Product Management and Design | 4 | 2 | 1 | 1 | Lenny asks whether managing PMs or designers is harder. Yuhki explains the crafts-oriented challenges of managing designers, and Lenny builds on this by comparing managing PMs to managing engineers. | |
| Mastering Storytelling, Synthesis, and the Memification of Insights | 4 | 3 | 0 | 0 | Yuhki breaks down his philosophy of storytelling, synthesis, and memification in product organizations. Lenny actively synthesizes and references the concept of escaping the curse of knowledge. | |
| Owning the Why and Root-Cause Problem Solving | 2 | 3 | 0 | 0 | Yuhki explains why PMs must uniquely own the 'why' rather than solely the 'what' or 'how', citing root-cause analysis and five whys at Figma. Lenny probes on retrospective practices. | |
| Customer Proximity and the Concerning Tweets Slack Channel | 4 | 2 | 0 | 0 | Yuhki details customer proximity rituals and the creation of the 'Concerning Tweets' channel for Dylan Field. Lenny contributes background knowledge regarding Dylan's early Twitter-scraping go-to-market strategy. | |
| Behind the Scenes of Working with Dylan Field | 2 | 2 | 0 | 0 | Yuhki provides insight into working alongside Dylan Field, sharing a personal anecdote from a pandemic walk in Dolores Park. Lenny expresses admiration for Dylan's hands-on product obsession. | |
| Sponsor Message: Streamlining Data Onboarding with Flatfile | 3 | 3 | 0 | 0 | Following a sponsor spot, Lenny asks about Figma features that struggled. Yuhki explains the challenges behind adopting branching and merging workflows for enterprise design systems. | |
| Cultivating Software Quality Through Dogfooding and Accountability | 3 | 2 | 0 | 0 | Yuhki describes cultivating quality by forcing internal dogfooding, such as shifting from memos to Figma decks. Lenny highlights the clever secondary effects of forcing teams into their own software. | |
| The Evolution of OKRs and Goal Setting at Figma | 3 | 5 | 1 | 1 | Yuhki offers a masterclass on why conventional OKRs frequently fail for core product teams and outlines Figma's evolution toward headline goals and commitments. Lenny engages with deep curiosity. | |
| Hiring Top Product Managers and Unconventional Interview Questions | 2 | 3 | 0 | 0 | Yuhki explains how he evaluates PM candidates by testing their handling of controversial decisions and ability to fast-forward through trade-offs. Lenny appreciates the tactical hiring questions. | |
| Fostering Community-Led Growth and Emotional Product Resonance | 5 | 4 | 1 | 1 | Yuhki reframes standard product-led growth into community-led growth and cultivating emotional resonance. Lenny matches this by citing Airbnb's internal growth maxim 'Love drives growth, not the other way around.' | |
| Exploring the Product Vision Behind the Adobe Acquisition | 2 | 2 | 0 | 0 | Lenny asks about the strategic vision regarding the proposed Adobe acquisition. Yuhki outlines opportunities around unifying workflows and bringing real-time multiplayer tech to creative tools. | |
| Embracing a Work in Progress Mindset in Product | 4 | 2 | 0 | 0 | Yuhki reflects on product management being inherently work-in-progress. Lenny shares an anecdote about Airbnb founders reminding teams that everything around them was designed by someone. | |
| Lightning Round: Books, Media, Tools, and Widgets | 1 | 1 | 0 | 0 | Lenny leads the lightning round touching on books, podcasts, movies, internal FigJam widgets, and open roles. The dynamic is lighthearted and straightforward. |
Statements from this episode (15)
Yamashita: Designers Must Suspend Feasibility Constraints to Push Vision
“As a PM, you're kind of in the center, facilitating all these different trade-offs. And when you go into design, you kind of have to ignore some of those other aspects to really be insistent on pushing on the best experience possible. Like, just kind of suspen…”
Yamashita: Managing Designers Is Harder Than Managing Product Managers
“I would say managing designers is harder than managing product managers.”
Yamashita: PMs Succeed When Executives Organically Quote Their Insights
“There are certain insights, data insights, research insights that were memified to the point where, like, someone like Travis or Dara would just cite this insight in the middle of a meeting, and you know that you've really done your job as maybe a researcher o…”
Figma leadership created a 'Concerning Tweets' Slack channel for Dylan Field
“So Chris, RCTL, and I kind of, like, intervened. We created this new channel, private channel called Concerning Tweets. And it's just, you know, for this small group of us that Dylan can kind of, like, drop those. And then these are tweets that aren't going vi…”
Yamashita: Dylan Field Needs to See End Implementations to Buy In
“For Dylan, I think it's very hard for him to really kind of like fully get bought in until he kind of sees like the end implementation to this really feel like if this is a good solution or not.”
Figma's branching feature saw low initial adoption despite user demand
“So in theory makes a lot of sense and things that our customers asked us for. But once we built it, you know, in the initial stages, didn't really see that much adoption. And, you know, it didn't feel great because it was like a really big investment for us.”
Yamashita: Dogfooding fails as quality control when building for external workflows
“And so I think as we're getting bigger, one of the things that I'm realizing is that we're starting to build a lot of features that are not necessarily for organizations like ours. And when we do that, we really need to be creative about how we understand how …”
Yamashita: Figma shifted to deck culture to increase internal dogfooding
“Like one of the first things I did when I arrived was, we're a little bit more of a memo culture. And I was like, you know what, we should be a deck culture, because we can build those decks in Figma.”
Yamashita: Engineers estimate half the time on ideas they advocate
“If you ask an engineer about how much time it'll cost to go and build something, and it's something that they came up with, or they're advocating for, it's almost always half the time as something that, like, you are asking for as a PM, right?”
Yamashita: Deprecated formal OKRs at Figma in favor of qualitative headlines
“And so that was when I kind of deprecated it on, you know, and said, I just want to understand, like, your headline, like, what are you trying to do, like, philosophically? And just, like, don't stress about whether you can measure it or not. I just want to un…”
Yamashita: Good OKRs require legibility, actionability, and authenticity
“I think that like, for me, there are three things that really matter about like a good OKR. And One is legibility. Like, people look at it and understand What it is, and like, it's not some, like, weird, obfuscated metric that doesn't mean anything to any work…”
Yamashita: Asking PM candidates about controversial decisions reveals perspective-taking ability
“One of my favorite interview questions It's asking, describe to me a time when you're part of, like, controversial product decision, right? And, you know, what did you do, and all those things, and I think it's really revealing because, you know, if they can k…”
Yamashita: Great PMs fast-forward experimental outcomes to decide what not to build
“The kind of PMs that have the ability to kind of imagine those outcomes, I think, like, it helps us be much more efficient, too, because we're like, well, if we all think that's going to Go there. And that's not going to compel us to take any action. Why do it…”
Yamashita: Figma's PLG operates by empowering internal user champions
“One of the things that I kind of, we all are collectively realizing is, you know, we talk about product-led growth, but in some ways, you know, I like to think about it more as kind of like community-led growth, or there are certain people inside a company tha…”
Yamashita: Figma uses an alignment scale widget to pulse-check product reviews
“We have this one called the alignment scale, which is a widget that you can insert into FigJam or Figma design actually, but, and we use it all the time. So basically, it's just a simple scale. And whenever people click it, their face appears on one end of the…”