All stories
TechTech / Design Tools

How Figma Won Design by Betting on the Browser

When everyone said browser-based design tools couldn't match native performance, Dylan Field traced that belief back to outdated assumptions — and built the tool that Adobe tried to buy for $20 billion.

Company: Figma|Founded by: Dylan Field

The Challenge

When Figma launched, the design tool market was dominated by Sketch — a native Mac application beloved by designers. The industry consensus was clear: "Design tools need native performance. Browsers are too slow for real-time graphics."

Even within Figma's own team, there were heated debates: could a browser-based tool really compete with native performance? Was the "browser-first" bet a brilliant strategy or a fundamental mistake? The team was split, and the answer would determine the company's entire direction.

The Approach — Tools in Action

Field used structured analytical thinking to resolve both the strategic question and the internal conflict:

Ladder of Inference: Field traced the "browsers are slow" belief back to its source:
  • Observable data: In 2012, browsers WERE too slow for complex graphics
  • Selected data: People anchored on 2012 browser capabilities
  • Interpretation: "Browsers will always be too slow"
  • Assumption challenged: WebGL and WebAssembly were closing the performance gap rapidly. By 2016, the assumption was based on 2012 reality, not current capability.

By walking the team down the Ladder, Field showed that the "browsers can't do this" belief was based on old data.

Decision Matrix: Field evaluated browser vs. native against weighted criteria:
CriteriaWeightBrowserNative
Collaboration ease5★★★★★★★
Cross-platform4★★★★★★★
Distribution4★★★★★★★
Performance (2016)3★★★★★★★★
Performance (2020+)3★★★★★★★★★

Browser won on the criteria that mattered most.

Second-order Thinking clinched the decision:
  • First order: "Native apps are faster today."
  • Second order: "If we build native, what happens in 5 years? Everyone has a fast browser, and we're stuck with a non-collaborative tool. If we build for browser, what happens? We're the only real-time collaborative design tool."
  • Third order: "Collaboration becomes the killer feature that native tools structurally can't match."

The Outcome

Figma's browser bet paid off spectacularly:

  • Became the dominant design tool with 4M+ users
  • Adobe attempted to acquire Figma for $20 billion (later unwound due to regulatory concerns)
  • Real-time collaboration — something native apps structurally couldn't match — became Figma's defining advantage
  • Changed the design industry from "designer works alone, shares file" to "everyone designs together in real-time"

The browser bet wasn't about technology — it was about recognizing that a belief ("browsers are slow") was based on outdated evidence, and that the second-order effects of being browser-native (collaboration, distribution, cross-platform) would be transformative.

💡

Key Takeaway

When experts say "X can't be done," trace the belief back to its evidence. Often the evidence is years old, and the world has changed since the belief was formed.

Tools Used in This Story

Related Combos

Sources