Three weeks of the same failure = system design problem…

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…'s two-week escalation hasn't resolved the issue
• Complements Escalate unresolved patterns from weekly to monthly review… (escalation threshold) and Design weekly adjustments as structural changes… (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…): 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.