Recurring errors with the same root cause need structural fixes, not more effort — process changes beat discipline every time

Why This Is a Rule

A single error might be bad luck, inattention, or an unusual circumstance. A recurring error with the same root cause is a system failure. If the same mistake happens three times for the same reason, the cause isn't individual carelessness — it's a process that makes the error easy and prevention hard. "Try harder" addresses the individual's effort on the next instance while leaving the system that produced the error entirely unchanged.

W. Edwards Deming's insight applies: 94% of failures are caused by the system, not the individual. A nurse who gives the wrong medication three times isn't careless three times — she's working in a system where the right and wrong medications look identical, are stored adjacent, and have confusingly similar names. The structural fix (color-code, separate storage, barcode scanning) eliminates the error category. The effort fix ("pay more attention") reduces the next instance's probability slightly while leaving the error-prone system intact.

Structural fixes work because they change the environment to make the error impossible or the correct action default. Effort-based fixes work only as long as the individual maintains heightened attention — and attention is a depletable resource (Design triggers for your worst cognitive day — if they only work when you're sharp, they fail when you need them most) that fails under exactly the conditions where errors are most costly.

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 structure — not your willpower deficit (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.