Recurring errors with the same root cause need structural…
When an error recurs with the same root cause across multiple independent instances, apply structural fixes (process changes, environmental redesign, automated checks) rather than effort-based resolutions (increased attention, more discipline, trying harder).
When This Fires
- When the same error recurs 3+ times with the same identifiable root cause
- When "we'll be more careful" has been the response to an error type more than once
- When post-mortems keep identifying the same contributing factors
- Complements When behavior contradicts values, investigate the reward… (investigate reward structure, not willpower) with the error-correction application
Common Failure Mode
Treating structural problems as discipline problems: "The team keeps missing deadlines → they need to manage their time better." If deadlines are consistently missed by multiple people, the system produces unrealistic deadlines, unclear priorities, or insufficient resources. No amount of individual time management fixes a structural estimation problem.
The Protocol
(1) When an error recurs, check: is the root cause the same across instances? If yes → it's structural. (2) Identify the system conditions that make the error easy: what about the process, environment, or tools allows this error to occur? (3) Design a structural fix that addresses the condition, not the behavior: Process change: add a step that prevents the error (checklist item, verification gate). Environmental redesign: make the error physically harder (separate confusable items, remove dangerous defaults). Automated check: add a system that catches the error before it produces consequences. (4) After implementing the structural fix, verify: does the error still recur? If yes → the structural fix didn't address the actual root cause. Diagnose again. If no → the system now prevents the error regardless of individual effort levels.