Figma: 2026 AI report on how AI reshapes design team collaboration
Figma released its third annual AI report alongside Config 2026, drawing on 8,403 survey responses and 639 interviews from designers, developers, and product managers across ten global markets: the US, UK, Japan, Germany, France, Canada, Australia, Brazil, India, and South Korea. The report tracks how AI adoption is changing collaboration patterns within product teams.
The headline finding—41% of respondents say AI meaningfully changes how their teams work together, up from 7% two years ago—indicates a shift that has moved from experimentation into structural practice at a significant share of product organizations.
Cross-functional blurring
The report’s most striking data concerns role boundaries. Designers participating in development work doubled to 41%. Developers doing design work rose from 44% to 60%. Figma attributes much of this to shared canvases: 76% of product builders spend at least half their working time on collaborative canvases, which allows teams to explore and iterate in one shared space rather than handing artifacts back and forth through handoff tools or documentation.
This is less about job titles dissolving and more about the practical reach of each role expanding. A designer can prototype directly in code; a developer can iterate on layout. AI tools lower the skill floor for both, but the expansion in cross-functional work appears to be a team behavior change as much as a tooling change.
Design’s perceived value post-AI
Despite ongoing concerns about automation, 90% of respondents believe design is at least as important as before the widespread adoption of AI tools, and 60% say it has become more important. The report interprets this as evidence that design value is migrating from execution toward judgment: quality control of AI outputs, strategic direction, and maintaining standards that models cannot reliably self-impose.
Four organizational approaches to AI adoption
Figma categorizes how product organizations are handling AI integration:
- Unified (36%) — organization-wide rollouts with top-down support and shared tooling standards
- Directive (27%) — AI use mandated by leadership with limited bottom-up input from practitioners
- Grassroots (20%) — individual teams or designers experimenting independently without central coordination
- Nascent (18%) — early exploration with no defined strategy or rollout plan in place
The distinction matters for practitioners trying to understand why AI adoption looks so different from company to company even when the tools are identical. A grassroots environment produces fragmented workflows; a directive one may mandate tools that don’t fit actual workflows. The unified group—36% of respondents—appears most likely to see durable productivity gains.
Who this is for
Design leaders and product managers planning AI integration strategies, HR and talent teams reassessing hiring and role boundaries, and practitioners trying to understand what their peers are actually doing with AI tools across different industries and markets.