Framework · Design systems · 3 min read
Design system adoption playbook
Seven moves that get teams to adopt the design system without policing: involve early, make the right way easy, show the benefit, pilot, migrate incrementally, listen to rejection, escalate rarely.
- 1Involve early
Put contributors from the domains on the council before you decide.
"Who should help shape this?" - 2Make it easy
Good docs, templates, plugins and starter files make the right way faster.
"Is our way the fastest way?" - 3Show benefit
Dev hours saved, fewer QA bugs, faster handoff, in their terms.
"What does this team gain?" - 4Pilot
Start with a willing team, then publish the results.
"Who wants to go first?"
- 5Migrate slowly
New screens use the system; old ones migrate when touched.
"What is a realistic timeline?" - 6Listen
A team refusing a standard often reveals a gap in the standard.
"What is missing for you?" - 7Escalate rarely
Only for the core tier and real user impact, with evidence.
"Is this core, and does it hurt users?"
Use it when
- You launch a new shared component, such as a data table, and need several domains to move to it.
- A team says "we don't want to use the design system" and your first instinct is to escalate.
- Someone asks you in an interview or a leadership meeting: "How would you handle teams that don't want to adopt shared standards?"
How to use it
- Involve teams before you decide. Put contributors from the domains on the council, so the standard is not decided without them. Output: a council with members from several domains.
- Make the right way the easy way. Invest in good docs, templates, plugins and starter files, so using the system is faster than building your own. Output: a starter kit a new screen can begin from.
- Show the benefit in their terms. Talk about dev hours saved, fewer QA bugs and faster handoff. A before/after story from a past migration or rollout works well. Output: one benefit story per audience (designers, developers, product managers).
- Pilot with a willing team, then publish the results. Pick a team that wants to try it, support them closely, and share what happened, including problems. Output: a short pilot write-up.
- Migrate incrementally. Agree the rule "new screens use the system; old ones migrate when touched", instead of a big-bang migration. Output: a written migration rule and a realistic timeline.
- Listen to rejection, escalate rarely. When a team refuses, ask why: missing feature, migration cost, or no visible value. Fix gaps in the system. Escalate only for the core tier and real user impact, with evidence. Output: a list of gaps found, and very few escalations.
Worked example
An internal operations platform with 6 product teams. The design system has a new shared data table. The billing team refuses to adopt it.
| Move | What the UX lead did |
|---|---|
| Understand why | Asked the billing designer and tech lead. Reasons: no inline editing, and three weeks of migration work. |
| Listen to rejection | Inline editing was a real gap. It went to the contribution process with billing's use cases. |
| Migrate incrementally | Agreed that billing's new screens use the table now; existing screens move when they are next changed. |
| Show the benefit | Shared the pilot from the warehouse team: fewer table bugs in QA and a faster handoff. |
| Escalate rarely | No escalation needed. The table is core, but the timeline was realistic and the gap was fixed. |
Watch out for
- Enforcing by authority. Mandates without a reason get minimal compliance and quiet workarounds. Make the case with evidence first.
- Treating resistance as a people problem. "They just don't like change" stops you from seeing the gap in the system. Ask what is missing.
- Big-bang migration. Asking teams to rebuild everything at once makes the cost visible and the benefit distant. Migrate when screens are touched.
- Escalating recommended patterns. If you escalate everything, escalation stops working. Save it for the core tier and real user impact.
Template
Use this answer when someone asks how you would handle a team that won't adopt. Adapt the words to your own voice.
"First I'd want to understand why: is the component missing something,
is migration too expensive, or do they not see the value?
Then I'd see whether it's a gap we should fix in the system, whether we
can make migration incremental, and whether it's a core standard or a
recommendation.
For core standards that affect users across tools, I'd make the case
with evidence and agree on a realistic timeline.
Most resistance is information, not opposition."
- Design That ScalesDan MallBook · 2023 (Amazon)
- Managing Change in your Design SystemNathan CurtisVideo (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.