How Figma Builds:
Story, Why & Community

Yuhki Yamashita

Chief Product Officer, Figma
Previously: Uber · Google (YouTube) · Microsoft

JAN 8 2023

Core Concept

Storytelling Is the PM Superpower

"If you've ever reported to me, storytelling has showed up in some kind of performance review. That's how much I care about it."

Synthesis: Distill many voices into one clear thesis — like literary commentary
Memification: Make insights so sticky that executives cite them unprompted in meetings
Escape the curse of knowledge: Reset your mental model and tell the story from zero context
Teaching discipline: Yuhki learned storytelling explaining pointers to CS students — if any student gets it, you've done your job

Framework

PMs Own the Why — Not the What or How

The what and how are shared — designers, engineers, and customers all generate ideas
Only the PM is uniquely responsible for the why
When teams know the why, they make great local decisions without the PM in the room — the only way to scale
Apply the Five Whys to customer requests: back up to the root problem, then ask — can I fix the underlying condition entirely?

The YouTube lesson

At Microsoft, Yuhki wrote perfect specs for every scenario. At YouTube, he owned an entire iOS app. Engineers made their own calls. The only way to scale: ensure everyone deeply understands why we're building this.

Five Whys — for product discovery

Customer asks for feature → Why? → Back up to the problem → Why do they have that problem? → Fix the underlying condition. One more step = 10x the product impact.

Figma uses this in engineering Five whys in postmortems: each "why" surfaces the root cause. Yuhki applies the same logic to product discovery.

Deep Dive

Radical Customer Proximity & OKRs That Actually Work

Customer Obsession

Dylan Field reads more customer feedback than anyone at Figma — after a decade, he still does it daily
"Concerning Tweets" channel: a private Slack where Dylan drops zero-like tweets that feel signal-heavy — canaries in the coal mine, not viral complaints
Balance tweets with support tickets, sales calls, usage data — never let one source create blind spots in your portfolio
Dog-food relentlessly: switched Figma from memos to Figma decks so PMs encounter real issues daily; ran performance calibrations in FigJam so all of HR uses the product

Dylan's customer obsession in action During a pandemic walk, Dylan used Yuhki's bathroom, met his partner who had Figma open, and immediately asked them about their biggest frustrations — completely genuine, not performance.

OKR Philosophy

Yuhki's love-hate journey: task lists → headlines → back to OKRs → still iterating. Three things make any goal system work:

1. Legibility People look at it and instantly understand it. No obfuscated proxy metrics that nobody really cares about.

2. Actionability It stirs action. Someone reads it and immediately wants to do something differently.

3. Authenticity It honestly describes what the team does day-to-day — not a post-rationalization bolted onto pre-decided projects.

Tactics

Hiring PMs & Community-Led Growth

Interview Signals

"Tell me about a controversial product decision." — Can they represent both sides without losing their own view?
"Describe a big problem you worked on." — Do I feel compelled to work on it after they finish?
Look for fluency across altitudes: move between macro vision and micro interaction without losing thread
"Fast-forward" thinking: if you already ran that experiment, what result do you predict and why?

PLG = Community-Led Growth

Figma's real engine: internal champions who evangelize to their organizations
Sales' job: equip those champions with data, stories, and executive connections — not replace them
Friends of Figma: geographic hubs that build loyalty and give users the courage to push Figma internally

Love drives growth Build authentic love for the product first — internally and externally. Equip users with a philosophy to champion, not just a tool.

Contrarian

Yuhki's Takes That Challenge Product Orthodoxy

✗ PMs should own the idea — that's what makes them the product leader INSTEAD → ✓ PMs own the why, not the idea. Customers, designers, and engineers all generate ideas. Your unique job is to hold the reason we are building at all.

✗ OKRs are the gold standard — just set them and track them INSTEAD → ✓ Most OKRs are either unmovable goals or unmeaningful metrics. A goal only works if it passes three tests: legible, actionable, and authentic.

✗ Product-led growth means letting the product sell itself — no sales needed INSTEAD → ✓ PLG is really community-led growth. Sales empowers the internal champion — it does not replace them. The salesperson is the champion's support team.

✗ Engineers building bottom-up without PM direction creates chaos INSTEAD → ✓ Bottom-up energy often beats top-down quality metrics. Engineers who personally experienced the bug fix it twice as fast. Personal accountability beats KPIs every time.