Perfect behavior is a dangerous design assumption
Many procedures are written as if the user will always have enough time, complete information, uninterrupted attention, and a perfect understanding of the rule.
Real work rarely behaves that way. People switch tasks, receive incomplete handovers, answer messages while solving another problem, and make decisions with partial context.
If a process only works when everyone behaves perfectly, the process is fragile by design.
The strongest process is not the one that demands perfect attention. It is the one that remains understandable when attention is imperfect.Working principle
Do not make memory carry the system
Experienced people develop shortcuts, mental models, and useful intuition. That knowledge is valuable, but it becomes a risk when the system quietly depends on someone remembering the right thing at the right moment.
Checklists, visible ownership, default values, clear status language, structured handovers, and useful prompts are not signs that people are incapable. They are ways of protecting attention for the parts of the work that genuinely need judgment.
Design principle
Reduce cognitive load before adding another rule. A clearer interface, a better default, or a visible ownership cue can prevent more errors than another paragraph of procedure.
Make the safe path the easy path
Rules are strongest when correct behavior requires less effort than incorrect behavior. If the official method is slow, confusing, or hidden, people will naturally create a faster path.
Sometimes that workaround is clever. Sometimes it creates risk. Either way, it is feedback about friction in the designed process.
Design for recovery, not only prevention
No system eliminates every mistake. A resilient system makes errors easier to detect, limits their impact, preserves history, and provides a clear way to recover.
This shifts the design question from 'How do we make sure nobody ever does this wrong?' to 'If something goes wrong, how quickly can we see it, understand it, and restore a safe state?'
Closing thought
Human-centered systems are not softer systems. They are more realistic systems.
When the design assumes ordinary human limitations, people can spend less energy fighting the process and more energy solving the problem the process exists to support.