Figma Needs Person-Level Network Effects

Diving deeper into

Matthew Moore, Head of Design at Lime, on Figma vs. Adobe

Interview
Discord has accomplished much of what we're thinking of as traditional network effects, expanding beyond the organization.
Analyzed 4 sources

The key difference is that Discord compounds value at the level of the person, not just the company. A designer uses Figma mainly because coworkers and files are already there inside the same workspace. A Discord user carries one identity across many servers, so every new community joined makes the product more useful everywhere else. That creates a classic cross community network effect that Slack style enterprise tools rarely get.

  • Figma’s strongest loop is inside one company. Teams centralize design files, comments, prototypes, libraries, and developer handoff in one browser workspace, then viewers become editors as collaboration deepens. That is strong seat expansion, but it is mostly organizational, not consumer social graph expansion.
  • Discord was built for large free communities. Servers are free to create and join, users keep the same identity across gaming, crypto, AI, and fandom groups, and monetization sits on the individual through Nitro, server boosts, and a cut of paid memberships. That pricing model works for communities at internet scale.
  • Figma’s community features, like plugins, templates, and shared inspiration, help discovery and onboarding, but the actual work and budget owner still sit inside the company. That is why FigJam and adjacent products mattered, they were attempts to pull marketers, PMs, and other non designers into a broader multi team workflow.

The path forward is clear. If Figma wants Discord like network effects, it has to make individual identity and cross company participation matter more than file access inside one org. That likely means more creator style distribution around templates, plugins, design systems, and lightweight collaboration products that travel with the user between workplaces.