Beyond efficiency: what design systems now deliver
For years, the argument for investing in a design system rested on productivity: less rework, faster handoffs, tighter design-to-dev collaboration. But recent research from the Design Executive Council (DXC), based on interviews with companies at various growth stages, suggests that framing is now too narrow. Organizations are increasingly treating design systems as instruments for customer retention, global expansion, and revenue growth—not just internal cost savings.
That shift matters for how teams pitch their work. Operational efficiency remains a measurable benefit, but executives often respond better to outcomes they already track, such as adoption, engagement, and satisfaction. The organizations profiled in the DXC report illustrate how design system teams are linking their output to those metrics, and in some cases, to top-line results.
Proving value through customer health metrics
Rather than inventing new KPIs, many teams are mapping design system work to existing customer health indicators. Freshworks, for example, ties its design system to a 28% reduction in customer service costs and faster support ticket resolution. The company also uses customer feedback to steer its design roadmap: after learning that new users struggled with onboarding, the team launched a workstream to ease that friction, tracking CSAT scores, A/B tests, and funnel diagnostics to decide which components and patterns to build next.
SAP takes a similar approach at a larger scale, feeding more than a million in-app survey responses back into its design system. The goal is continuous improvement driven by real user input, not static guidelines.
Scaling brand, values, and global reach
Design systems also act as a vehicle for extending a company's identity and principles. Linear, which competes on polish, treats its design system as a living tool rather than a rigid rulebook. "It is less about rigid rules and numbers and more about whether the product feels crafted with intention," says product designer Yann-Edern Gillet. That focus is one reason the company sees strong customer loyalty and net revenue retention.
On the global front, design systems help teams navigate regional and cultural complexity. Hyundai Motor Group uses one system to unify more than 30 vehicle models across Hyundai, Kia, and Genesis, ensuring each brand feels native in any market while retaining a distinct identity. Grammarly built localization into its design system from the start, hiring in-house linguists and making right-to-left readability a core input. The company's distributed teams in North America, South Korea, and Poland rely on that shared foundation to stay consistent across languages, hardware constraints, and display sizes. At 42dot, Hyundai's AI and mobility arm, designers even use custom Figma plugins to test multilingual interfaces against their standards.
Better collaboration, measurable gains
Inside organizations, design systems continue to break down silos between design and engineering. At 42dot, the system in Figma functions as a single source of truth, with engineers joining weekly design crits to spot implementation challenges early. "Engineers and designers finally speak the same language. That shared understanding has transformed how we ship," says principal product designer Chris Jacobs.
These qualitative improvements can translate into hard numbers. Grammarly ran an internal survey and found that its design system saved design and development teams 25% of their work week. The company also built a network of 10 design and engineering advocates to drive adoption—so successful that the engineering team offered to trade headcount for more design system investment.
Notion takes a sentiment-focused approach, tracking informal feedback through shared team channels rather than formal handoffs. Engineering and design jointly own quarterly priorities and maintenance, with signals like quick reactions or notes of appreciation indicating how well changes land.
Making the case at the top
For teams needing executive buy-in, visibility at the board level can make the difference. SAP Chief Design Officer Arin Bhowmick elevated the design system to a board-level KPI, tracked through Objectives and Key Results. He also dedicates about 10 hours per week to design reviews to keep adoption consistent.
The takeaway from the DXC research is that design systems now sit at the intersection of efficiency and strategy. Their impact can be measured through inputs like time savings and collaboration, as well as outputs like customer retention and revenue. As teams adapt to the AI era, maintaining craft and consistency at scale only becomes more dependent on a well-supported design system.
