How Figma Caught Adobe By Surprise — With Carmel DeAmicis

Episode Summary

Executive Summary: The episode explores how Figma, once a little-known UI design startup, grew into a major Adobe challenger by betting on browser-based, real-time collaboration before the market was ready. Former Figma editor Carmel Diamisis explains how community-building, product quality, and shifting work habits turned resistance into adoption, and why Adobe ultimately bought Figma for $20 billion after underestimating the threat.

Main Topics: What Figma is and why it mattered (Priority: 5/5): Figma is a web-based UI design tool used to create digital interfaces for apps, websites, dashboards, and increasingly other creative work. Its importance came from making design collaborative and browser-native rather than file-based and isolated. The technical bet on web-first collaboration (Priority: 5/5): Figma’s founders built on emerging browser tech like WebGL to make a fast design tool in the browser. This enabled live, multi-user editing similar to Google Docs and fundamentally changed who could participate in design work. Overcoming designer skepticism through community (Priority: 5/5): Designers initially disliked browser-based design and real-time access to files. Figma responded by building trust through evangelists, design advocates, storytelling, and community programs instead of traditional growth marketing. Figma’s growth curve and pandemic acceleration (Priority: 4/5): Diamisis describes a slow conversion from ignorance to awareness to standard adoption, with COVID-19 acting as a major accelerator because remote work made collaborative web tools far more valuable. Why Adobe didn’t move sooner (Priority: 5/5): Adobe had money and adjacent products, but its legacy desktop software, customer resistance to collaboration, and lack of urgency around web-native design kept it from matching Figma in time. What the acquisition means for culture and innovation (Priority: 4/5): The discussion closes on whether Adobe can preserve Figma’s autonomous, user-centered, craftsmanship-driven culture and apply its lessons across Adobe without crushing the product’s strengths.

Key Arguments: Figma’s browser-based design model was not merely a technical change; it reshaped the culture of design by making collaboration earlier, broader, and more fluid. Designers initially rejected collaborative browser tools, so Figma had to win trust through community and evangelism rather than force adoption. The market for Figma was larger than UI design alone because collaborative design opened the door for non-designers to participate and pay for design tooling. Adobe’s delay was partly rational: browser technology had to mature, UI design was not its main battleground, and its users had resisted collaboration when Adobe tried it. The pandemic normalized live collaborative workflows, making Figma’s product feel inevitable and accelerating its mainstream adoption. Adobe’s $20 billion acquisition signals both that Figma was a real competitive threat and that Adobe saw growth upside in adopting Figma’s model and community. The real risk after the acquisition is cultural: if Adobe integrates Figma too aggressively, it could destroy the very autonomy and user focus that made Figma successful.

Data Points: Acquisition value: $20 billion - Adobe’s purchase of Figma, described as one of the largest startup acquisitions ever. Figma founding period: 2012–2013 - Diamisis says Figma began in stealth around this time before public launch. Browser product readiness: ~2012 to 2015 - Years spent experimenting before browser tech like WebGL could support a fast web-based design tool. Public launch: 2016 - Figma did not launch publicly until shortly before Diamisis joined in January 2017. Diamisis join date: January 2017 - She joined as employee number 20 and worked on blog, marketing, comms, and internal communications. Employee count at join: 20 - Figma was still very small when Diamisis arrived. Age of Dylan Fields at birthday mentioned: 23 or 22 - Diamisis recalls his mother bringing cupcakes to celebrate his birthday shortly after she joined. Years to inflection: About 2 to 2.5 years after joining - She says Figma’s adoption felt like it shifted from niche to mainstream during her first few years there. Adobe stock impact: Stock sold off sharply - Investors reacted negatively after the acquisition news because it suggested Adobe had been challenged and forced into defense. Teal Fellowship funding: $100,000 - Dylan Fields and Evan Wallace reportedly received this amount from Peter Thiel to start Figma. Design advocate program size: 30 to 40+ - Diamisis says the community evangelist program grew substantially over time.

Pivotal Quotes: "It was a UI design tool, which means anything digital that you might interact with, your Uber app or you go on Google, maybe even your Tesla dashboard, is probably designed in Figma." — Carmel Diamisis: Explaining what Figma does and how broadly it is used in interface design. "They did not like the idea of the file being open and accessible to anyone." — Carmel Diamisis: Describing the initial designer resistance to browser-based collaboration. "If Adobe tries to squeeze Figma in and make it the same as the rest of Adobe, that's where you could really lose the magic." — Carmel Diamisis: Her warning about the post-acquisition cultural risk.

Implications: The story shows that startup defensibility can come from workflow and culture, not just features. Big incumbents may miss shifts until it’s too late, but only if the newcomer builds a real product moat and community. For Adobe, success now depends on preserving Figma’s autonomy.