Figma (Matching Real Design Workflows) #

Key Result: Figma’s monthly active users grew from 4 million in 2022 to 13 million by Q1 2025, with net revenue retention of 132% (SEC S-1 filing). BS-0065

Background #

For most of the 2010s, professional design tools assumed design was a solitary desktop activity. Files lived on individual machines; collaboration meant exporting, emailing, versioning by filename, and walking stakeholders through static screenshots. But watch how design work actually happens and a different picture emerges: reviews, handoffs, stakeholder feedback, and iterative co-creation. Design is a team behavior performed with individual tools.

Figma bet on closing that gap, with its browser-based editor reaching the market in 2016. Instead of treating collaboration as an add-on to a single-player editor, it selected “review and iterate together in one shared artifact” as the product’s unit of behavior and built everything else around it. The result was that the tool matched the behavior teams were already performing awkwardly across email threads, meetings, and version-numbered files.

What actually drove adoption #

The behavioral mechanism was making the team behavior the default rather than an optional mode. But that choice was only viable because of a hard technical achievement underneath it. Browser-based multiplayer rendering of professional-grade design files was genuinely difficult; Figma’s own engineering account of its multiplayer technology documents how much invention it took. Competitors saw the same collaboration opportunity and could not execute it: InVision and the Sketch-plus-Abstract stack both attempted collaborative workflows and failed to displace the single-player model. Behavior selection told Figma what to build; the technical moat determined who could actually build it.

With that foundation, the design choices compound:

• Browser-native files behind a shareable link collapsed access friction to a click. No installs, no licenses to provision, no file transfers - the artifact lives where every stakeholder already is.
• Multiplayer co-editing let designers, PMs, and engineers work in the same file simultaneously, replacing the export-review-reconcile cycle with direct manipulation.
• Commenting in context brought stakeholder feedback into the artifact itself, fitting the real contexts where reviews happen: meetings and asynchronous threads.

Removing access friction for non-experts proved more powerful than adding power features for experts. Once cross-functional stakeholders could participate by clicking a link, teams standardized their workflows around the shared file - and collaboration became the moat. BS-0065

Behavior Fit Assessment #

These ratings are analyst examples of a Behavior Fit Assessment, not direct measurements. For the target behavior - review and iterate together in one shared artifact - Dispositional Fit is high because design teams consistently value feedback, coordination, and shared iteration; the tool asked for behavior the population already chose in reviews. Professional identity can reinforce those priorities, but it is not the definition of the score. Capability Fit is high because the stakeholder-side actions (click a link, leave a comment, move an object) have a near-zero learning curve. Context Fit is high because design reviews happen in meetings and async threads, and a browser link slots into both without ceremony. The notable point is that the fit is highest for non-designers - the population legacy tools excluded entirely.

Results #

• MAU grew from 4M (2022) to 13M (Q1 2025), with roughly two-thirds (~67%) being non-designers, confirming collaboration as the behavior driving adoption (SEC filing, S-1). BS-0065

• 95% of Fortune 500 companies use Figma; third-party analysis puts its collaborative-design market share at 38.5% (SEC filing / third-party, 6sense).
• Net revenue retention reached 132% (Q1 2025), indicating teams expand usage once the collaborative behavior is established (SEC filing, S-1).
• Adobe offered ~$20B (~50x revenue) to acquire Figma in 2022; the deal was terminated in December 2023 amid regulatory pushback (press-reported).

Limitations #

Behavior selection was not the sole driver, and this case should not be read as if it were. The browser-based multiplayer engine was a genuine technical moat: collaboration-first competitors like InVision and Sketch-plus-Abstract had the same behavioral thesis and failed on execution. Technical differentiation and execution quality are therefore co-drivers of the outcome, not footnotes to it. Figma’s growth also coincided with the remote-work shift, which inflated demand for browser-based collaboration tools generally. Finally, the headline metrics come from a pre-IPO S-1, a document written to support a listing narrative; independent verification of MAU and engagement figures is limited.

Lessons #

1. Select the unit of behavior, not the behavior alone. “Collaborate in the file” versus “design, then share” is a choice about what the product’s atomic action is. Getting that unit right turned a feature competitors could copy into a workflow they could not dislodge.
2. The excluded population is often the growth population. Two-thirds of Figma’s users are not designers. Lowering the capability bar for stakeholders, the people legacy tools ignored, drove more adoption than adding expert power features.
3. Behavioral insight needs an execution moat to become a durable advantage. Others saw that design was collaborative. Only the team that solved browser-based multiplayer rendering could act on the insight. Behavior selection tells you where to aim; it does not fire the shot.

Sources #

• How Figma’s multiplayer technology works (Figma blog)
• Adobe and Figma terminate $20B deal amid regulatory pushback (TechCrunch, 2023)
• Figma S-1 Filing (SEC, 2025)
• Figma market share (6sense)
• Evidence Ledger: BS-0065