Slack From the Start | Figma Blog (opens in new tab)

Figma chose to build its collaboration experience around Slack rather than recreate messaging and notification features. User research showed that Slack was already central to designers’ daily workflows and correlated with more transparent collaboration. By making a Figma team a Slack team and routing notifications through Slack, Figma aimed to reduce tool fragmentation and strengthen its core product.

Why Slack Mattered to Figma’s Users

• Figma interviewed many designers about file storage, specifications, and product decisions.
• More than half of the designers surveyed reported using Slack throughout the day.
• Slack adoption was associated with more open and transparent design processes.

Building on Slack Instead of Duplicating It

• Figma considered recreating communication features inside its own product.
• The team rejected that approach because it would create another inbox and require users to manage teams in two places.
• Instead, Figma built its collaboration model on top of Slack:
  • A Figma team corresponded to a Slack team.
  • Figma file notifications were delivered through Slack.
  • Communication about design remained connected to users’ existing workflows.

A Strategic Platform Bet

• Figma viewed Slack as a platform well before Slack formally celebrated its platform launch.
• Deep integration was considered a significant product and business bet.
• Early results suggested the strategy was working, and Figma expected other companies to adopt similar integrations.

The practical lesson is to integrate with tools users already rely on rather than reproducing their functionality. For Figma, treating Slack as foundational reduced friction and made collaboration feel like part of an existing workflow.