Protocol
Change the design so the mistake has less room to happen
A better warning is not always the best prevention.
Before you use it
- Use when
- The same predictable error keeps returning despite reminders to be careful.
Keep this limit in mind
- Validation can reject legitimate cases or create unsafe workarounds. Test boundaries and do not claim one control makes the whole system error-proof.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
A better warning is not always the best prevention.
Steps
- Identify the exact action or omission that creates the recurring error.
- Prefer a suitable design constraint or immediate validation that prevents that error path, then test legitimate exceptions.
An example
An import form validates the required identifier format before accepting a file, rather than relying on a note that operators routinely miss.
Check your result
Does the change block the specific mistake while still allowing valid work?
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 readingChange the design so the mistake has less room to happen
Evidence and sources
Error-proofing changes the process or design to prevent or detect a specific mistake.
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.
Error-Proofing · Definition and examples
All sources (1)
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-12