Adoption

Question 1

Roughly what share of your product interfaces is built with design-system components?

Adoption share is the outcome metric. Everything else in this check is an input to it.

Question 2

How do you know that number?

An estimated adoption rate cannot be steered. A measured one turns the system from a cost centre into a reportable asset.

Question 3

What enablement do teams get beyond documentation (training, office hours, pairing)?

Documentation answers known questions. Enablement surfaces the questions people did not know to ask.

Question 4

Where do consumers go when something is broken or missing, and how quickly do they get an answer?

Support latency is the most direct signal of whether the system feels like a product or a favour.

Question 5

How do you handle teams overriding, forking or detaching components?

Overrides are data, not misbehaviour: each one marks a gap the system has not covered yet.

Question 6

How is the design system positioned by leadership?

Adoption stalls at the point where using the system costs a team more than ignoring it — that trade-off is set above the team.