Figma Needs Workflow Fit
Matthew Moore, Head of Design at Lime, on Figma vs. Adobe
The hard part of taking Figma from designers to everyone else is no longer collaboration, it is workflow fit. Figma beat Sketch because it replaced local files, exports, and version confusion with one live browser canvas where designers, PMs, and engineers could all work together. In slides, Google already solved live editing, so Figma would need a different edge, likely tighter connection to product work, better reuse of design assets, or a better way to turn working files into narratives without rebuilding them elsewhere.
-
Inside product teams, Figma already acts like a decision workspace, not just a drawing tool. Teams at Lime used it to avoid exporting mockups into Google Slides, because comments, edits, and narrative context could stay in the same file where the design work already lived.
-
That advantage does not automatically carry into company wide presentations. Slide tools need broad horizontal jobs, like embedding charts from Sheets, finding an old board deck by content, and sharing files in formats every stakeholder can open. Those are native strengths of Google Slides and Office style bundles.
-
The closest comp is Canva, which expanded by serving non designers who still make visual work every day, like marketers and sales teams. Its growth shows the prize is real, but it also shows that winning outside design requires templates, asset management, brand controls, and easy output for many roles, not just multiplayer editing.
The next phase of the market is about who becomes the default visual workspace for non designers. Figma is well positioned where slides are closely tied to product and design review. Broader presentation share will go to the company that combines collaboration with distribution, search, data integrations, and easy publishing across the whole business.