Dylan Field 2.0 on Figma

Source: Lenny’s Podcast Speaker: Dylan Field Source URL: https://www.lennyspodcast.com/dylan-field-2/

Key ideas

Design is how you win or lose: “Good enough is not enough. It’s mediocre.” In a world where AI generates more code faster, design is the differentiator. Craft matters more than ever, not less.
Follow the workflow: Figma’s platform expansion strategy is not “find the next biggest TAM” but “trace the user’s workflow”. FigJam, Slides, Dev Mode, Sites, Buzz, Draw — each emerged from noticing a workflow step that didn’t fit cleanly in Figma Design.
Product taste is a learnable loop: exposure → reflection → framework-building. 0.01% of people become true taste-makers (create new genres); most people learn to match an established framework. Both are valuable, but they are different skills.
Time to value: get users to the “special sauce” moment as fast as possible. The “Blockers” team at Figma addressed one blocking issue at a time and could see each improvement in the retention graph.
Role boundaries will blur: 72% of Figma survey respondents cite AI tools as the top reason for expanding their role responsibilities. The future of product building is “we’re all product builders” — designers, engineers, PMs increasingly do each other’s work.

Post-Adobe deal: keeping momentum

After the Adobe deal fell through (16 months; killed by regulators), Dylan ran a programme internally called Detach — a Figma pun for detaching components. Any employee could take 3 months’ severance and reapply in 6 months; the offer was framed as: “Maybe you joined thinking you were joining Adobe. If you need a reset, that’s okay.” Just over 4% took it. Many did significant career pivots, not just company changes.

The broader lesson: communication cadence is the primary tool for maintaining morale under uncertainty. Dylan did quarterly check-ins, then more frequent ones as the path narrowed. At some point he told the team: “The path is narrow.” Most people still expected the deal to close. Transparency prepared those who were paying attention.

Coming out of the deal, Figma launched Dev Mode and accelerated platform expansion — using the disruption as a forcing function for the “what’s next” conversation.

Platform expansion: follow the workflow

Figma’s multi-product strategy is driven by one question: what is the next step in the user’s workflow that currently lives awkwardly inside Figma Design?

FigJam: diagramming and brainstorming pulled out of Design
Figma Slides: presentations pulled out of Design
Dev Mode: design-to-code handoff made into its own surface
Sites: design-to-publish made into its own surface
Buzz: brand-to-marketing asset production
Draw: vector illustration, a bet on a return to expressive internet aesthetics
Figma Make: AI-assisted prototyping from prompt to working prototype

Critically: TAM is the wrong lens. Bureau of Labour Statistics counted 250,000 designers when Figma launched. Dylan’s intuition was that the value was moving up the stack — better consumer software was raising expectations, which would expand design hiring. That intuition turned out to be correct. The lesson: market sizing captures the past, not the future.

“You can’t constrain by always sorting descending by TAM. You have to go from strength to strength and do what is right.”

FigJam and making “fun” a differentiator

One month before the launch of FigJam at Config, the product was done but felt soulless. Dylan convened a board meeting specifically to create clarity on differentiation: the answer was “make FigJam fun.”

The team’s response was scepticism — “That’s our differentiator?” But a design sprint generated ~20 ideas in one day; several made it into FigJam launch (including Cursor Chat). In retrospect: the context demanded it. FigJam is a brainstorm tool used during COVID when people were withdrawing and going quiet. Making it welcoming and playful was the right product instinct for the moment.

The insight: fun is context-dependent. FigJam can lean into play in ways Figma Design cannot — the latter needs to get out of the way of professional workflow.

Product taste: the loop

Dylan’s fullest definition of taste across both appearances:

Have an experience (sensory, aesthetic, functional — any domain).
React: do I like it? Why? Why not?
Build the canon: understand what came before this thing; find the path of decisions that led here.
Disagree or agree philosophically with that path.
Repeat across domains — find cross-domain correlations.

This loop builds taste. Most people who do this consistently learn to match a framework (understand a genre and execute within it). The rare 0.01% learn to create the framework — invent a new genre, find a new aesthetic, expand the possibility space. Both matter in organisations:

Framework-creators set the direction.
Framework-matchers execute within it with high fidelity.

Cross-domain exposure accelerates both. Dylan’s new chief design officer Loredana is a former musician. Many people on the podcast who exhibit strong taste were serious musicians. “There’s something to that.”

The practical expression of taste in product review: the ability to turn it on and off. “I have my own taste, I know what I like. Now I’m going to match your brand.” The most effective product designers can switch between these modes.

Time to value

The principle: get users to the “special sauce” moment as fast as possible. Not the fully-formed experience — the specific thing that is amazing about the product.

For Figma Design: the multiplayer collaboration moment. For FigJam: the same. For Figma Make: the moment the first prompt produces something impressive.

The Blockers team: Figma assigned a small team to go one-by-one through the blocking issues preventing users from adopting Figma Design. Each time they resolved one, they could see the change in the retention and activation graphs. “Literally you could see the change in the graph. It was pretty wild.” Removing blockers is as important for retention as adding new features.

Implication: every product launch needs both (a) something genuinely awesome, and (b) a clear path to that awesome thing. Neither alone is sufficient.

Maintaining startup pace

Key practices Dylan uses to keep a 13-year-old company moving at startup speed:

Problem selection: make sure people are working on things that motivate them. Map interests to projects.
Estimate pressure: understand assumptions from first principles; surface “padding” vs. genuine constraint.
Path dependency awareness: many blockers are assumed constraints that are not actual constraints.
Tech debt management: sometimes slow speed has systematic causes — address the infrastructure, not just the sprint.
Flat org: preserve direct visibility into work.
Willingness to move on: if a project is not converging, move resources.

The future of product building

72% of Figma survey respondents said AI-powered tools are one of the top reasons their role responsibilities are expanding. 56% of non-designers say they engage regularly in at least one design-centric task (up from 44% a year prior).

Dylan’s prediction: roles will not disappear but will blur. The direction is not “fewer roles” but “we’re all product builders.” Designers need to step into product leadership roles. PMs, engineers, and researchers need to engage with design. Judgment, vision, and the ability to rally a team around a goal remain as important as ever.

On AI and headcount: productivity gains exist but are “mild to moderate” for established codebases. Figma is still growing headcount across most functions. The strategic frame: use AI as an opportunity to grow, not a cost-cutting tool.