Quarter Circle
Circle
Circle

zeroheight / Measurement

Know if your design system is working

See how teams and AI agents actually use your docs, and track adoption through to code. Fix what’s not working, then prove your system’s value.

Measurement / Usage

Make better docs decisions with data

Track page views and engagement trends from teams and AI agents, alongside helpfulness ratings and feedback across your styleguide. Drill into individual pages to see how engagement changed after a release. You can also integrate and measure via Google Analytics.

Measurement / Adoption

Track what actually makes it to code

See how often each component is used across your repositories, right down to the props developers select. Find hardcoded colours that should use tokens and identify repos using older package versions. Sync with GitHub, GitLab, Bitbucket, or Azure DevOps, or use the zeroheight GitHub Action to update tracking after every merge.

Measurement / Docs health

Find the gaps before your users do

Get a clear list of what needs work: content that’s months out of date, missing design or code examples, undocumented Figma components, and searches that come up empty.
Square ShapeCircle ShapeTriangle Shape

Measurement / AI views

Understand how AI is using your docs

Your docs have a new audience. See how AI uses them alongside your teams, from coding agents like Cursor and Claude Code to assistants in Figma, Slack, and Teams.

Measurement / ROI

Have the evidence when leadership asks

Show leadership the value of a well-adopted design system: greater reuse, faster delivery, and less design and technical debt. Demonstrate how teams and AI agents rely on your documentation as a source of truth, and take tangible numbers into your next budget conversation.

Measurement / Feedback

Collect direct feedback from the people using your styleguide

Use a suite of feedback tools to understand what’s working and what needs attention. Capture suggestions when searches return no results, and collect feedback directly on individual pages and blocks.

Frame 1948764792
Richard
a few seconds ago
Resolve
Really clear visual examples — especially helpful for new designers.
Smiling young man in a dark hoodie against a light beige background, showcasing a friendly and approachable demeanor.
Francisco
a few seconds ago
Resolve
Could use more real-world layout examples — hard to know how components come together.
Frame 1948764794
Jess
a few seconds ago
Resolve
Content is improving, but it still feels like some docs were written by different teams — voice and structure vary a lot.
Smiling young man with short black hair wearing a gray sweater, set against a pink background.
Daniel
a few seconds ago
Resolve
The new component pages with usage do’s and don’ts are really helpful.
Smiling woman with long dark hair wearing a maroon sweater against a bright yellow background.
Chloe
a few seconds ago
Resolve
Spacing and layout tokens are much easier to follow now — nice updates!
Frame 1948764797
Mahdi
a few seconds ago
Resolve
Love that the button guidelines now explain when to use each variant.
Frame 1948764798
Bethany
a few seconds ago
Resolve
Would be great to see how theming works across products — not just the default brand.
ADT Security Services Logo
It’s quite clear that the design system has had a huge impact on how people are working and moving.
Patrick Tunga-Lergo
Lead Design System Designer

Measurement / Adoption tracking

The proof is in the product

Track components, tokens and packages across your codebase, and spot where teams and AI agents are hardcoding values or using deprecated versions. See what’s adopted, what needs updating and where technical debt is building before it reaches production.

Screenshot displaying the version information for the @pixelwave/ui-components repository, showing two projects: 'marketing-site' with version 1.1.19 and 'pixelwave-app' with version 1.6.6, both last updated on September 24 at 16:12.

Package adoption

See design system coverage across teams and products – and where action is needed to bring teams back into alignment.
Bar chart displaying component usage statistics in an admin dashboard and file manager, highlighting components like Typography, Box, ListItemText, MenuItem, and AutocompleteInput with varying counts.

Component usage

See how often each component is used in production. Spot version compliance issues and prove which components are doing the heavy lifting.
Token Usage

Token usage

Know which tokens are being used and where raw values are sneaking in. Catch drift before it compounds.

Usage Shapes

Color usage

Catch off-brand values in production before they spread. Know where your palette is being followed – and where it isn't

Color Usage Static
Background Shape

FAQs

  • What does zeroheight's design system platform measure and track?

    zeroheight measures design system adoption end-to-end, from engagement with your documentation to component usage in production code. It tracks which components are used across your codebase, identifies outdated implementations and hardcoded values, shows which documentation pages get read and which get ignored, and surfaces what teams are searching for but can’t find. Everything is available in a single dashboard so design system teams can prove impact and prioritise what needs work.

  • How does zeroheight track component adoption across codebases?
  • Can zeroheight show the ROI of a design system?
  • How does zeroheight collect feedback from design system users?
  • Does zeroheight integrate with existing analytics tools?