An inside look at how Figma builds product | Yuhki Yamashita (CPO of Figma)

Episode Summary

Executive Summary: Yuki Yamashita, CPO at Figma, explains how Figma builds products through storytelling, deep customer proximity, internal dogfooding, and a strong community-led growth model. He emphasizes that PMs should own the “why,” that product development should stay authentic and legible, and that teams must experiment openly—even with goal-setting systems like OKRs.

Main Topics: Yuki’s career path and product philosophy (Priority: 5/5): Yuki traces his path from Microsoft to YouTube, Uber, and Figma, highlighting how working across PM and design shaped his view that great product leadership requires empathy, cross-functional fluency, and an obsession with user experience. Storytelling as a core PM skill (Priority: 5/5): He argues that effective PMs synthesize complex input into a clear narrative or meme that drives action, helps teams align, and makes ideas memorable enough to spread throughout the organization. PMs own the 'why' (Priority: 5/5): Yuki believes product managers are uniquely responsible for articulating the purpose behind a product decision, enabling decentralized teams to make better local decisions and scale coherent product thinking. Customer proximity and community feedback loops (Priority: 5/5): Figma’s product process is grounded in constant customer feedback, from user conversations to public Twitter signals. Yuki describes this as a way to keep a pulse on customer sentiment without overreacting to any single source. Building quality through dogfooding and accountability (Priority: 4/5): Figma uses its own tools internally to force constant exposure to product friction. Yuki says personal accountability—seeing real users or feeling the pain yourself—dramatically improves quality and motivation to fix problems. OKR experimentation and skepticism (Priority: 4/5): Yuki shares Figma’s evolving approach to goals, describing frustration with conventional OKRs when they become either unmeasurable vanity metrics or disconnected task lists. He values legibility, actionability, and authenticity over rigid frameworks. Product-led growth as community-led growth (Priority: 5/5): Yuki frames Figma’s growth as driven less by sales alone and more by empowered internal champions, community advocacy, and a product that represents a new way of working that users want to champion.

Key Arguments: Storytelling is a foundational PM skill because it synthesizes dispersed inputs into a clear thesis that others can remember and act on. PMs should own the 'why' of a product because distributed teams need a shared purpose to make strong local decisions without constant central oversight. Customer proximity matters most when it creates a balanced feedback portfolio; vocal social signals are useful, but they must be weighed against support, sales, and broader customer data. Internal dogfooding increases product quality because it creates firsthand exposure, personal accountability, and stronger motivation to fix issues. OKRs often fail when they become either fake precision or disconnected bureaucracy; teams should optimize for a clear headline, then measure more thoughtfully over time. Figma’s growth succeeds because users aren’t merely adopting a tool—they’re championing a collaborative philosophy and new workflow. The best PMs can move fluidly between problem framing and solution space, quickly exploring alternatives and imagining outcomes before investing heavily.

Data Points: Figma tenure: Almost 4 years - Yuki says he has been CPO at Figma for nearly four years. Company PM headcount: 22 product managers - Yuki says Figma has 22 PMs, which he frames as small for the company’s scale. Newsletter popularity: 4th most popular post of all time - Lenny says the prior interview post on how Figma builds product became his fourth most popular newsletter post. Internal use frequency: About 6 hours a day - Yuki says designers inside Figma are in the product roughly six hours a day. Automation impact from Vanta: Up to 90% of SOC 2 work - Sponsor read states Vanta automates up to 90% of SOC 2 compliance work. Vanta customer count: 3,000+ fast-growing companies - Sponsor read cites Vanta’s customer base. SOC 2 timeline improvement: Weeks instead of months - Sponsor read says Vanta can prepare companies for audits much faster than traditional methods. Discount offer: $1,000 off - Sponsor read offers Lenny’s listeners $1,000 off Vanta. Podcast post rank: #1 search result for 'how Figma builds product' - Lenny says the newsletter interview comes up first in search.

Pivotal Quotes: "If this is the future of design, I'm quitting, right? I'm changing careers." — Lenny quoting early reaction to Figma: Used to illustrate how controversial Figma’s collaboration model felt at the start. "PMs own the why." — Yuki Yamashita: Core principle of product management at Figma: PMs define the purpose behind product decisions. "We live in a work in progress world." — Yuki Yamashita: Explains Figma’s experimental mindset toward strategy, product processes, and goal-setting.

Implications: For PMs and founders, the episode argues that narrative clarity, customer intimacy, and authentic team alignment matter more than rigid frameworks. Figma’s model suggests community and product can reinforce each other when the product embodies a compelling new way of working.