Three weeks of the same failure = system design problem, not execution problem — shift from trying harder to structural redesign

Why This Is a Rule

One week of failure is an event. Two weeks is concerning. Three weeks is a system design verdict: the system (your environment, schedule, defaults, tools, commitments) cannot produce the desired behavior. No amount of willpower, intention, or self-criticism will change this because the constraint isn't motivation — it's structure.

This is Design weekly adjustments as structural changes (move blocks, change environments, create defaults) — persistent patterns are system problems, not motivation problems's structural intervention principle with a specific threshold. After three weeks of the same failure, the diagnosis shifts definitively from "I need to try harder" (execution framing) to "The system needs to change" (design framing). The three-week threshold provides enough data to distinguish a genuine structural problem from a temporary circumstantial glitch while preventing the indefinite "I'll do better next week" deferral that keeps people attempting execution solutions to design problems.

Deming's distinction between common-cause variation (inherent to the system) and special-cause variation (specific identifiable events) applies here. A failure that recurs for three weeks without any specific cause is common-cause variation — it's what the system reliably produces. Changing the output requires changing the system, not exhorting the operators.

When This Fires

• During weekly reviews when the same gap has appeared for the third consecutive week
• When "I'll try harder next week" has become the default response to recurring failures
• When Escalate unresolved patterns from weekly to monthly review after 2+ consecutive appearances — persistent problems need a higher-altitude intervention's two-week escalation hasn't resolved the issue
• Complements Escalate unresolved patterns from weekly to monthly review after 2+ consecutive appearances — persistent problems need a higher-altitude intervention (escalation threshold) and Design weekly adjustments as structural changes (move blocks, change environments, create defaults) — persistent patterns are system problems, not motivation problems (structural adjustments) with the definitive diagnosis that ends execution-level problem-solving

Common Failure Mode

The willpower escalation: week 1 "I'll try harder." Week 2 "I'll try MUCH harder." Week 3 "Why can't I do this? Something must be wrong with me." Each week increases the self-blame without changing anything structural. The system continues producing the same result because the system hasn't changed.

The Protocol

(1) During weekly review, if the same failure has occurred for 3 consecutive weeks: STOP treating it as an execution problem. It is now officially a design problem. (2) Ask the design question: "What structural feature of my system produces this failure? What would need to change in my environment, schedule, defaults, or commitments for this behavior to become easy rather than hard?" (3) Design a structural intervention (Design weekly adjustments as structural changes (move blocks, change environments, create defaults) — persistent patterns are system problems, not motivation problems): change the environment, change the schedule, change the default, change the commitment. The intervention should work even on a day with zero extra willpower. (4) Implement the structural change before the next week begins. (5) Monitor for 3 weeks: does the new system produce the desired behavior? If yes, the structural diagnosis was correct. If no, the structural intervention targeted the wrong constraint — identify the actual binding constraint and redesign again.