← Back to list
Colossus (Invest Like the Best / Business Breakdowns)Podcast31 Dec 2020Source: joincolossus.comHost: Patrick O'Shaughnessy

Dylan Field - The Growing Importance of Design – [Founder’s Field Guide, EP.14]

In plain words

Figma's CEO Dylan Field argues design is becoming a core business skill, not just aesthetics. He believes design tools will spread like word processors. Figma runs in a browser and lets multiple people edit together in real time (multiplayer). He's bullish on Figma (valued over $2B, early users stuck with it even when buggy), warns Adobe killed Fireworks and left a gap, and notes Sketch grabbed market share with a focused but buggy approach.

AI SummaryAI-generated · may contain errors · verify against the original

Figma CEO Dylan Field discusses the future of design tools and the growing importance of design in business. Figma's latest valuation exceeds $2 billion, with backing from top venture capital firms such as Andreessen Horowitz, Sequoia, Kleiner Perkins, and Greylock. Key insights include: Figma revol

~13 min full read · 9 sections
Deep Analysis

At a Glance

Dylan Field is the co-founder and CEO of Figma, a browser-based collaborative design tool with a latest valuation exceeding $2 billion, backed by top venture capital firms including Andreessen Horowitz, Sequoia, Kleiner Perkins, and Greylock. The core theme of this episode: Design is evolving from a peripheral role of "making things look good" into a core competitive advantage for enterprises, and Figma is redefining design tools through native browser support and real-time multiplayer collaboration. Dylan Field believes that design tools will become as ubiquitous as word processors—everyone will need visual communication skills in the future, but professional designers will still exist.


Theme 1: The Future of Design Tools — From "Tool" to "Space"

Dylan Field believes that the browser environment forces design tools to evolve from "one-to-one tools" into "digital spaces," which is Figma's most fundamental differentiator.

  • Historical Context: When Figma was founded in 2012, the market generally believed that browsers could not support high-performance design tools. Field recalls that during early recruiting, he "had to open the browser and demonstrate on the spot, otherwise candidates thought I was crazy."
  • Mechanism Breakdown: In a browser, when multiple people edit the same file simultaneously, if the tool does not support real-time collaboration, the file will keep reloading, resulting in a poor experience. Therefore, "the browser naturally requires you to treat the tool as a space, not a one-to-one tool" — this forced Figma to build multiplayer functionality.
  • Data Support: Initially, only "one or two designers said they wanted" Figma's multiplayer feature, but the team "bet on it" based on their understanding of the browser's nature, ultimately finding it to be the right direction.
  • Extrapolation: Field believes that future design tools will resemble "workshops/workspaces" more than a "hammer-nail" relationship. He cites Bret Victor's Dynamicland experiment — a space where source code is visible on walls and physically interactive — as a long-term direction.

Theme 2: The Role of Design in Business Is Undergoing a Fundamental Shift

Dylan Field points out that design has evolved from "beautification" to "defining how software works," and companies that neglect design will lose their competitive edge.

  • Data Chain: At IBM's New York office in 2012, the ratio of engineers to designers was 72:1; by 2017, the company-wide ratio had dropped to 8:1, and on the mobile side to 3:1. Field believes the industry target ratio is 1:6 to 1:8 (designers to engineers).
  • Mechanism Breakdown: Field defines design as "creating a visual language that allows users to understand and solve problems." As cloud and developer tools mature, "it's no longer enough to just build things; they must be exceptionally well-designed."
  • Changes in Consumer Expectations: Consumer-grade applications such as Facebook, Gmail, and Apple have significantly raised user expectations for experience. "Companies with poor design will lose."
  • Extrapolation: Field predicts that the definition of "designer" will broaden—many developers will begin to see themselves as designers. He cites a recent example where a developer told him, "With Figma, I can finally do design myself."

Theme 3: Figma's Design Principles and Product Philosophy

Dylan Field articulated Figma's two core design principles: "Make the simple things easy, but make the complex things possible" and "direct manipulation."

  • Principle 1: Progressive Disclosure — Users can complete basic tasks without learning, while advanced users have pathways to master complex features. Field believes this is key to Figma serving both novices and experts.
  • Principle 2: Direct Manipulation — Using Figma's "arc tool" as an example: users drag control points on the circle to change the angle, rather than entering values in a panel. Field cites Bret Victor's Inventing on Principle talk as inspiration, emphasizing that "there should be an immediate feedback loop between the creator and the creation."
  • Tension Point: Field highlights the core contradiction in design tools — "People want a free-form creative process, but software ultimately requires structured data." Figma's challenge is to "let the computer automatically infer structure after users freely create."
  • Falsification Condition: If Figma cannot support complex workflows while keeping things simple, users may migrate to more specialized tools.

Theme 4: Pricing Strategy and Identifying Product-Market Fit

Dylan Field shared Figma’s pricing lessons—"Not charging actually hurt adoption"—and the key signals for identifying product-market fit (PMF).

  • PMF Identification: Field prefers the term "product-market pull" over "fit." Early key signal: A Coursera user spent hours testing Figma when it was still extremely laggy (taking minutes to write a single line), then sent a 10-page document predicting Figma’s potential.
  • Pricing Turning Point: A large enterprise customer proactively asked Figma to start charging, reasoning that "if you don’t charge, people think you’re unreliable and will go out of business, making it impossible for me to promote it internally." Field thus realized that "not charging actually hindered adoption."
  • Pricing Strategy:
  • Simplicity First: Avoid over-reliance on conjoint analysis or consulting firms. Instead, design a few plans and talk to users face-to-face, observing their body language.
  • Free Viewer Strategy: Figma deliberately made viewers free, hoping they would eventually convert to editors. Field emphasized "linking vision with strategy."
  • Honest Market Positioning: Figma’s pricing structure is "progressive," gradually upgrading from free to professional tiers.

Theme 5: Hiring, Management, and Competition – The Founder’s Growth

Dylan Field candidly shared the painful transition from an "intern CEO" to a manager, along with key lessons on hiring and competition.

  • Management Lessons:
  • Early on, he managed 10 direct reports while his father was dying of cancer, creating immense pressure. "The team gave me a lot of feedback, and I didn't know how to handle it."
  • Key improvements: Learning to "provide context" rather than react directly; learning to "generate buy-in"; learning to "show progress and momentum"—before Figma's launch, the team went long stretches without market feedback, leading to low morale.
  • Hiring Lessons:
  • Citing legendary investor John Doerr's advice: "Wake up in the morning thinking about hiring, think about hiring during every break, and think about hiring as the last thing before bed"—hiring must be the founder's top priority.
  • Timing: Once product-market pull is evident, hiring should accelerate aggressively. Field regretted that "we could have gone much further if the team had grown faster."
  • Replacing oneself: As CEO, one must continuously hand off work to more senior people, or risk losing strategic altitude. He cited the example of Chief Customer Officer Amanda Kleha (from Zendesk): "After she joined, I immediately had a partner who could help build the business for the long term."
  • Competition Reflections:
  • On Adobe: Adobe killed Fireworks (a tool suited for interface design) just as Figma was getting started, "creating a market gap."
  • On Sketch: Sketch, a European team, captured the market quickly with a "buggy but focused" approach. Field admitted that "if Figma had launched earlier, it would have been better."
  • Core lesson: "You can't forget your core, and you can't ignore your community"—Adobe's mistake was neglecting the needs of the interface design community.

Theme 6: The Rise of the Creator Economy and the Future of Privacy

Dylan Field believes we are undergoing a paradigm shift from "consumption to creation," while privacy will become a central battleground for the tech industry.

  • Creator Economy: Field points out that "people are beginning to realize they can use technology to create and express themselves, not just consume." He is optimistic about creator funding models such as Patreon, arguing that "the number of independent creators will increase significantly."
  • Interesting Tools: He cites examples such as Coda, Notion, Roam (document/knowledge management), Wing, Descript, and Reduct (video editing).
  • Privacy Views:
  • Definition: Privacy is "the gap between expectations and reality."
  • Trend: The adoption of Signal during the Black Lives Matter protests shows that "people are becoming aware that their communications are being tracked and are actively choosing more private tools."
  • Action: The tech industry has a responsibility to make "private by default" the norm, including privacy protections for digital currencies.
  • Counterintuitive Judgment: Field argues that the "cat is out of the bag" argument resurfaces every decade, but in reality, privacy has been slowly improving. He cites historical examples such as anti-sodomy laws to illustrate that "private by default" is crucial for protecting minority groups.

Mentioned Positions

Position Guest Attitude Key Data
Figma Bullish (own company) Latest valuation >$2 billion; started in 2012, took 9-12 months to find direction; early users wrote a 10-page document predicting its potential
Adobe Risk warning (competitive perspective) Killed Fireworks (interface design tool), "created a market gap"; but respect for its historical contributions
Sketch Neutral (competitive perspective) European team, quickly captured the market with a "buggy but focused" approach; Field admitted "it would have been better if Figma launched earlier"
IBM Neutral (data citation) Designer-to-engineer ratio dropped from 1:72 in 2012 to 1:8 (company-wide) / 1:3 (mobile) in 2017
Coursera Neutral (early user case) Early users spent hours testing Figma even when it was extremely laggy
Kimberly-Clark Neutral (use case) Used Figma during the pandemic to reduce order forms from 13 fields to 5
Zendesk Neutral (talent source) Figma's Chief Customer Officer Amanda Kleha came from Zendesk
O'Reilly Neutral (personal background) Field's first internship in high school
Patreon Bullish (industry trend) Representative of sustainable revenue models for creators
Coda / Notion / Roam Bullish (industry trend) Innovative tools in the document/knowledge management space
Wing / Descript / Reduct Bullish (industry trend) Innovative tools in the video editing space
Signal Bullish (privacy trend) Adoption surged during the Black Lives Matter protests

Judgments Worth Remembering

1. "Design tools will become as ubiquitous as word processors" (Dylan Field) — In the future, everyone will need visual communication skills, but professional designers will still exist. Supporting evidence: Figma's free viewer strategy and progressive disclosure design.

2. "The browser naturally forces you to treat the tool as a space, not a one-to-one tool" (Dylan Field) — This is the fundamental reason Figma built multiplayer, and also its hardest-to-replicate moat. Supporting evidence: In a browser, files reload during multi-user editing; failing to solve this results in a terrible user experience.

3. "Not charging actually hurt adoption" (Dylan Field) — Large enterprise clients proactively asked Figma to charge fees, because being free made people suspect the company would go bankrupt. Supporting evidence: Clients said, "Please charge something, otherwise I can't promote it within my company."

4. "Recruiting must be the founder's first and last task every day" (quoting John Doerr) — Field regretted not recruiting more aggressively in the early days, believing that "if the team had grown faster, Figma could have gone much further."

5. "Companies with poor design will lose" (Dylan Field) — As consumer expectations have been raised by Facebook, Apple, and others, design has become a core competitive advantage for businesses. Supporting evidence: IBM's designer-to-engineer ratio dropped from 1:72 to 1:8.

6. "The 'cat is out of the bag' argument comes around every decade, but privacy has been slowly improving" (Dylan Field) — A counterintuitive judgment. Supporting evidence: Signal's adoption during the BLM protests proves people will actively choose privacy-focused tools.

7. "Figma's design principle: Keep simple things simple, but make complex things possible" (Dylan Field) — This is the core mechanism for Figma to serve both novices and experts. Supporting evidence: Progressive disclosure design.

8. "Product-market pull is more accurate than product-market fit" (Dylan Field) — The real signal is when users start "pulling" you forward even when your product is still very rough. Supporting evidence: Coursera users spent hours testing Figma when it was laggy and wrote 10-page documents.