AI is now the default.
The question is no longer whether to adopt. 74% use Claude. 56% use Figma Make. Most teams juggle 2–4 tools.
ZEROHEIGHT RESEARCH · 2026
123 practitioners. 8 sections. The data on what's working, what's not, and what to do about it.
Free · Instant access · No spam
Join 2,400+ design system practitioners
KEY FINDINGS FROM 123 RESPONDENTS
82%
of teams use AI
in some form
61%
say usage increased
significantly this year
63%
most satisfied with AI
for writing documentation
50%
say shadow AI is
creating real problems
WHAT’S IN THE REPORT
123 practitioners, mostly in-house product design leaders at mid-to-large technology companies.
82% use AI. 61% say usage grew significantly. The question is what to use it for.
Documentation wins. Design generation disappoints. The satisfaction gap is the story.
Only 17% rate docs as ‘very AI-ready.’ 48% already run an MCP server.
50% say other teams’ AI use is creating problems. 44% of orgs tolerate it.
25% say ‘no time’ is the top barrier. Budget isn’t the blocker. Time is.
63% feel favorable. 67% say AI is overhyped. Top concern: output quality.
Eight data-backed moves. Documentation first. MCP second. Quality over adoption.
INSIDE THE REPORT
The question is no longer whether to adopt. 74% use Claude. 56% use Figma Make. Most teams juggle 2–4 tools.
Documentation is the standout win. Design generation is the biggest miss — a −53 net satisfaction score.
Half of teams say other parts of the org are using AI without involving the design system. 44% simply tolerate it.
Optimism and scepticism in the same breath. 63% feel favourable. The top concern isn’t job loss — it’s output quality.
ZEROHEIGHT RESEARCH
123 practitioners. 8 sections of data, charts, and actionable insights on AI in design systems.
Free · Instant access · No spam
Join 2,400+ design system practitioners
No spam. Unsubscribe anytime.