Dec 5, 2024 · 1h 9m · in-depth
How Figma taps into taste, simplicity, and storytelling | Yuhki Yamashita (CPO)
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 episode of In Depth, Figma Chief Product Officer Yuhki Yamashita details his frameworks for product management, exploring how Figma scaled into a multi-product ecosystem, balanced simplicity with functional power, and leveraged storytelling and craft to drive industry transformation.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Brett holds 23.3% of the talking time here. How this is scored →
Brett as informed peer 4.2 Guest teaching 4.5 Guest disagreement 0.4 Brett pushing back 0.9
speaking balance: gold is Brett, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 34:00 Challenging software dogmatism with operational reality
Yamashita rejects pure tech and design dogmatism by recounting how a simple ops email at Uber solved a core pickup routing problem far better than an intricate in-app software flow.
Hardest push from Brett ▶ 43:13 Pushing for designers to own revenue targetsBerson directly challenges standard startup design culture by asserting that zero-to-one product designers should be forced to personally close the first million dollars in revenue.
Biggest teaching moment ▶ 46:15 Selling trajectory to overcome Sketch feature parityYamashita provides a masterclass on enterprise go-to-market when facing mature competitors, showing how Figma anchored on trajectory, collaboration, and speed rather than getting crushed in feature checklists.
Brett holds their own ▶ 17:39 Deconstructing multi-product SKU expansion modelsBerson demonstrates deep venture and enterprise software expertise by breaking down multi-product SKU strategy into selling new SKUs to existing buyers versus selling equivalent SKUs across disparate department buyers.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Brett as informed peer | Guest teaching | Guest disagreement | Brett pushing back | Why |
|---|---|---|---|---|---|---|
| The Screenshot Test for Simplicity and Power | 4 | 0 | 0 | 0 | The episode opens with a clip of Yamashita explaining the screenshot test, followed by Berson giving a detailed intro outlining Yamashita's career arc across Microsoft, YouTube, Uber, and Figma before setting up the opening question on why Figma succeeded. | |
| The Foundational Technology Bet and Community Influence | 4 | 5 | 1 | 2 | Yamashita educates the host on Figma's early strategy: betting on WebGL in the browser, graphing Design Twitter influencers, and weaponizing the controversy around multiplayer collaboration. Berson probes on whether WebGL was luck versus deep conviction. | |
| Joining Figma and Blurring Product Design Boundaries | 3 | 3 | 0 | 0 | Yamashita details joining Figma at 90 employees because of personal conviction in dissolving boundaries between product management and design workflows, rather than commercial certainty. | |
| Product Philosophies Across Microsoft, Google, Uber, and Figma | 3 | 6 | 1 | 0 | Yamashita breaks down the distinct operating philosophies across tech giants: Microsoft's rigid DCR spec culture, Google and Uber's reliance on storytelling and decentralized problem understanding, and Figma's live, fluid canvas model. | |
| Balancing Product Iteration, Operational Goals, and Platform Integrity | 4 | 5 | 0 | 1 | Yamashita contrasts Uber's operational leverage with Figma's need for strict primitive discipline, recounting how FigJam originated organically from pandemic remote work and forced Figma to navigate independent team velocity versus shared platform integration. | |
| Aligning User Needs with Commercial Expansion Opportunities | 6 | 4 | 0 | 2 | Berson demonstrates strong enterprise software fluency by comparing expansion models (selling existing SKUs to new buyers like Jira vs new SKUs to existing buyers). Yamashita explains that two-thirds of Figma's active users are non-designers, justifying products like Dev Mode. | |
| Challenging Core Assumptions and Leading 0-to-1 Products | 4 | 6 | 1 | 0 | Yamashita reflects on launching Dev Mode, emphasizing that multi-product success requires leaders willing to challenge legacy assumptions held by the core product team, such as whether an infinite canvas is actually useful for developers. | |
| Zero-to-One versus Scaling Product Management Skill Sets | 4 | 5 | 0 | 1 | Yamashita distinguishes zero-to-one product builders from scale operators, noting that early-stage product leaders require a degree of irrationality and brute-force conviction to make an unproven concept believable. | |
| Design Archetypes, Commercial Sensibilities, and Big Tech Unlearning | 6 | 4 | 2 | 3 | Berson questions why designer founders remain rare and whether Google's AdSense cash cow distorted product culture. Yamashita counters that functional boundaries have converged, though admits he had to unlearn software-only biases when simple ops emails beat app redesigns at Uber. | |
| Incubating New Products: The Journey of Figma Slides | 4 | 5 | 0 | 1 | Yamashita narrates the incubation of Figma Slides, showing how internal grassroots adoption forced leadership to prioritize the product, and details Figma's end-to-end lifecycle map and acqui-hire philosophy. | |
| Commerciality in Design and Bridging the Production Gap | 5 | 4 | 1 | 2 | Berson argues designers should be forced to sell and close initial revenue to build commercial taste. Yamashita reframes the problem as tooling isolation, explaining that designers are structurally distanced from actual production code. | |
| Narrative Trajectory Over Feature Parity in Competitive Markets | 4 | 6 | 1 | 0 | Yamashita shares how early Figma dealt with severe feature gaps against Sketch by selling future trajectory and collaborative product philosophy rather than getting dragged into feature-parity checklists. | |
| Prioritization Frameworks and Designing for Sophisticated Teams | 4 | 5 | 0 | 1 | Yamashita discusses building for sophisticated design teams like Facebook and Airbnb to pull the product forward, while managing the unique friction of builder customers who mock up literal UI solutions to their own complaints. | |
| Visual Storytelling and the One Screenshot Test | 3 | 5 | 0 | 0 | Yamashita elaborates on his 'one screenshot test' as the ultimate benchmark for product clarity and positioning, citing Dev Mode's code diff view and FigJam's playful visual branding. | |
| Preserving Simplicity Amid Growing Complexity | 5 | 5 | 0 | 1 | Yamashita discusses the inevitable complexity trap as products mature, referencing a customer tweet demanding Figma unship features at Config, and argues simplicity is about intuitive mental models rather than feature count. | |
| Defining Product Craft, Conviction, and Taste | 5 | 4 | 0 | 1 | Yamashita defines taste as the willingness to halt corporate consensus and refuse mediocre binary choices. Berson connects this obsessiveness to film directors and Steve Jobs insisting on perfecting the internal casing of computers. | |
| Synthesizing Subtle Insights into Cohesive Product Theses | 3 | 4 | 0 | 0 | Yamashita credits his high school English teacher Georgina MacArthur with teaching him literary synthesis, comparing the deconstruction of textual nuances to identifying subtle user signals and forming coherent product theses. |
Statements from this episode (15)
Dylan Field mapped Design Twitter to seed Figma with top influencers
“And so he actually visualized Design Twitter into this graph And figured out the nodes that were the largest of, okay, who's following who, and then went to them and showed Figma, got their feedback, kept going back to them, not trying to sell them it, but jus…”
Real-time multiplayer design was originally seen as undesirable by designers
“The tension was this idea that everyone could be in the file at the same time. And that was now intuitive, but back then was considered undesirable to some extent. Like, you know, this idea that a hovering art director is always going to be in your file, like …”
Operational changes at early Uber often had bigger impact than the app
“Uber was very much about, you can be a little bit more fast and loose, get stuff out there, learn. And to your point, ops was really important to the point where sometimes operational changes could have a drastically bigger impact on the business, on the user,…”
Two-thirds of Figma's weekly active users are non-designers
“Two thirds of our users are, our weekly active users are non-designers, like developers, like PMs and others.”
Yamashita: The best products come from internal conflict challenging core team intuition
“I think the best products come out of a little bit of, like, internal conflict around people standing up for a use case in a way that, like, is counterintuitive to the core product team. The core product team is so used to one way of thinking and, like, a set …”
Figma is open to standalone product acquisitions to advance its vision
“For now, we've been very, building a very integrated product. And so it's a little bit harder to imagine something like completely orthogonal. And that being said, you know, certainly for the right thing, and if it isn't service advancing our vision for making…”
Zero-to-one product builders should personally close the first $1M in revenue
“I think a lot of the best zero to one product people Should be forced to get the first million dollars in revenue for the thing, not just build the widget and have the sales team bring it to market.”
The biggest design problem is the gap between mockups and production code
“I think the biggest problem is that kind of, like, kind of gap between what's, you know, what's designed in their mock and what's actually built.”
Startups must sell product trajectory over feature parity when fighting incumbents
“When you end up in a conversation where it's just about features, this is not a place you want to be in, right? Because, well, technically, Sketch has more features, you know, or competitors have more features. And so, what we really needed to kind of, like, s…”
Designers initially used Figma reluctantly because Sketch was a better single-player tool
“Around the time when I joined, I like to describe Figma as designers reluctantly using it because they recognize the value of collaboration, but like they themselves, a single player tool, like they felt it was insufficient relative to sketch.”
Design systems drove Figma's enterprise adoption by centralizing software purchasing
“Our design systems features was actually one of the reasons, you know, people chose Figma, because it created economies of scale, and the design functions were maturing, and that kind of buying, the buyer was becoming more kind of centralized in these design o…”
Figma prioritized features by building for Facebook and Airbnb's advanced workflows
“We actually talked to, spent a lot of time with the customers at the most sophisticated design teams. So back then, that was like a Facebook and Airbnb. They represented the future of design teams, like where design teams might be in two or three years. So how…”
Five percent of Figma files were presentation decks before Slides launched
“For slides, for example, you know, something like five percent of Figma files are decks. Before slides existed, right?”
AI may allow software tools to avoid bloated interfaces by bypassing navigation
“AI bypasses a lot of, like, navigation and complexity. And so we might see kind of like a different set of incentives emerging or kind of tools evolving separately or, you know, tools not feeling the pressure to kind of keep adding to their interfaces and rath…”
Corporate incentives inherently favor velocity and decision-making over product craft
“The first thing is, like, in a corporate environment, you can kind of logic your way into a lot of choices, and it can sometimes be hard to fight that because so much of the incentive is making progress, making decisions, and so someone who's willing to slow s…”