Principle
Standardize the part users should not have to relearn
Variation is expensive when it carries no useful information.
Before you use it
- Use when
- Similar tools or workflows use different labels, control locations or sequences for no meaningful reason.
Keep this limit in mind
- Do not standardize away domain-specific distinctions merely to make interfaces look uniform.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Standardize recurring control positions, terminology, states and routine sequence where differences do not serve the task. Preserve variation only where context genuinely requires it. Familiar consistency reduces training burden and slip risk when people move between similar processes.
An example
Use the same status names and escalation semantics across several internal support workflows instead of local synonyms for identical states.
Check your result
A person moving between comparable workflows encounters fewer arbitrary differences without losing necessary context.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingStandardize the part users should not have to relearn
Evidence and sources
Human-factors guidance treats standardization of equipment and processes as a reliability strategy that reduces unnecessary variation and retraining burden.
Standardization can suppress legitimate local adaptation when contexts differ materially.
Human Factors Engineering · Standardization
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.