Year after year, the same research keeps confirming what actually makes a design system work, and it's rarely the tooling.

Every year, a handful of research-backed reports, chiefly zeroheight's Design Systems Report and Sparkbox's long-running Design Systems Survey, poll hundreds of practitioners on how design systems actually get built and adopted. Read together across editions, they point to the same truths sharpening year over year. Here's what the current data shows, and why it matters for any team scaling a system past the prototype stage.

The data sources worth trusting

zeroheight's report is now in its fourth annual edition, surveying just under 300 designers, engineers, and product professionals in 2025. Sparkbox has run its survey since 2018, splitting respondents into "maintainers" who build systems and "subscribers" who consume them. Both are self-reported samples skewed toward practitioners already engaged enough to take the survey, useful for tracking direction, not treated as hard population statistics.

Dedicated teams keep correlating with healthier systems

zeroheight's 2025 report found 79% of organizations now have a dedicated design systems team, up from 72% in 2024. Every company-size segment saw dedicated-team prevalence rise by at least 10 percentage points year over year. Yet team sizes still top out around 20-25 people, even three years after zeroheight's first survey. Maturity hasn't meant headcount growth.

Tokens crossed from niche to default

84% of teams reported adopting design tokens in 2025, the report's clearest adoption story. Tokens are meant to keep decisions synced between design tools and code, but most teams are still stitching that pipeline together manually rather than automating it.

Governance works best light, not heavy

The healthiest systems keep governance minimal: enough to stay trustworthy without slowing contribution. Sparkbox's data ties success to how often users actively contribute back, not just top-down documentation.

The real bottleneck is buy-in, not tooling

Resource constraints and communication breakdowns remain the top blockers to adoption, more than any technical detail. This has been the throughline since 2018.

AI is present, but still marginal

Only 10% of teams use AI for design-system tasks like documentation, a modest figure that tempers the hype around AI-native systems.

If your studio is building a design system, the data is clear: invest in the team and the governance conversation before the tooling.