Measuring Design System Impact: Insights from Industry Leaders
Craft Across: Measuring Design System Impact
This is a summary from the event. If you would like to watch the full recording and get access to all the resources, check out the event page.
Measuring design system impact is one of the most critical but often overlooked aspects of design system success. We at Infa recently hosted a deep-dive session with design system leaders from Datadog, Yahoo, and Volvo Cars to explore practical approaches to quantifying design system value.
Why Measure Design System Impact?
Metrics serve as evidence that guide our decisions and validate our direction. As Natalya Shelburne from Datadog explains, "We all want to make sure that the work we do has an impact. How do we know which decisions to make, which direction we're going to validate that direction? We have to have some sort of metrics and data points to guide our actions and decisions."
We all want to make sure that the work we do has an impact. How do we know which decisions to make, which direction we're going to validate that direction? We have to have some sort of metrics and data points to guide our actions and decisions.But measuring impact isn't just about collecting numbers—it's about understanding what your organization values and aligning your metrics accordingly.
Design Systems Are Infrastructure, Not Optional
One of the most powerful reframes from our session: design systems are infrastructure, not a "nice to have" feature. As Natalya puts it, "Why in this year 2025 are we entertaining the conversation that a core bit of infrastructure needs buy-in? Think about how many successful companies who have scaled needed to scale their brand and design have all really come to the conclusion that design systems should exist."
The conversation shouldn't be about justifying why you need a design system—it should be about understanding what pressures stakeholders are under and addressing those concerns directly. Sometimes the question isn't really about metrics; it's about whether design is respected as a discipline.
Metrics Are Signals, Not Goals
Brian Alfaro from Yahoo emphasizes that metrics depend on where you are in your design system maturity journey. For early-stage systems, qualitative feedback from surveys and interviews provides the most valuable insights. As you mature, you can layer in quantitative data from Figma Analytics, code repositories, and product usage like Infa.ai.
Tiago Almeida from Volvo Cars makes an important distinction: "Adoption is almost like a signal instead of a metric. It's almost like, okay, why aren't people adopting this? Is it because of the system? Is it the culture thing? Is it like lack of skills in the team?"
You'll never achieve 100% adoption—and that's okay. Custom components and experimental features will always exist. The goal isn't perfect adoption; it's understanding what adoption signals tell you about your system's health.
Focus on Human Metrics, Not Just Efficiency
While efficiency metrics matter, the most successful design systems focus on human-centered outcomes. Brian shares his framework for measuring impact through human metrics:
- Is what I'm doing useful? The most useful thing?
- Am I building trust? Or taking away trust?
- Is it creating emotional relief? Or adding stress?
- Is it easy to learn? Or confusing?
- Does the user have control? Or are they giving up control?
As Natalya explains, "A design system is the stable, trusted layer of the UI. That's what allows other teams to experiment because we know that this is the stable, trusted layer that users can reach into."
Measurement by Maturity Level
The complexity of your measurement approach should match your design system's maturity. Understanding your design system stages helps determine which metrics matter most:
Level 1-2: Start with People
- Surveys and user interviews provide immediate value
- Focus on qualitative feedback and pain points
- Track perceived consistency and quality
Level 2-3: Add Tool Analytics
- Use Figma Analytics to track component usage
- Monitor GitHub repositories for design system library adoption
- Measure alignment between design and code
Level 4: Build Data Pipelines
- Combine data from design tools, code repositories, and product analytics like Infa.ai
- Create dashboards for different audiences (contributions, performance, adoption, impact)
- Requires data engineering support for complex integrations
For teams just starting out, our first 90 days playbook provides a framework for establishing measurement practices from day one.
Tools and Techniques
Our panelists shared several practical tools for measuring impact:
- Datadog: For tracking component version adoption across repositories and identifying teams that need support
- Figma Analytics: Built-in usage data for design system components
- GitHub Actions: Analyze codebase usage of design system libraries
- Product Analytics: Tools like Infa.ai for measuring visual adoption in production
- Surveys and Interviews: The most accessible starting point for any team
For more insights on design system measurement strategies, explore our design system insights documentation.
The Storyline Matters More Than the Numbers
Brian emphasizes that metrics need a proper storyline backed by data points. The story you tell depends on your audience:
- Design leaders care about designer experience and workflow efficiency
- Engineering leaders focus on code quality, technical debt, and developer productivity
- Product leaders want to understand impact on delivery speed and user experience
Align your metrics with company objectives and organizational OKRs. If your design system supports faster time-to-market, measure that. If it improves accessibility compliance, track those scores. The metrics should reflect what your organization values.
Practical Next Steps
We at Infa recommend starting with the simplest approach that provides value:
- Begin with qualitative feedback: Conduct surveys and interviews to understand current pain points
- Layer in tool analytics: For product measurement, start tagging and measuring across your product to show deviations and good usage examples, along with references. By using Infa.ai, you can use local boards completely free. You only need a Pro account if you want to track metrics across time, share links, and store screenshots. Use Figma Analytics and GitHub data to track usage.
- Connect to business outcomes: Align metrics with organizational objectives
- Build dashboards for different audiences: Create tailored views for design, engineering, and product leaders
- Focus on trust and collaboration: Remember that design systems are about helping people work better together
The goal isn't to measure everything—it's to measure what matters for your organization and use those insights to create a healthier, more effective design system ecosystem. As Natalya reminds us, "Everything we're talking about here is just people. It's not about buttons or the components or the plugins or the tooling. We're just talking about people collaborating together, trying to make impossible things happen."
Ready to start measuring your design system's impact? Sign up for Infa to track adoption across your product directly in your browser.