# Standardize the part users should not have to relearn

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Standardize the part users should not have to relearn

ID: MHC-D-RESEARCH-0485 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/standardize-the-part-users-should-not-have-to-relearn

Variation is expensive when it carries no useful information.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Similar tools or workflows use different labels, control locations or sequences for no meaningful reason.

### Avoid when

- Do not standardize away domain-specific distinctions merely to make interfaces look uniform.

### Explanation

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.

### Example

Use the same status names and escalation semantics across several internal support workflows instead of local synonyms for identical states.

### Check

A person moving between comparable workflows encounters fewer arbitrary differences without losing necessary context.

### Limits

- Do not standardize away domain-specific distinctions merely to make interfaces look uniform.

### Evidence and sources

- supports: Human-factors guidance treats standardization of equipment and processes as a reliability strategy that reduces unnecessary variation and retraining burden. — RS-272D6838C3209365. Standardization can suppress legitimate local adaptation when contexts differ materially. (Standardization)
- RS-272D6838C3209365: Human Factors Engineering — https://psnet.ahrq.gov/primer/human-factors-engineering

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/use-a-checklist-for-omissions-not-for-pretending-judgment-disappeared
