Figma's 2026 AI report, The new era of multiplayer design, is built on three years of data: 8,403 survey responses and 639 qualitative interviews with designers, developers, and product managers. The sample now covers ten markets, with Brazil, India, and South Korea added alongside the United States, United Kingdom, Japan, Germany, France, Canada, and Australia.
From individual output to team workflows
The 10x engineer—the individual whose output sets them apart—has long been the reference point for productivity. But when AI can 10x anyone, personal productivity is no longer the thing to optimize. For the first time in the three years of data, AI is meaningfully changing how teams work together: 41% of respondents say so today, compared to only 7% two years ago.
Roles are converging as well. Over the last year, the number of designers participating in development doubled to 41%, and developers doing design work rose from 44% to 60%.
Single-player work moves onto the canvas
The bigger shift isn't what people can do, but where they do it. Teams are turning single-player workflows into multiplayer ones on the canvas. Today, 76% of people do at least half their work on the canvas, and six in 10 spend the bulk of their time there. Even one in five developers would rather start projects on the canvas.
The reasoning is spatial: a terminal or a prompt is a solo space, where you can't riff with someone else or put designs side by side. On the canvas, teams can explore ideas, get feedback, and work through a problem space together.
Deciding what's worth building
AI can build almost anything, but it can't determine what's worth building. When prototyping is fast, choosing what ships matters more; when drafting copy is easy, deciding what to say matters more; when generating assets is cheap, differentiation is critical. Good calls get sharper when teams weigh conflicts, directions, and trade-offs together.
That decision-making was always part of design—AI has just made it more crucial. Ninety percent of respondents say design is at least as important as it was before AI, and nearly six in 10 say it's more important. Developers agree: 65% say the same. As one software engineer puts it, "Design, taste, and the user experience matters more than before, so we are trying to improve it every single day."
Ultimately it's more of an organizational gap, exposing some of our communication and knowledge gaps across squads.
— Principal product designer at a grassroots company
Four patterns of adoption
The share of designers, developers, and PMs calling AI "transformational" has tripled in the past year, but usage pace and sentiment still vary. The report identifies four adoption patterns: grassroots, directive, nascent, and unified.
- Directive: AI adoption is driven from the top down.
- Grassroots: adoption bubbles up from practitioners on the ground.
- Nascent: adoption is still early.
- Unified: individuals and organizations move AI adoption forward together.
Both directive and grassroots companies run into friction: people aren't on the same page, and teams lack a shared playbook. The goal is unified adoption.
What to do from where you are
The path forward depends on the experience a team is having today. Grassroots changemakers should socialize what's working—make workflows visible, build structure around them, and champion shared spaces. Those pushing AI at a leadership level should work on closing the gap between strategy and practice.
The pressure to move faster and make better decisions is universal, but the report's framing is collective: it's not about how fast any one person moves, but how everyone moves fast together.



