Communicating Value

A design system has to justify itself in the funder’s terms. “It’s more consistent” and “it’s more efficient” are true, but they read as nice-to-haves to anyone who doesn’t use the system day to day. The bar is low industry-wide: zeroheight’s Design Systems Report 2026 (147 practitioners) found only 5% of teams measure ROI at all. A team with any credible value story is already ahead of most of the field.

The problem

“A style guide is an artifact of design process. A design system is a living, funded product with a roadmap & backlog, serving an ecosystem.” — Nathan C., via Brad F.

A style guide can just sit there and still be useful. A design system can’t: it has to keep earning its funding. Systems that can’t explain their value beyond “it’s tidier” are the first thing cut in a budget squeeze, because nobody outside the team can see what’s at stake in losing them.

Practices

Translate value into each funder’s terms

A CFO cares about cost and time saved, in real numbers. A CTO cares about velocity and a lower long-term maintenance burden. A CEO or product leader cares about speed to market and whether the product feels coherent at scale. The system’s internal metrics, like component count or token compliance, mean nothing to any of them. The translation has to happen before the pitch. Sources: Supernova, “Getting Executive Buy-In and Proving ROI of Design Systems” and Adobe XD, “20 levers for communicating the value/ROI of design”.

Argue beyond productivity

Figma’s Design Executive Council research notes that the value conversation used to be almost entirely about productivity: less rework, faster handoffs. That’s only part of it. Organizations increasingly invest in design systems to scale product offerings, improve retention, expand into new markets, and raise the craft bar. The same research has named examples, which persuade better than abstract advice because the numbers come attached to a real outcome:

Freshworks credited its design system with a 28% cut in customer service costs and faster support-ticket resolution, an outcome the whole org cares about.
SAP feeds over a million user data points from in-app surveys into the system. Its Chief Design Officer put the design system on the board’s agenda as a KPI tracked through OKRs.
Hyundai Motor Group uses its system to unify 30+ vehicle models across three brands (Hyundai, Kia, Genesis). Every interface feels native to its market while keeping a distinct brand identity, an argument no productivity metric captures.
Grammarly made localization a strategic input from the start, with in-house linguists and right-to-left readability treated as core requirements.
Linear frames its system’s value less as rigid rules and more as enabling the craft and quality that drive loyalty and retention.
Notion tracks lightweight “sentiment signals,” feedback moving naturally through team channels, as an ongoing value indicator alongside formal reviews.

Put a dollar figure on it

“It saves us time” is easy to dismiss. A dollar figure, even a crude one, is something a finance stakeholder can evaluate and repeat to someone else. Mike Fortuna’s account walks through turning design-system time savings into an actual dollar figure. Estimating ROI covers keeping that figure honest once it goes into a business case.

A simpler illustration, meant to persuade rather than measure: if a moderately complex component takes three days to design, build, and test, and fifty product teams each build their own, that’s 150 days of duplicated work for something built once and shared. The arithmetic is rough, but executives find it persuasive because it’s easy to hold in your head.

Common mistakes

Leading with internal health metrics when pitching outward. Component count, token compliance, and adoption percentage are the right numbers to track and improve. But they mean nothing to someone who has never opened the docs. Lead with the business metric the stakeholder cares about, and keep the operational numbers as supporting detail.