Yuhki Yamashita
Chief Product Officer, Figma · 1 appearance on the record.
computed by AI from the episodes · how this works → · full disclaimer →
executiveoperator@yuhkiyam ↗LinkedIn ↗figma.com/@yuhki ↗
Yuhki Yamashita is the Chief Product Officer at Figma, where he oversees product management and design strategy. He previously held product leadership positions at Uber, Google, and Microsoft.
33statements → 10claims → 6claims resolved → 100%fully supported → 4.09/5average certainty → 1.97/5average debate potential → ≈4.5/5argument clarity, estimated →
6 supported 0 partly supported 0 contradicted 1 not yet assessed 3 not checkable as stated how the 10 claims stand · each chip opens the sources
2 predictions · 8 assertions · 3 opinions · 18 insights · 2 disclosures · every statement was checked. The predictions and assertions are the 10 claims: statements the public record can support or contradict. 6 are resolved, 1 is not yet assessed, and 3 name no date, number or outcome precise enough to check. Everything else (opinions, insights, what ifs, disclosures) can never be settled by the record, so it carries no assessment.
The record, in short
What the tape says about how Yuhki argues and how the claims held up. Everything they said, and everything said about them, is in the tabs below.
Expressed certainty vs assessment result
weighted support: a fully supported claim counts one, a partly supported claim counts half. Each filled bar is clickable and opens exactly those claims; "none yet" means nothing said at that certainty level has resolved yet
How they sound: not measured why? →
We measure speaking style by listening to the audio itself, and a fair number needs at least 2,000 words from one person on tape we have measured. We have 8,125 words of Yuhki Yamashita, and that is not enough to publish a rate. This says nothing about how they speak.
How the interview went all their pushback → series average →
Across 1 rated episode:
host pushback ▾ 4/10
pushed back at the host 2/10
setup questions received 25%
host pushback: the hardest questions Harry asked, tap to play ▶ 28:24“What was the biggest flop, the one that released, and it just did not work, and it was super clear, and what did you learn about that?” ▶ 41:49“Do you think it was the right decision to have that many products that quickly?” ▶ 56:20“What is bad about the Figma product culture that remains and you would like to change?”
Everything Yuhki Yamashita said on 20VC that made the record, most notable first. Filter by type, assessment or year in the ledger →
Yamashita: Early-stage startups should not hire product managers
“Smaller companies shouldn't have PMs because the founder is playing that role.”
Yamashita: Figma engineering headcount won't scale proportionally with product expansion
“I don't think we'll have fewer engineers than we have today, but you know, I think we'll be able to do more than we're able to today. You know, as we expand more products, I don't, expect the number of engineers, for example, to grow in proportion.”
Yamashita: Non-designers prefer linear workflows over Figma's 2D infinite canvas
“But as we started building other products, we realized, and other audiences, they're like, oh no, people are confused by a two D canvas. They would prefer to be in more of a workflow where they can see one thing at a time. And so as we contemplated other Types…”
Yamashita: Over-Prioritizing Simplicity Stifles Necessary Feature Growth
“So there is truth to that, but simplicity is a perception. So it's not necessarily a reality. You know, if you take simple is always better to an extreme, you might not add new features. You might not add new capabilities. And I don't think that's always the r…”
Yamashita: Observing User Hacks Reveals Real Signal for Product Roadmaps
“It's important to observe how people hack your product, you know, use that as inspiration, because that's real signal, right? They're going out of their way to demonstrate to you that they have a need, even though you're not delivering on it.”
Yamashita: Products requiring tutorials to explain value signal design failure
“All too often people end up kind of having to walk people through, okay, this tutorial of like, let me just explain to you why this product is better. And to me, that's not just a story. It's also kind of a constraint in the design. Like you're maybe not pushi…”
Yamashita: Future product building tools must support multiple entry points
“The future has to be one where there are many entry points because building a product is just necessarily this very Complex, multifaceted thing.”
Yamashita: Code is the primary source of truth in Figma Make
“In Figma make, source of truth is code, and we figure out how to take your design, translate it into code, and then let you iterate via code, because code is so expressive.”
Yamashita: Figma's early Make Design feature merely matched prompts to templates
“We had worked on some AI features the year before, which at the time we had called make design, where you can go from a prompt and it would generate some designs on the canvas. And it was a pretty simple feature. You write some prompts and then it would use so…”
Yamashita: Great PMs must frame routine tasks as existential missions
“A PM is really great at motivating something incredibly boring as existential, and so whenever I'm interviewing PMs, you know, I just ask, okay, well, what are some projects you've led, and whatever, and if they can't make it sound interesting to me, no matter…”
Yamashita: Gap between design and production code is primarily a bug
“I would say it's primarily bugged today. Perhaps at times masquerading as a feature because I think designers are always designing ahead, right? So they're always thinking about v one, v two, v next. And so as a result of that, it is natural for the designs to…”
Yamashita: Design and human craft will differentiate software in the AI era
“There's a sea of software, you know, everyone can make some product, and it's really about, well, what is going to help differentiate One product from the next, and we deeply believe it's great design, great craft, and that's not something that, like, you can …”
Yamashita: Users created 3.5M presentation decks in Figma before Slides launched
“Before our Slides product, three and a half million decks were being made in Figma design, even though it wasn't intended for it.”
Yamashita: Tangible prototypes convince stakeholders far better than theoretical pitches
“Building something tangible that people can use convinces people more that this idea is tenable.”
Yamashita: Prototyping with new capabilities must be a core product team skill
“Well, I think it's really important right now for every product team to think about how to prototype and play with new capabilities because it's, everything is so fast moving, so programs like Maker Week help, but I think it's a core capability that we all nee…”
Yamashita: Prompting and coding are as valid as canvas manipulation for design
“Design you might think of as that thing of visual manipulation on a canvas drawing some mock, but actually just as valid is A bunch of iterations via prompting or just as valid is writing some code because maybe designing via coding is faster.”
Yamashita: Designers rarely push pixels today, instead compositing design system elements
“Designers, they're very rarely pushing pixels anymore. They're compositing things that Already exist in their design systems and putting it together.”
Yamashita: Product excellence requires tension between business, user, and tech advocates
“And that tension is what I think advances a product, right? And so I think people have to push on these things, like advocate for the business, advocate for the user, advocate for technical feasibility, and they might not be expressed through these traditional…”
Yamashita: AI tools lower entry barriers while boosting top-tier productivity
“I always like to go back to our own framework of how AI helps with design, which is that it does both lower the floor and raise the ceiling, right, which is that it makes, in our case, design, but in this case, coding more accessible and approachable to everyo…”
Yamashita: Figma's perfectionist culture requires pushing teams to ship
“For example, at Figma, we have a culture of everyone wants to get the details right, so sometimes we have to encourage people to be comfortable getting something shipped.”
Yamashita: Polish core user paths first, skip perfecting speculative features
“If you're perfecting details for a critical part that it's going to help you understand how well this product is going to do in the market, then by all means. But if you're starting to kind of perfect these areas that are much more speculative or areas of the …”
Yamashita: Figma tracks user reliance via ND7s, targeting 5 days weekly
“Our first product, Figma Design, has always set the bar for what it means to be a kind of tool that people are deeply, deeply reliant on. That's kind of the golden standard... We call it ND sevens, like how many days in a week? That people are using your produ…”
Yamashita: Dylan Field mapped design Twitter graphs to recruit early users
“One of the first things he did was he took design Twitter, he visualized it as a graph, and then figured out which people designers are following the most, and then went to those designers to get feedback on Figma and get them excited about Figma. And that was…”
Yamashita: Software Tools Differ From Consumer Apps Due to Unpredictable Behavior
“Some of these are pretty sophisticated products, and the kind of interesting thing about building a tool is a tool is very different from, like, a typical consumer product where, you know, there's a funnel and you're trying to optimize the metric. Like, you're…”
Appearances (1)
| Episode | Date | Speaking time |
|---|---|---|
| 20Product: Figma CPO on How Figma Builds Products: What Works, What Does Not | How Figma D | May 16, 2025 | 39m |