# Change the design so the mistake has less room to happen

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

---

## Change the design so the mistake has less room to happen

ID: MHC-D-RESEARCH-0181 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/change-the-design-so-the-mistake-has-less-room-to-happen

A better warning is not always the best prevention.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- The same predictable error keeps returning despite reminders to be careful.

### Avoid when

- Validation can reject legitimate cases or create unsafe workarounds. Test boundaries and do not claim one control makes the whole system error-proof.

### Explanation

A better warning is not always the best prevention.

### Steps

1. Identify the exact action or omission that creates the recurring error.
2. Prefer a suitable design constraint or immediate validation that prevents that error path, then test legitimate exceptions.

### Example

An import form validates the required identifier format before accepting a file, rather than relying on a note that operators routinely miss.

### Check

Does the change block the specific mistake while still allowing valid work?

### Limits

- Validation can reject legitimate cases or create unsafe workarounds. Test boundaries and do not claim one control makes the whole system error-proof.

### Evidence and sources

- supports: Error-proofing changes the process or design to prevent or detect a specific mistake. — lei-error-proofing. Claim basis: professional_convention. Claim limit: One protected error path does not make the whole process error-free.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Definition and prevention examples"].
Agent release review: Checked the named definitions in the May 2025 Kanban Guide, LEI and Meadows. Non-manufacturing examples are editorial applications. The text preserves safe-stop, ownership and contextual boundaries. (Definition and examples)
- lei-error-proofing: Error-Proofing — https://www.lean.org/lexicon-terms/error-proofing/

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (alternative): https://vedokrok.com/knowledge/build-a-checklist-from-real-misses
