Yuhki Yamashita (CPO of Figma)08 January 2023

An inside look at how Figma builds product

7Frameworks

15Insights

Episode overview

Lenny Rachitsky talks with Figma CPO Yuhki Yamashita about the career experiences and storytelling habits that shaped his approach to product leadership. Yamashita explains Figma's emphasis on customer proximity, internal product use, community-led growth, and empowering teams to understand the “why” behind their work. They also examine Figma's experiments with goals and OKRs, its hiring criteria, collaboration with sales, and the possibilities surrounding Adobe's then-pending acquisition.

Key ideas

Product managers should own and communicate the “why” so designers and engineers can make sound local decisions without exhaustive specifications.
Strong product storytelling depends on synthesis, accessibility, memorability, and an ability to frame problems from the perspective of someone without context.
Figma stays close to customers through direct feedback, social channels, support and sales inputs, while balancing vocal feedback with research and behavioral data.
Using your own product extensively creates personal accountability and exposes quality problems; Figma encourages this through decks, reviews, and performance calibration in Figma and FigJam.
Bottom-up fixes from motivated designers and engineers can improve product quality more effectively than purely top-down quality programs.
Useful goals should be legible, actionable, and authentic; Figma repeatedly revised its OKR process when metrics became performative or disconnected from daily work.
Figma's growth is described as community-led: passionate internal champions are equipped with data, stories, and a philosophy of collaborative work to drive adoption.
Yamashita looks for product managers who can tell compelling stories, represent competing perspectives, navigate solution branches quickly, and anticipate likely research or experiment outcomes.

Transcript available · source text is retained privately and is not published

Frameworks in this episode

Marketing6 steps

Community-Led Growth: Equip the Champion

The salesperson is the designer inside the company — your job is to make them a superhero.

Read →

Leadership5 steps

Legibility, Actionability, Authenticity

Three tests any goal must pass, regardless of whether you call it an OKR.

Read →

Innovation5 steps

Manufactured Dogfooding

Invent internal reasons for every function to live in your product — quality follows hours logged.

Read →

Communication5 steps

Synthesis-to-Meme Storytelling

Turn scattered inputs into one distilled idea leaders can repeat from memory in a meeting.

Read →

Strategy5 steps

The Balanced Feedback Portfolio

Treat every feedback channel as a biased sensor, then hold a portfolio so you have no blind spots.

Read →

Leadership4 steps

The Compelled-to-Work-on-It PM Interview

Hire PMs by testing whether their story makes YOU want to go work on their boring old problem.

Read →

Leadership5 steps

The PM Owns the Why

Don't spec the what — distribute the why so hundreds of local decisions come out right.

Read →

People & resources mentioned

Attributed to the moment in the episode. Timestamps are approximate.

People · 13

Yuhki YamashitaMentionsYuki is Chief product officer at figma where he's been for almost four years
“today my guest is Yuki yamashida Yuki is Chief product officer at figma”
▶ Watch at ~1:00approx.
Lenny RachitskyMentionstoday we've got another very special compilation episode something I've been pulling on more and more with the podcast and the newsletter
“welcome to Lenny's podcast I'm Lenny”
▶ Watch at ~1:00approx.
Yuhki YamashitaMentionsYuki is Chief product officer at figma where he's been for almost four years
“Yuki welcome to the podcast”
▶ Watch at ~4:30approx.
Susan WojcickiMentionsReferenced as part of Google's leadership during its shift from traditional broadcast advertising toward YouTube.
“I believe sincere has been on on this podcast before yes this year was leading YouTube at the time”
▶ Watch at ~6:00approx.
W. B. YeatsMentionsmentioned
“you're reading like uh William Yates poem and you're trying to kind of like You observe all these interesting things”
▶ Watch at ~14:00approx.
Travis KalanickMentionsFormer Uber leader discussed as a visionary product leader during the company's early era.
“someone like Travis or Dara was just like this Insight in the middle of a meeting”
▶ Watch at ~15:30approx.
Dara KhosrowshahiMentionsmentioned
“someone like Travis or Dara was just like this Insight in the middle of a meeting”
▶ Watch at ~15:30approx.
Dylan FieldCoinedthat's something Dylan's really good out is trusting his intuition and gut
“way back when when Dylan the small group of people were building figma”
▶ Watch at ~23:00approx.
Dylan FieldMentionsthat's something Dylan's really good out is trusting his intuition and gut
“Dylan's always reading customer feedback and pro infections reads the most customer feedback of all of us”
▶ Watch at ~25:00approx.
Jeff HoldenMentionsat Uber our first estate product Officer Jeff Holden was someone who often talks about kind of fast forwarding to the Future
“at Uber our first estate product Officer Jeff Holden was someone who often talks about kind of fast forwarding to the Future”
▶ Watch at ~50:30approx.
Scott BelskyMentionsHe's a former founder starting a company called Behance that he sold to Adobe where he worked up the ranks to chief product officer
“you also get to work with Scott belsky which is going to be pretty sweet”
▶ Watch at ~1:01:30approx.
Brian CheskyMentionsBrian chesky at Airbnb there was a whole article where we unpacked this moment in their product development cycle
“Airbnb Founders always came back to Joe and Brian were both designers”
▶ Watch at ~1:03:00approx.
Joe GebbiaMentionsAt Airbnb, he discussed employees identifying with both their discipline and cross-functional team.
“Airbnb Founders always came back to Joe and Brian were both designers”
▶ Watch at ~1:03:00approx.

Resources · 51

Harvard UniversityMentionsplace
“even taught in introductory computer science course at Harvard”
▶ Watch at ~1:00approx.
UberMentionscompany · Uber
“prior to figma he was at Uber both as a product leader and also interestingly as head of design”
▶ Watch at ~1:00approx.
Lenny's PodcastCoinedpodcast · Lenny Rachitsky
“welcome to Lenny's podcast I'm Lenny”
▶ Watch at ~1:00approx.
Lenny's NewsletterRecommendsnewsletter · Lenny Rachitsky
“highly recommend you check it out it's currently my fourth most popular newsletter post of all time you can find it at lennysnewsletter.com”
▶ Watch at ~1:30approx.
NotionUsessoftware · Notion Labs
“I use notion to coordinate this very podcast including my content calendar my sponsors and prepping guests for launch of each episode”
▶ Watch at ~2:00approx.
VantaMentionssoftware · Christina Cacioppo
“this episode is brought to you by vanta helping you streamline your security compliance to accelerate growth”
▶ Watch at ~3:00approx.
HotmailMentionssoftware · Microsoft
“I was the product manager on Hotmail”
▶ Watch at ~5:00approx.
MicrosoftMentionscompany · Bill Gates and Paul Allen
“my first job out of college is actually at Microsoft”
▶ Watch at ~5:00approx.
Windows 8Mentionssoftware · Microsoft
“at the time they were working Windows 8 and Windows 8 was really interesting”
▶ Watch at ~5:30approx.
Silicon ValleyMentionsplace · Mike Judge, John Altschuler, and Dave Krinsky
“I really don't the draw of Silicon Valley and I ended up at YouTube”
▶ Watch at ~5:30approx.
YouTubeMentionswebsite · Google
“had the opportunity to lead the YouTube app on iOS over there”
▶ Watch at ~6:00approx.
YouTubeMentionswebsite · Google
“I ended up at YouTube”
▶ Watch at ~6:00approx.
iPhoneUsesproduct · Apple
“I had never touched an iPhone before my first day”
▶ Watch at ~6:30approx.
Apple StoreMentionsplace · Apple
“my manager on my first day just sent me to the Apple store to buy an iPhone”
▶ Watch at ~6:30approx.
UberMentionscompany · Uber
“eventually kind of ended up at Uber”
▶ Watch at ~7:00approx.
AirbnbMentionscompany · Brian Chesky, Joe Gebbia, and Nathan Blecharczyk
“Airbnb was one of them uh Uber was another”
▶ Watch at ~7:00approx.
FigmaUsessoftware · Figma
“I happen to be working on a project that experimentally brought figma into the company”
▶ Watch at ~8:00approx.
GoogleMentionscompany · Google
“in Google culture it's kind of like okay well the answer is well designers they can kind of figure it out”
▶ Watch at ~20:30approx.
SlackUsessoftware · Slack Technologies
“he would drop in tweets that he sees into different slack channels”
▶ Watch at ~25:00approx.
TwitterUseswebsite · Twitter
“the figma team is very good at Twitter and you know staying on top of the sentiments”
▶ Watch at ~27:00approx.
Dolores ParkMentionsplace
“we were doing a 101 walking around Dolores Park”
▶ Watch at ~30:00approx.
The CastroMentionsplace
“so he came out to my house in the Castro”
▶ Watch at ~30:00approx.
SpotifyMentionssoftware · Spotify
“our customers like Square Spotify and Zora are able to grow their businesses on top of flat file”
▶ Watch at ~32:00approx.
ZuoraMentionscompany
“our customers like Square Spotify and Zora are able to grow their businesses on top of flat file”
▶ Watch at ~32:00approx.
FlatfileMentionssoftware · Flatfile
“our customers like Square Spotify and Zora are able to grow their businesses on top of flat file”
▶ Watch at ~32:00approx.
SquareMentionscompany · Block, Inc.
“our customers like Square Spotify and Zora are able to grow their businesses on top of flat file”
▶ Watch at ~32:00approx.
FigmaUsessoftware · Figma
“I use it probably every day for my newsletter for illustrations and Banners and all the stuff”
▶ Watch at ~32:30approx.
FlatfileMentionssoftware · Flatfile
“if you'd like to learn more or get started check out flat file at flatfile.com Lenny”
▶ Watch at ~32:30approx.
FigmaUsessoftware · Figma
“we can build those decks in figma”
▶ Watch at ~35:30approx.
FigJamUsessoftware · Figma, Inc.
“we just did uh calibrations for performance reviews and fig jam”
▶ Watch at ~36:00approx.
Friends of FigmaMentionsother · Figma
“we've really been focused on a program called friends of figma”
▶ Watch at ~55:30approx.
DiscordUsessoftware · Discord Inc.
“come together in like a Discord Channel they meet uh regularly and are helping us evangelize”
▶ Watch at ~55:30approx.
AirbnbMentionscompany · Brian Chesky, Joe Gebbia, and Nathan Blecharczyk
“love drives growth not the other way around they made posters of this put it all over the product teams”
▶ Watch at ~58:30approx.
AdobeMentionscompany
“with the potential acquisition with Adobe which I know isn't done yet”
▶ Watch at ~58:30approx.
Adobe IllustratorUsessoftware · Adobe
“maybe you're kind of doing that intricate like illustration in illustrator”
▶ Watch at ~59:30approx.
Adobe PhotoshopUsessoftware · Adobe
“you know editing raster in Photoshop right and and then you're bringing some of those things into figma”
▶ Watch at ~59:30approx.
Adobe After EffectsUsessoftware · Adobe
“maybe you're creating that micro interaction in After Effects”
▶ Watch at ~59:30approx.
SwitchRecommendsbook · Chip Heath and Dan Heath
“first one that comes to mind is switch and it's really about how to affect organizational change”
▶ Watch at ~1:04:00approx.
The Story of the StoneRecommendsbook · Cao Xueqin
“my favorite book of all time is one called the story of the stone and it's a Chinese novel”
▶ Watch at ~1:04:00approx.
The Good NurseRecommendsfilm
“last movie I watched was called the good nurse and it was about kind of a serial killer uh working in a hospital”
▶ Watch at ~1:05:00approx.
FigJamUsessoftware · Figma, Inc.
“we're starting to use the big Jam for everything from calibrations to interview debriefs to product reviews to everything”
▶ Watch at ~1:05:30approx.
SlackUsessoftware · Slack Technologies
“we ever use those suspects like slack and Asana”
▶ Watch at ~1:06:00approx.
AsanaUsessoftware · Asana, Inc.
“we ever use those suspects like slack and Asana”
▶ Watch at ~1:06:00approx.
DropboxUsescompany · Drew Houston and Arash Ferdowsi
“some of agencies Dropbox to me personally it's Coda”
▶ Watch at ~1:06:00approx.
CodaUsessoftware · Coda
“to me personally it's Coda”
▶ Watch at ~1:06:00approx.
Dropbox PaperUsessoftware · Dropbox, Inc.
“oh I say Dropbox paper very cool yeah I love that product”
▶ Watch at ~1:06:00approx.
Alignment ScaleUsestool
“we have this one called the alignment scale which is a widget that you can insert into figure by Design”
▶ Watch at ~1:06:00approx.
How Figma Builds ProductRecommendsnewsletter · Lenny Rachitsky
“if you just Google how figma builds product it comes up number one”
▶ Watch at ~1:07:00approx.
Apple PodcastsMentionssoftware · Apple Inc.
“you can subscribe to the show on Apple podcast Spotify or your favorite podcast app”
▶ Watch at ~1:08:00approx.
Lenny's PodcastMentionspodcast · Lenny Rachitsky
“you can find all past episodes or learn more about the show at lennyspodcast.com”
▶ Watch at ~1:08:00approx.
SpotifyMentionssoftware · Spotify
“you can subscribe to the show on Apple podcast Spotify or your favorite podcast app”
▶ Watch at ~1:08:00approx.

Spot an error or want something removed? Request a correction or removal.

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Hot Take· 3

Hot Take10:30

Managing Designers Is Harder Than Managing PMs

Asked which is harder, Yuki says managing designers is harder than managing product managers. Designers need to grow their craft, and the company's biggest problem isn't always the place where a designer can develop the specific skill they're trying to learn. PMs, by contrast, are hungry for impact, so you can simply point them at the company's biggest problems.

Designers need to grow craft, and the biggest company problem may not align with what they want to learn.
PMs are hungry for impact, so you can point them at the most important problems.
The PM discipline itself is still hard because it's often unclear day-to-day what the single best thing to do is.

“I would say managing designers is harder than managing product managers”
Yuhki Yamashita · 10:30

#management#design#product-management

Hot Take39:00

Engineers Estimate Half the Time for Their Own Ideas

Yuki argues for protecting bottoms-up energy: a developer noticing something broken and just fixing it is often a more effective quality lever than top-down metrics. He notes that when an engineer estimates work they themselves proposed, it's almost always half the time of the same work assigned top-down, because buy-in changes their willingness and creativity.

Bottoms-up fixing can beat top-down quality-metric programs.
Try not to get in the way of engineers fixing what they notice is broken.
Engineers estimate roughly half the time for work they advocated for versus work assigned to them.
Developer buy-in spikes willingness, creativity, and speed.

“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…”
Yuhki Yamashita · 40:00

#engineering#estimation#motivation#bottoms-up

Hot Take52:30

It's Community-Led Growth, Not Product-Led Growth

Figma is held up as a model of product-led growth, but Yuki reframes it as community-led growth. Certain people inside a company feel so strongly about Figma that they advocate and evangelize for it. The sales team's real job is to empower those internal champions with data and stories so they can make the case, meaning the true salesperson isn't Figma's sales team but the internal designer.

Yuki reframes product-led growth as community-led growth.
Internal champions who love Figma push for it inside their companies.
The sales team's role is to empower and connect those champions, not to sell directly.
The real salesperson is the internal designer, not Figma's sales team.

“we talk about product-like growth but in some ways you know I I like to think about it more as kind of like community-led growth”
Yuhki Yamashita · 52:30

#growth#product-led-growth#community#sales

Explainer· 1

Explainer12:30

Storytelling: Synthesis and Memification

Yuki names storytelling as the single skill most responsible for his success, and says being a great PM is largely about being a great storyteller. He breaks it into two ideas: synthesis (distilling many opinions into one cohesive thesis, a skill he traces to literature classes) and memification (compressing an insight so tightly that leaders repeat it in meetings). A memified insight is how knowledge actually transfers inside a company.

Storytelling shows up in every performance review Yuki writes.
Synthesis: pull disparate opinions and data into one distilled message or thesis.
Memification: compress an insight until executives quote it from memory.
You've done your job when people can draw from your insight in a meeting, the way Travis or Dara did at Uber.
Everyone lives with ~30 seconds of attention, so memorability is what makes a story stick.

“I often talk about mimification which is this idea that like I found this out most at Uber”
Yuhki Yamashita · 15:00

#storytelling#communication#product-management

Story· 4

Story25:00

Figma's Private 'Concerning Tweets' Channel

Dylan Field reads more customer feedback than anyone at Figma and used to drop tweets into Slack channels, but as the company grew, people felt they had to drop everything to react. So they created a private channel called 'concerning tweets' where Dylan drops tweets that aren't going viral, sometimes with zero likes, but that feel like they have an essence of truth worth investigating.

Dylan has read the most customer feedback of anyone at Figma for a decade.
As Figma scaled, a CEO-dropped tweet caused people to drop everything and react.
The private 'concerning tweets' channel contains that reaction for a small group.
The tweets often have near-zero engagement but an 'essence of truth' worth a deeper look.

“we created this new channel private Channel called concerning tweets”
Yuhki Yamashita · 25:30

“these are tweets that aren't going viral by any means they're just things that he sees with like one like sometimes zero likes but he…”
Yuhki Yamashita · 25:30

#customer-feedback#figma#culture

Story33:00

When Figma's Branching and Merging Flopped

Yuki shares a feature that didn't work out as hoped: branching and merging for design systems, a heavily requested workflow that lets teams review changes before they hit components used by thousands of projects. Despite a big investment, initial adoption was low, partly performance, partly an unfamiliar workflow Figma didn't use much itself. The lesson: as Figma builds features for organizations unlike its own, it must get creative about measuring effectiveness beyond internal dogfooding.

Branching and merging was customer-requested and made sense in theory.
Initial adoption was low despite a large investment; reasons included performance and workflow unfamiliarity.
Figma didn't use the workflow much internally, so it missed gaps.
Building for customers unlike yourself requires new ways to gauge effectiveness beyond dogfooding.

“we're starting to build a lot of features that are not necessarily for organizations like ours”
Yuhki Yamashita · 34:00

#figma#product-failure#design-systems

Story35:30

Switching From Memos to Decks to Dogfood Figma

To build high-quality software, Yuki says the biggest lever is getting your whole company using your own product. One of his first moves at Figma was flipping the PM team from a memo culture to a deck culture, because decks get built in Figma. Similarly, the head of design built a performance-review calibration template distributed through HR, giving everyone another reason to use FigJam. The more hours people spend inside the product, the better it naturally becomes.

The single biggest quality lever is using your own product creatively.
Yuki flipped the PM team from memos to decks specifically so decks get built in Figma.
A FigJam performance-review calibration template pushed usage across the company via HR.
More internal usage improves the product because people fix their own day-to-day workflows.

“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…”
Yuhki Yamashita · 35:30

#dogfooding#figma#product-quality#culture

Story40:30

Yuki's Love-Hate Relationship With OKRs

Yuki walks through Figma's ongoing OKR experimentation. Working on core experiences, he found OKRs either produce a secondary metric nobody cares about or an ambitious business metric you can't actually control or prove you moved. He deprecated formal metrics in favor of headline intentions, later reintroduced OKRs with a data team, and now judges any goal by three tests: it must be legible, actionable, and authentic.

Core-experience work makes OKRs feel performative: either a meaningless secondary metric or an uncontrollable top-line one.
Teams treated OKRs as a to-do list and dreadful spreadsheet reviews.
Yuki first switched to headline intentions, then reintroduced OKRs (renamed 'commitments') with a data team.
A good goal must be legible, actionable, and authentic to what you actually do day-to-day.
Figma admits it still hasn't cracked the code and keeps iterating.

“either you incred something that like matters but you can't move or you make it something that you just move it doesn't actually matter”
Yuhki Yamashita · 42:30

“and then the third one is authenticity which is like does this actually honestly depict what you're doing”
Yuhki Yamashita · 47:00

#okrs#goal-setting#metrics#figma

Q&A· 2

Q&A08:30

Why a PM Should Try Switching Into Design

Yuki spent the tail end of his Uber career switching from PM to leading design teams for bikes and scooters. He argues the move isn't for everyone, but it builds deep empathy and forces you to push on a product from a different angle. Going into design means suspending concerns about business, usability, and engineering feasibility to insist purely on the best possible experience.

Switching from PM to design is a strong empathy-building exercise.
A PM sits in the center facilitating trade-offs; a designer must ignore some of those to fight for the best experience.
It's an opportunity for designers and PMs to learn each other's language.
Only worth doing if you genuinely want to, not as a checkbox.

“when you go into design you kind of have to ignore some of those other aspects to really be insistent on posting on the best…”
Yuhki Yamashita · 09:30

#career#design#product-management#empathy

Q&A48:30

Yuki's Favorite Interview Question for PMs

One of Yuki's favorite interview questions is to describe a time you were part of a controversial product decision. It reveals whether a candidate can set up the conflict, represent both sides fairly, and explain why the problem mattered in an even-keeled way. He also asks candidates to describe a big problem they worked on, using it as a thought experiment for whether he walks away feeling compelled to work on that problem too.

Ask candidates to describe a controversial product decision they were part of.
Watch whether they can represent both sides and explain the conflict even-keeled.
Also ask about a big problem they worked on; the test is whether you feel compelled to work on it.
A great PM can make even a boring-sounding problem sound fascinating.

“to me a time when you're part of like controversial product assistant right and you know what did you do and all those things”
Yuhki Yamashita · 49:00

#hiring#interviewing#product-management

Takeaway· 5

Takeaway17:00

Reset Your Brain to Beat the Curse of Knowledge

To get better at storytelling, Yuki 'resets the internal computer' of his brain and rebuilds the story from zero context. He learned this teaching a computer science course, where explaining pointers forced him to lean on real-world metaphors. If you can tell a story any student with no context can understand, telling it to closer audiences becomes easy.

Start from no context and rebuild the story from scratch.
Put yourself in the shoes of a user who has no idea what's happening.
Teaching (e.g. explaining pointers to CS students) forces grounding metaphors.
Master the no-context explanation and every closer audience gets easier.

“I think of it as kind of like resetting the internal computer of my brain a little bit so that like I start from scratch…”
Yuhki Yamashita · 17:00

#storytelling#communication#teaching

Takeaway18:30

PMs Own the Why, Not the What or How

Yuki holds the PM uniquely responsible for the 'why' of a product, while the what and how are shared across the company and customers. He learned this at YouTube, where owning a whole app meant he couldn't spec everything and designers and engineers had to make their own local decisions. If everyone understands why they're doing something, they can make great decisions at scale.

The PM doesn't have to be the person with the idea; the answer to that is usually no.
At Microsoft, specs defined every detail; at YouTube, you had to let designers make local calls.
Shared understanding of 'why' is the only way great local decisions scale.
Push the five-whys further: ask why the customer even has the problem in the first place to find bigger opportunities.

“I do think the why is something that I really always hold the PM uniquely responsible for”
Yuhki Yamashita · 19:30

#product-management#decision-making#why

Takeaway26:30

Treat Loud Tweets as Canaries, Not the Whole Signal

Yuki warns against over-indexing on the vocal minority on Twitter. He treats loud tweets as canaries in the coal mine, one input among many. Support tickets skew dissatisfied, sales conversations reflect perception, and most of Figma's audience isn't on Twitter at all, so a PM needs a balanced portfolio of feedback to avoid blind spots.

Balance the vocal minority against what's actually happening.
Tweets are canaries in the coal mine, one of many inputs.
Support tickets skew dissatisfied; sales talks skew toward perception.
Most of the real audience isn't on Twitter, so build capabilities to extract insight from other sources.

“I really view some of those tweets more as kind of like canaries in the coal mine in a way”
Yuhki Yamashita · 26:30

#customer-feedback#research#product-management

Takeaway37:30

Personal Accountability Comes From Feeling the Problem

Yuki observed at Uber that an engineer's motivation to fix a bug is completely different if they've personally experienced the problem. Engineers who took Ubers to work and saw a driver struggling felt embarrassed and personally accountable to fix it. At Figma, designers feel the same accountability because their customers are people they already know in the community, so they ship work they're proud to defend.

Motivation to fix a bug spikes when the builder has felt the problem firsthand.
Uber engineers who saw drivers struggle felt personally accountable to fix it.
Figma designers know their customers personally via the community, creating accountability.
Increase interaction points between builders and end users to manufacture this effect.

“the degree of motivation is so different if that engineer has somehow experienced a problem in some way”
Yuhki Yamashita · 37:30

#accountability#engineering#motivation

Takeaway56:30

Great Products Equip Customers With a Philosophy

For product-led growth founders, Yuki says you need an almost irrational, emotional love for your product, cultivated internally first and then externally. Beyond solving problems, you equip customers with a philosophy about a different way of working. Figma's controversial idea, that everyone can see your work and multiple designers can be in a file at once, made customers feel part of a revolution they'd champion, not just a tool they'd use.

You need an almost irrational, emotional love for the product, internal before external.
Beyond solving problems, equip customers with a philosophy on a new way of working.
Figma's controversial multiplayer idea made some designers say they'd quit, which was signal.
Customers then champion a new way of working, not just a tool.

“first it has to be cultivated internally too like you know people internally have to authentically love something to really stand behind it”
Yuhki Yamashita · 57:00

#growth#product-led-growth#positioning#figma

Key ideas

Frameworks in this episode

Community-Led Growth: Equip the Champion

Legibility, Actionability, Authenticity

Manufactured Dogfooding

Synthesis-to-Meme Storytelling

The Balanced Feedback Portfolio

The Compelled-to-Work-on-It PM Interview

The PM Owns the Why

People & resources mentioned

People · 13

Resources · 51

Insights & moments

◆Hot Take· 3

Managing Designers Is Harder Than Managing PMs

Engineers Estimate Half the Time for Their Own Ideas

It's Community-Led Growth, Not Product-Led Growth

✶Explainer· 1

Storytelling: Synthesis and Memification

❝Story· 4

Figma's Private 'Concerning Tweets' Channel

When Figma's Branching and Merging Flopped

Switching From Memos to Decks to Dogfood Figma

Yuki's Love-Hate Relationship With OKRs

?Q&A· 2

Why a PM Should Try Switching Into Design

Yuki's Favorite Interview Question for PMs

▲Takeaway· 5

Reset Your Brain to Beat the Curse of Knowledge

PMs Own the Why, Not the What or How

Treat Loud Tweets as Canaries, Not the Whole Signal

Personal Accountability Comes From Feeling the Problem

Great Products Equip Customers With a Philosophy

Hot Take· 3

Explainer· 1

Story· 4

Q&A· 2

Takeaway· 5