Designed enterprise collaboration features including live cursors and commenting system that drove 200% growth in enterprise revenue.
Role
Product Designer
Team
Timeline
2024 - Present
Skills
The collaboration features drove a 200% increase in enterprise revenue within 18 months. Adoption hit 85% among enterprise accounts in the first quarter. Average design review time dropped from 3.5 days to 1.2 days, and external tool usage for design feedback fell by 70% among enterprise teams. Featured in the Figma Config 2022 keynote as the centerpiece of the enterprise announcement.
Figma's real-time cursors were magical for teams working at the same time in the same room. But enterprise design teams don't work that way. They're distributed across time zones, juggling asynchronous feedback loops that stretch over days. The existing commenting system lacked threading, mentions, and resolution tracking, which meant teams were using Slack, Loom, and email for the actual design review process — fragmenting the feedback loop and creating version confusion.
I led the design of enterprise collaboration features over 14 months, creating the tools that brought the entire review process back into Figma. The project directly contributed to Figma's push into the enterprise market and became a key differentiator in enterprise sales conversations.
I embedded with 8 enterprise design teams for two-week observation periods each, mapping their end-to-end review workflows and documenting every touchpoint, handoff, and communication channel. The picture that emerged was striking.
The average design review involved 4.2 different tools and took 3.5 days from review request to final approval. Designers were spending 30% of their review time just context-switching between tools to consolidate feedback. And the most common pain point, repeated almost verbatim across every team: "I don't know if my feedback was seen, acknowledged, or acted on."
65% of enterprise teams reported missing critical feedback because it lived outside Figma. The irony was that Figma had built the best real-time collaboration canvas in the industry, but the actual collaboration — the back-and-forth of review and iteration — was happening everywhere except on that canvas.
I designed a unified system that addresses each stage of the review process. Threaded comments support full conversations with rich text formatting, and they attach to specific design elements — moving with those elements through iterations so context is never lost. Smart @mentions suggest the right people based on team structure, recent collaborators, and file ownership, then trigger notifications across email, Slack, and in-app so feedback reaches people wherever they work.
Resolution workflows let teams track the lifecycle of every piece of feedback. Comments can be marked resolved with full history preserved. Design leads can filter by status, batch resolve, and view resolution analytics. Enhanced presence indicators show not just where teammates are on the canvas but what they're doing — viewing, commenting, or actively editing — so you know whether to wait or jump in.
Beyond the collaboration tools themselves, I designed the SSO onboarding flow and team management interfaces that enterprise admins require. The permissions model maps to corporate hierarchy while preserving Figma's open collaboration ethos — a delicate balance, since enterprises need control but designers need freedom.
I also built admin dashboards that surface team collaboration metrics: active reviewers, average review time, feedback resolution rates. This gives design leadership visibility into their team's workflow health and helps them identify bottlenecks before they become problems.
The shipped system closed the loop that had been open since Figma's earliest days. Real-time collaboration was always Figma's strength, but now asynchronous collaboration is equally strong. Design teams can run their entire review process — from initial feedback through iteration to final sign-off — without leaving the canvas. The feedback that used to get lost in Slack threads and email chains now lives right next to the work it refers to.