LLenny's Podcast
← All episodes
30 June 2024

Dylan Field live at Config: Intuition, simplicity, and the future of design

6Frameworks
15Insights

Episode overview

Recorded live at Figma Config, Lenny Rachitsky interviews Figma CEO and co-founder Dylan Field about product intuition, organizational decision-making, and the future of product management. Field describes intuition as a hypothesis generator that must be tested through debate and evidence, while arguing that strong product managers create shared frameworks grounded in strategy and a point of view. He also explains why simplicity requires continual system-level attention, reflects on Figma's slow initial launch and early customer research, and discusses Websim as an emerging form of generative, world-building entertainment.

Key ideas

  • Intuition generates hypotheses; teams should debate them and seek evidence before adopting a working hypothesis.
  • Strong product managers unite teams around frameworks that combine strategy, a point of view, a destination, and a path to reach it.
  • Design disciplines overlap: product managers, designers, engineers, and researchers all benefit from user exposure, technical awareness, business context, and craft.
  • Adding locally sensible features can still create an incoherent system, so product teams must repeatedly revisit complexity at the system level.
  • New launches balance quality, features, and deadlines; software's iterability allows different tradeoffs as long as a minimum quality bar is understood.
  • Shipping earlier accelerates feedback, but the appropriate threshold is a minimally awesome product rather than a universal feature or quality formula.
  • Figma's early adoption grew through identifying respected designers, learning from them, showing them the product, and incorporating their detailed feedback.
  • Websim demonstrates a different form of generative UI: a persistent, model-created internet that can function as interactive world-building entertainment.

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

Frameworks in this episode

Innovation5 steps

Intuition as Hypothesis Generator

Treat product taste as a hypothesis machine, not an oracle — then debate it down to a working hypothesis

Read →
Innovation5 steps

Irreducible Complexity — The Simplicity Audit

1 + 1 = 1.5, not 3 — every addition subtracts, so audit the system, not the local decisions

Read →
Strategy5 steps

Quality, Features, Deadline — Choose Two

Every launch drops one of three; software lets you drop quality only if you plan to earn it back

Read →
Marketing5 steps

The Influence-Graph Fanboy Loop

Run PageRank on your community's network, then approach the central nodes for feedback — not distribution

Read →
Leadership5 steps

The Non-Fatal Override

If it isn't fatal, let them run it — but log your skepticism first so the outcome teaches both of you

Read →
Leadership6 steps

The PM Framework Wrapper

A PM's real output is a framework that wraps strategy plus a point of view — and gets everyone to the same destination

Read →

People & resources mentioned

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

People · 9

  • Dylan FieldMentionsthat's something Dylan's really good out is trusting his intuition and gut

    “with figma CEO and co-founder Dylan field”

    ▶ Watch at ~0:06approx.
  • 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

    “Lenny let's keep talking about design”

    ▶ Watch at ~6:49approx.
  • Rick RubinMentionsJack Clark is our you know head of policy and he got connected to Rick Rubin

    “I'm going to play a short clip with Rick Ruben”

    ▶ Watch at ~9:48approx.
  • Brian CheskyMentionsBrian chesky at Airbnb there was a whole article where we unpacked this moment in their product development cycle

    “last year you had Brian chesky here”

    ▶ Watch at ~16:12approx.
  • Evan WallaceMentionswe talked to Evan our CTO and knew it would take about another year for him to build it

    “Evan my co-founder introduced me to early on in fig history”

    ▶ Watch at ~22:49approx.
  • Dharmesh ShahMentionsone of the attendees there is darmesh founder of hubspot and very thoughtful person

    “I had dares Shaw on the podcast he's the co-founder of Hub spots”

    ▶ Watch at ~25:12approx.
  • Sho KuwamotoMentionsthe customer Obsession that we have the the care of especially that editor tool

    “show has joined us as a director of engineering he's a vpa product now”

    ▶ Watch at ~27:06approx.
  • Max VoltarMentionsMax volar I'm like oh my God this guy is just genius these icons are incredible

    “Max volar I'm like oh my God this guy is just genius these icons are incredible”

    ▶ Watch at ~32:32approx.
  • Shishir MehrotraMentionsshashir marocha is the co-founder and ceo of koda before starting koda shashir led the youtube product engineering and design teams

    “shashir Is Amazing by the way and like has been a mentor for a long time to me”

    ▶ Watch at ~35:10approx.

Resources · 24

  • ConfigMentionsevent · Figma

    “recorded live at figma config”

    ▶ Watch at ~0:03approx.
  • FigmaCoinedsoftware · Figma

    “with figma CEO and co-founder Dylan field”

    ▶ Watch at ~0:06approx.
  • Moscone CenterMentionsplace

    “in front of a live audience at the muscone center in San Francisco”

    ▶ Watch at ~0:10approx.
  • WebsimRecommendssoftware

    “he shares his favorite AI tool called Web Sim which is wild”

    ▶ Watch at ~0:44approx.
  • WorkOSRecommendscompany · WorkOS, Inc.

    “you should consider work OS it's a dropin replacement for azero”

    ▶ Watch at ~5:02approx.
  • AnvilRecommendssoftware · Anvil

    “build document software fast with Anvil”

    ▶ Watch at ~6:36approx.
  • SlackUsessoftware · Slack Technologies

    “there's a slack Channel repaste them”

    ▶ Watch at ~11:46approx.
  • AirbnbMentionscompany · Brian Chesky, Joe Gebbia, and Nathan Blecharczyk

    “they got rid of product management at Airbnb”

    ▶ Watch at ~16:20approx.
  • FigmaUsessoftware · Figma

    “we can make it more powerful but to do that in a way that's not making it more complex”

    ▶ Watch at ~23:18approx.
  • UserTestingRecommendssoftware · UserTesting

    “learn more today at usertesting.com”

    ▶ Watch at ~24:49approx.
  • HubSpotCoinedcompany · HubSpot

    “he's the co-founder of Hub spots”

    ▶ Watch at ~25:16approx.
  • FigJamCoinedsoftware · Figma, Inc.

    “fig Jim is a great example that we shipped it incredibly fast”

    ▶ Watch at ~28:00approx.
  • Figma SlidesCoinedsoftware · Figma

    “figma slides great example that too”

    ▶ Watch at ~28:11approx.
  • Dev ModeCoinedsoftware · Figma

    “Dev mode for what it's worth it took us longer”

    ▶ Watch at ~28:15approx.
  • PageRankUsessoftware · Google

    “the central nodes were which you can just run page rank on”

    ▶ Watch at ~31:23approx.
  • DropboxMentionscompany · Drew Houston and Arash Ferdowsi

    “the first time I met Tim was a Dropbox”

    ▶ Watch at ~32:46approx.
  • CodaMentionssoftware · Coda

    “one of your first customers was Koda sponsor I think of config”

    ▶ Watch at ~34:26approx.
  • KryptonMentionscompany

    “used to be called Krypton”

    ▶ Watch at ~34:31approx.
  • WebGLUsessoftware · Khronos Group

    “obviously webgl you were on early and that's what allowed figment to exist building it in the browser”

    ▶ Watch at ~35:51approx.
  • CryptoPunksUsesproduct · Larva Labs

    “I saw you Tweeting about Crypt punks way before they were worth millions of dollars”

    ▶ Watch at ~36:02approx.
  • Figma VenturesUsescompany · Figma

    “we actually invest in web Sim with a figma ventures”

    ▶ Watch at ~36:34approx.
  • OpenRouterUsessoftware

    “you can use open router to get like a bigger context window”

    ▶ Watch at ~36:55approx.
  • WebsimUsessoftware

    “I just have like gone deep and geeked out on this”

    ▶ Watch at ~37:08approx.
  • Lenny's PodcastCoinedpodcast · Lenny Rachitsky

    “you can find all past episodes or learn more about the show at Lenny podcast.com”

    ▶ Watch at ~47:56approx.

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· 2

Hot Take13:00

Dylan Field is still skeptical of Figma pages

Asked what he has changed his mind about, Field admits he was overruled on Pages. He remains skeptical that Pages is the most elegant solution and doubts his team would build them the same way if they started over. He shipped them anyway because users and the team insisted they needed them.

  • Field changed his mind and shipped Pages despite personal doubts
  • He still thinks Pages isn't the most elegant fit for the overall product design system
  • Users and the team told him it mattered and they needed it
  • Figma is not unshipping Pages

“I'm not sure we'd come to the same implementation of pages that we are at today uh I just don't think it's like the most…”

Dylan Field · 13:30
#product#figma#changing-your-mind
Hot Take44:30

Hot take: different LLMs are each uniquely good if you get them in the right mood

Diplomatically dodging a favorite-product question, Field says it's fascinating how each LLM is uniquely good at different things. He hints that you can hack them the right way and get them in the right mood to unlock what they'll do, leaving the details deliberately vague as his diplomatic answer.

  • Each LLM is uniquely good at different things
  • You can hack them the right way to get more out of them
  • Getting a model 'in the right mood' changes what it will do
  • Field kept the specifics deliberately diplomatic

“it's so fascinating to look at all the different LMS out there right now and what each one is uniquely good at and it's really”

Dylan Field · 44:30

“fun if you can hack them the right way and get them in the right mood what they'll do that's what I'll say”

Dylan Field · 45:00
#ai#llms#hot-take

Explainer· 4

Explainer07:00

Why Dylan Field defines design as art applied to problem solving

Field unpacks his favorite definition of design as art applied to problem solving. Pure art ignores the user need, but stripping the art away leaves something utilitarian and soulless. The beauty is in combining creative expression with a real problem that needs solving.

  • Design must match a user need or problem, not just express creativity
  • Solve the problem with no art and the result is utilitarian and lacks soul
  • The combination of art and problem solving is what he finds beautiful
  • He notes there are many competing definitions (design is dialogue, design is problem solving)

“it's not pure art and if you but if you lose the art and you're just solving the problem like it's totally utilitarian and it…”

Dylan Field · 07:30
#design#craft#product
Explainer11:00

Intuition is a hypothesis generator

Asked how he built his product taste, Field reframes intuition as a hypothesis generator rather than a gut oracle. Hypotheses from him and others get put forward, debated, and tested against data before narrowing to a working hypothesis. He feeds this engine by constantly ingesting information about Figma from everywhere online.

  • Intuition generates hypotheses; it doesn't hand you the answer
  • Hypotheses are debated and tested with data that supports or negates them
  • The team narrows to a working hypothesis and moves forward from it
  • He constantly ingests Figma feedback across Twitter, support channels, and the wider internet
  • He digs for the root problem, since people often ask for X but really want Y or Z

“I think intuition is like a hypothesis generator and uh you're constantly generating these hypotheses and others are generating hypothesis as well and you then…”

Dylan Field · 11:00

“I definitely look everywhere I'm trying to constantly ingest information about figma”

Dylan Field · 11:30
#intuition#product-taste#decision-making
Explainer18:00

What the best product managers actually do

Field argues the lines between PM, designer, and engineer are inherently blurry, and each role should carry some of the others' skills. The best PMs create frameworks that carry a point of view and strategy, aligning everyone on the destination. Weak PMs fail when they treat the job as process and lose sight of the problem and the users.

  • Role boundaries between PM, designer, and engineer are always blurry
  • PMs need technical sense; engineers and designers need business and taste
  • Best PMs build frameworks that carry a point of view and strategy
  • Those frameworks make the destination and path clear to everyone
  • PMs fail when they lean too hard on process and ignore users and the problem

“when you see people that fall down in that function is because they treat it too much like process”

Dylan Field · 19:30

“the best PMS I think uh again create those Frameworks that bring everyone else along and those Frameworks also have a point of view and…”

Dylan Field · 21:30
#product-management#teams#strategy
Explainer22:30

Irreducible complexity: why one plus one can equal one and a half

Field cites the idea of irreducible complexity his co-founder Evan introduced him to: adding to a product doesn't always add value, and can subtract it. The danger is that every local decision is right yet the combined system becomes too complex to work. His job is to keep revisiting those systems before they become a monstrosity.

  • Irreducible complexity: 1 plus 1 sometimes equals one and a half, not three
  • The more you add, the more complex and worse a tool can get
  • You can make Figma more powerful, but keeping it simple at the same time is extremely hard
  • All the right local decisions can still add up to a system that's too complex and stops working
  • The fix is to go back and revisit the whole system

“contains the term irreducible complexity and it's based this idea that like 1 plus 1 does not equal three it sometimes equals like one and…”

Dylan Field · 23:00

“we made like all the right local decisions and yet together they're too complex and they're not working anymore”

Dylan Field · 24:00
#simplicity#product#complexity

Story· 2

Story30:30

How Figma got early users: PageRank the design community

Field describes scraping Twitter around 2012-2013 to build a graph of the most central designers using PageRank, inspired by network visualization work he saw at LinkedIn. He reached out to the ones whose work inspired him, offered to buy them coffee, and used the meetings to learn and get feedback rather than to sell. It worked especially well because designers are unusually good at giving feedback.

  • He ran PageRank on scraped Twitter data to find the most central designers
  • The tactic only worked then; the Twitter API no longer exists
  • He reached out to designers he admired and offered to buy them coffee
  • The motive was fanboy learning and feedback, not a growth hack to convert them
  • It works with designers because they're exceptionally good at giving feedback

“I kind of constructed this list of like here are the most Central designers in the graph but also then I like looked at their…”

Dylan Field · 31:30

“it especially works for designers that way because designers are really good at giving feedback like it turns out that not everyone is good at…”

Dylan Field · 33:30
#growth#early-users#figma-history
Story34:00

Turning the car around for Figma's first customer

Field recounts helping set up an early customer (Coda, then called Krypton, led by Shishir Mehrotra), driving home, then learning they had an issue and turning the car around to help. He later realized only afterward that Shishir's team was Figma's first real team user, and introduced him at the office before making the connection.

  • He set up an early customer, drove off, then turned the car around when they hit an issue
  • The customer was Coda, formerly Krypton, a config sponsor
  • Shishir has been a long-time mentor to Field and his team
  • Field only later realized that team was Figma's first team user

“somehow found out that that they were had an issue and we turned the car around”

Dylan Field · 35:00
#early-customers#figma-history#founder-stories

Tool· 1

Tool36:00

WebSim, the hallucinated internet Dylan is geeking out on

Field's favorite recent tool is WebSim, which he calls a hallucinated internet: type any URL or prompt and it invents what that website would look like using models like Claude or GPT-4o. The more you use it, the more you build up a context window that becomes an almost world-building universe. Figma Ventures invested, and Field shares fun examples like an invented Gmail and a frog-themed FigJam parody.

  • WebSim invents websites from a typed URL or prompt using models like Claude or GPT-4o
  • OpenRouter can give it a bigger context window
  • Continued use builds a context window like a world you're constructing
  • Figma Ventures invested in WebSim
  • Example: he generated a whole 'frog jam' marketing site with toad puns and lily-pad sticky notes

“web Sim is like a um hallucinated internet basically if you go to web sim.”

Dylan Field · 36:30
#ai#tools#generative-ui

Takeaway· 6

Takeaway14:00

Let people run with ideas that aren't fatal

Field describes how he handles disagreement: if a decision isn't fatal, he lets the person go ahead while sharing his skepticism. He changes his own mind fastest when someone brings something concrete he can debate, asks for examples, and pushes for first-principles understanding rather than process.

  • If a call isn't fatal, he tells people to go with it and shares his feedback anyway
  • Sometimes they come back proven right; he builds deep trust either way
  • Concrete artifacts and things he can debate move him fastest
  • He asks for examples and follow-up questions and sends people to find missing answers
  • He values understanding decisions from first principles without bottlenecking the org

“if things are not going to be fatal then if I hear from someone hey I really think we should do X then I'll say…”

Dylan Field · 14:00

“I think the more concrete and artifact is or the more you can debate something the better uh I like ask for examples a lot”

Dylan Field · 14:30
#leadership#decision-making#trust
Takeaway25:00

Keep the simple things simple, make the complex things possible

Field says simplicity is everyone's responsibility, not just a top-down mandate, framing the work as constantly fighting entropy in the product. His guiding principle for tools is to keep simple things simple while making complex things possible, and he warns how easily the simple things get made complex.

  • Everyone is responsible for simplicity, not only leadership
  • Guiding principle: keep the simple things simple, make the complex things possible
  • It's dangerously easy to make simple things complex
  • Fighting product complexity is like fighting the second law of thermodynamics

“keep the simple things simple make the complex things possible”

Dylan Field · 25:30

“it's really easy to make the simple things complex unfortunately”

Dylan Field · 26:00
#simplicity#design-principles#tools
Takeaway27:30

Ship fast because faster out means faster feedback

Reflecting on Figma taking three and a half years to launch, Field endorses shipping quickly to get feedback sooner. FigJam and Figma Slides shipped fast and reached the market faster; Dev Mode took roughly three times as long because they had to keep iterating to truly understand the developer user. Speed is the default, but some new things need real iteration first.

  • The faster you ship, the more feedback you get, which is a positive thing
  • FigJam and Figma Slides are examples of shipping incredibly fast
  • Dev Mode looked simple but took at least three times as long to get right
  • Some directions failed and required deep iteration to understand the developer user
  • Figma took ~3.5 years to launch and ~5 years to a first paid customer

“the faster you get it out the more feedback you get that is a positive thing”

Dylan Field · 27:30
#shipping#startups#iteration
Takeaway29:30

Quality, features, deadline: pick two

Field shares a rule his co-founder Evan taught him: for any new launch you get quality, features, and deadline, and you can only choose two. Because software keeps iterating, you can sometimes ship on features and deadline and improve quality later, but new things still need a minimum quality bar. He calls the goal a minimally awesome product.

  • For any new launch you get quality, features, deadline, and can pick only two
  • Software's advantage is you can keep iterating after shipping
  • Sometimes you trade fewer features to hold a real quality bar
  • Know upfront what a new thing will take before you ship it
  • Aim for a minimally awesome product, and keep improving quality, not just features

“for any new launch you got quality features deadline choose too and uh I think that the beautiful thing about software is you can keep…”

Dylan Field · 29:30
#shipping#prioritization#quality
Takeaway39:30

Mentors can come from anywhere, even the interns

Asked what most helped him scale, Field says all of it, and stresses a learner's mindset. Mentorship can come from community, the people you hire, investors, coaches, and even people you mentor. New founders and Figma interns have taught him things and served as mentors in their own right.

  • Scaling required constantly adapting, growing, and changing
  • Mentors can come from community, hires, investors, and coaches
  • People you mentor can become mentors back to you over time
  • New founders and Figma interns have taught him things he'd never considered
  • You have to stay ready to absorb new information

“mentors can come from anywhere it can come from the community”

Dylan Field · 40:00

“interns at figma have been mentors to me in many ways”

Dylan Field · 41:00
#leadership#mentorship#learning
Takeaway45:00

When people give you advice, they're giving themselves advice in your shoes

Field's favorite piece of advice is that advice isn't really for you: people are giving themselves advice as if they were in your shoes. He offers it as a useful lens for weighing any guidance you receive.

  • Advice is people telling themselves what they'd do in your position
  • It's a useful filter for how much weight to give any advice
  • He applies it even to his own advice in that moment

“when people give you advice they're not giving you advice they're giving themselves advice in your shoes”

Dylan Field · 45:00
#advice#mindset#decision-making