Article Design Systems Automotive & Mobility

A System Is Established Only When Other Teams Can Use It

When a system rollout reaches only the design team, other teams continue working in their own ways. A sounder approach is to define success by whether other teams can use the system independently, and make that standard explicit in an adoption checklist.

Qingmei Future InsightsMarch 16, 20267-minute read

Key points

A system rollout should extend adoption beyond the design team.
Left unchecked, the same outcome repeats: other teams continue working in their own ways.
Start by defining success as other teams being able to use the system independently.
Record that decision in an adoption checklist, with the design lead accountable for it.
From then on, assess adoption against one question: can a colleague outside the design team use a component correctly without help?

01What to Decide First About System Adoption

The first step in system adoption is not to repackage a system used only by designers. During rollout, the sequence of decisions matters more than wording in determining whether other teams continue working in their own ways.

If you begin by rewriting the language, the team may assume adoption has improved while everyone else continues working as before.

Define success by whether other teams can use the system independently. Until then, adoption remains confined to the design team.

02Which Adoption Decisions Must Wait?

Some decisions must wait. Discussing channels, visuals or messaging before defining success as independent use by other teams simply preserves a design-only system under a different description.

Later decisions still matter, but they must follow the choices made earlier. Otherwise, teams keep addressing symptoms while other teams continue working in their own ways.

03The Adoption Sequence Is Part of the Design

Set out the sequence in three steps: first, define success as independent use by other teams; next, create an adoption checklist; only then, allow external messaging to change.

Reverse that sequence and adoption may look busy while remaining confined to the design team.

04Use Tools to Keep Adoption in Sequence

The adoption checklist should make the sequence clear. Anyone reading it should know what has been decided and what cannot change yet.

After each phase of rollout, use the adoption checklist to check whether campaign demands have disrupted the sequence.

05When to Review System Adoption

Assign ownership to the design lead. When an exception breaks the sequence, revise the rules in the adoption checklist instead of improvising a new instruction in a group chat.

The review asks just one question: can a colleague outside the design team use a component correctly without help? Only a clear answer shows that the sequence is working in practice.

Framework

The Four Layers of System Adoption

From non-negotiable commitments to practical tools, each layer answers one question, keeping system adoption from becoming another exercise confined to the design team.

L1Ready to Use

This layer defines what cannot be compromised in system adoption.

L2Help Still Needed

This layer turns system adoption into conditions that can be checked.

L3Guidance to Add

This layer defines what may change across different contexts as the system is adopted.

L4Not Yet Established

This layer puts adoption into the hands of those using the system and specifies the exceptions.

Note: This diagram is a conceptual framework. It explains a way of thinking and is not statistical data. Source: Qingmei Future Insights.

Recommended actions

Action 01

Start from the site

Identify the moments in the rollout when teams actually use the system. Start there, rather than revising material used only within the design team.

Action 02

Keep it to one page

Replace lengthy explanations with adoption checks. Keep only what supports one standard: other teams must be able to use the system independently.

Action 03

Judge it by one question

After each rollout phase, ask one question: can a colleague outside design use a component correctly without help? Until you can answer, the adoption plan is not yet actionable.

Action 04