Dylan Field on product intuition, simplicity, and building Figma

Executive overview

Most design tools grow more complex over time, not less. Dylan Field, CEO of Figma, has made simplicity a first-order constraint — not a polish step — arguing that each addition can reduce overall coherence.

Intuition is a hypothesis generator, not an oracle: test it, debate it, and winnow it with data.

Intuition and product taste

• Intuition surfaces hypotheses; others generate hypotheses too — debate and data determine which survive.
• Constantly ingesting feedback: reads every mention of Figma across Twitter/X, support channels, and anywhere online.
• Asks follow-up questions to reach root problems — what users say they need often differs from what they actually want.
• Encourages the team to do the same rather than filtering all user insight through himself.
• Artifacts and concrete examples shift his mind faster than abstract arguments.
• If a question lacks an answer, the response is: go find the answer, then return to the decision.

Changing your mind as a leader

• Pages in Figma: still skeptical of the implementation, but "the world told us they needed them."
• Trust built with individuals leads to "just go with it" decisions for non-fatal calls.
• Teams usually come back with validation — or acknowledge he was right — but rarely with bad news.
• For high-stakes decisions, working from first principles prevents premature closure.

What the best product managers do

• The best PMs build frameworks that give everyone a shared destination and a shared strategy.
• PMs who treat the role as pure process lose sight of the actual user problems.
• A good PM has a point of view — some will lead to good outcomes, some won't.
• Team cohesion after a milestone matters: if everyone's unhappy, you partially failed.
• All roles — PM, designer, engineer — should overlap in user empathy, business sense, and taste.

Simplicity as a constraint

• Irreducible complexity: one plus one sometimes equals one and a half — adding features can reduce total value.
• All the right local decisions can still produce a system that's too complex overall.
• "Keep the simple things simple; make the complex things possible" is the design principle Dylan holds.
• Simplicity is everyone's responsibility, not just the CEO's.
• Parts of Figma's own product are currently too complex — revisiting those systems is active work.

Early Figma: shipping and finding early users

• Three and a half years to launch; in hindsight, ship faster — every day of delay is a day without feedback.
• Sho joined and immediately presented the gap and a path to shipping; catalysed the team to launch.
• Figma slides shipped fast; Dev mode took much longer because they had to truly understand the developer as a user.
• Framework for new launches: quality, features, deadline — choose two. Software can iterate; physical products can't.
• The goal is a minimally awesome product: meet a minimum quality bar, ship, then iterate.

Finding early users through the design community

• Built a social graph of influential designers on Twitter using PageRank, modelled on work seen at LinkedIn.
• Reached out to designers whose work genuinely inspired him — not purely as a growth tactic.
• Designers are exceptionally good at giving feedback; early deep dives with them shaped the product significantly.
• Early customer Coda (then Krypton): drove back mid-journey when they hit an issue — their Wi-Fi was down.
• Personal hustle in those early moments built relationships that lasted; Shashir (Coda CEO) later learned he was Figma's first team customer.

Spotting trends early

• WebGL in the browser enabled Figma to exist; identifying that early was the foundational technical bet.
• WebSim (websim.ai): a hallucinated internet — type any URL and an LLM invents what that page looks like.
• Figma Ventures invested in WebSim; Dylan sees it as lean-forward entertainment and world-building with AI.
• LLMs each have distinct strengths — worth experimenting to find what each model does uniquely well.

Scaling as a leader

• Mentorship comes from everywhere: investors, coaches, reports, interns, and people you're mentoring.
• People you mentor often return years later with insights that help you — the relationship inverts.
• Constant adaptation is the requirement; no fixed arrival point.
• Advice others give you is advice they're giving themselves in your shoes — factor that in.

Responsibility at scale

• Serving designers means serving the people shaping the world's technology — that's a felt responsibility.
• The obligation: keep simplifying, advance the craft, understand true user needs, champion design quality.
• Carries it as fuel, not weight.