Dylan Field
Co-founder and CEO of Figma; “design is the new code” — visual-first building with direct canvas-to-production pull requests.
Last updated: 2026-04-13
Overview
Dylan Field co-founded Figma and has led it from a design tool to a platform spanning design, prototyping, code generation, and visual AI. He thinks about design at the intersection of craft, judgment, and AI capability — arguing that taste and point of view remain irreducibly human even as execution becomes cheap.
His public thesis for the near future: “We’re entering a world where design is the new code. You’ll be designing in a visual-first way and you’ll be able to do a pull request right to production.”
Key Ideas
Taste, Craft, and Point of View
Three related but distinct concepts:
- Taste: navigating the possibility space with clear, articulable preferences — helping others understand what you’re going for and what you’re not
- Craft: pushing past where others push; thinking across all levels of abstraction simultaneously — macro and micro, and making sure they fit together
- Point of view: expressing something unique, bringing an insight to life that moves a conversation forward. “If everyone agrees with your point of view, you probably don’t have much of a point of view.” POV finds global maxima; pure user feedback finds only local ones.
AI as clay, not answer
The output of a prompt is never a final result. It’s clay you mold. The right workflow is diverge widely using AI, then converge using human judgment. “Use AI as a starting point, push with craft and intention and care towards the final output.”
Field’s personal writing workflow: dump incoherent thoughts → ask for 10 obvious ways to say it → almost never use any of them, but it breaks the blank-page problem and gets the brain spinning.
Direct manipulation > prompting
Hierarchy for adjusting visual properties:
- Canvas direct manipulation (fastest, most expressive for visual work)
- Code editing
- Prompting (slowest, least precise for visual specifics)
The Figma MCP bidirectional loop (design ↔ code) exists specifically to enable this: start in code if that’s fastest to get a prototype, then hop to the canvas for visual iteration where direct manipulation is superior.
Non-linear process
Product development is not a linear pipeline. It’s diamond shapes (diverge/converge) stacking on top of each other in any order. You might start in code, jump to design, go back to a doc, prototype on canvas — whatever gets to learning fastest. The right question is not “which stage are you in?” but “what’s the fastest way to test this?”
Design is the new code
As AI lowers the cost of execution, value moves up the stack. The canvas — a visual representation — is a higher-level abstraction than code. Field’s prediction: eventually you’ll do a pull request straight from Figma to production. This doesn’t eliminate engineering judgment; it elevates where that judgment is applied.
On makers vs. document producers
“If you’re a PM and you think that your job is to make documents and slide decks for upwards review and alignment, you’re going to love this new world that we’re in. You get to make things too. People need to see that leaders in their organization are making things too — and that is what inspires and actually creates the inflection.”
~60% of Figma Make designs are created by non-designers (PMs, researchers, sales, support).
Connections
- design-taste-craft — his taste/craft/POV framework in detail
- prototype-and-prune — parallel framing: both emphasize diverge-then-prune over linear planning; Zhuo from product POV, Field from design POV
- model-context-protocol — Figma MCP as a concrete implementation: code ↔ canvas round trip
Sources
- Figma CEO on the New Design Playbook in the AI Era — video transcript, added 2026-04-13