A Design System Needs an Owner
If a design system is considered complete as soon as it is published, exceptions accumulate and no one updates the system.
Article Design Systems Technology
Templates Should Preserve Decisions, Not Eliminate Every Difference
When a template dictates every detail, people tend to copy it exactly or abandon it altogether. A more effective approach fixes only the non-negotiable decisions and allows variation elsewhere. The template guidelines should make that choice explicit.
Key points
- A template should do more than prescribe every detail.
- Left unchecked, the same pattern repeats: people copy it exactly or abandon it altogether.
- Start with a different principle: fix the non-negotiable decisions and allow variation elsewhere.
- The design lead should make that choice explicit in the template guidelines.
- Use one acceptance criterion: can users explain where variation is allowed?
01Translating Templates into Practice
Putting a template in a file does not make it ready for use. The first step is to fix the non-negotiable decisions and allow variation elsewhere.
Simply shortening an overly prescriptive template leaves users facing the same choice: copy it exactly or abandon it altogether.
Fix the non-negotiable decisions and allow variation elsewhere. Until then, the template still dictates every detail.
02Where Templates Lose Their Intent
Templates most often lose their intent when work is divided among teams. Each department takes away a convenient instruction, without the boundaries that give it meaning.
The template still appears to prescribe every detail, while internally no one can explain why people either copy it exactly or abandon it altogether.
03The Smallest Useful Unit of Template Guidance
The smallest useful unit is a judgment someone can apply on the spot. Template guidelines should provide that unit of guidance.
With the template in hand, users should have no need to guess what the brand team would think.
04The Template in Users' Hands
During template reviews, examine one real application and check whether the guidelines have slipped back into prescribing every detail.
Revisions can be useful. The problem is failing to acknowledge that a revision has changed the template.
05Where Judgment Belongs
Judgment should stay with the people using the template. The design lead must also give them authority to reject requests that conflict with the guidelines.
End training with one question: can users explain where variation is allowed?
Framework
The Four Layers of a Template
From non-negotiable principles to tools for everyday use, each layer answers one question, keeping the template from slipping back into prescribing every detail.
L1Fixed Decisions
This layer defines what is non-negotiable in the template.
L2Room for Variation
This layer turns the template into criteria that can be checked.
L3Why
This layer defines what can change when the template is used in different contexts.
L4Misuse
This layer puts the template in users’ hands and makes the exceptions explicit.
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 when people actually turn to the template. Start there, rather than trying to lock down every detail.
Action 02
Keep it to one page
Use concise template guidance in place of lengthy explanations. Keep only what supports the principle: “Lock in the non-negotiable decisions; allow variation everywhere else.”
Action 03
Judge it by one question
At the template review, ask one question: can users explain where variation is allowed? If they cannot, the decisions are not yet clear.
Action 04
Name the owner
The design lead. Without an owner to maintain it, a template will be quietly altered when conflicts arise.
Related
All insightsRelated insights
New Components Need Clear Criteria for Entry
If anyone can add a component whenever they need one, the number of components grows while the system becomes harder to use.
Record Exceptions Before They Become Unwritten Rules
In everyday design work, a verbal agreement to make a one-off exception often leads to the same exception recurring until it becomes the rule in practice.