Escalate unresolved patterns from weekly to monthly review after 2+ consecutive appearances — persistent problems need a higher-altitude intervention

Why This Is a Rule

Weekly reviews (Open weekly planning by reviewing plan vs. actuals — identify the single biggest gap without judgment, then make one structural fix) are designed to catch tactical problems: this week's plan-vs-actual gaps, near-term adjustments, immediate obstacles. But some problems are structural — they recur weekly because they're caused by something at a level the weekly review can't see or fix. "I keep running out of deep work time" appearing for three consecutive weeks isn't a weekly scheduling problem; it's a structural problem with how your calendar, commitments, or environment are designed.

Attempting to solve structural problems at the weekly tactical level produces whack-a-mole: you make a weekly adjustment, the symptom temporarily improves, and it returns the following week because the structural cause was never addressed. The weekly fix is like treating a fever without diagnosing the infection — it addresses the symptom, not the disease.

The two-week escalation threshold detects when a problem has exceeded the weekly level's problem-solving capacity. One occurrence is a data point. Two consecutive occurrences is a pattern that the weekly level's interventions haven't resolved — time to escalate to the monthly review, which has the broader perspective and longer time horizon to address structural causes.

When This Fires

• During weekly reviews when noting the same problem for the second (or third) consecutive week
• When weekly adjustments aren't producing lasting improvement
• When a problem feels chronic rather than acute
• Complements Open weekly planning by reviewing plan vs. actuals — identify the single biggest gap without judgment, then make one structural fix (weekly review) and Three review altitudes: weekly (execution), monthly (portfolio), quarterly (strategic) — each catches different kinds of drift (multi-altitude review) with the escalation mechanism between altitudes

Common Failure Mode

Infinite weekly re-solving: the same issue appears in every weekly review, receives a new weekly tactical fix, and returns the following week. After 8 weeks of "I'll try to schedule more deep work time," the pattern remains because the structural cause (too many meetings, no calendar protection policy, unclear priorities) was never addressed at the monthly level.

The Protocol

(1) During weekly review, note each recurring issue and count consecutive weeks it has appeared. (2) When an issue reaches 2+ consecutive weeks without resolution → mark it for monthly review escalation. Stop attempting weekly fixes. (3) At the monthly review, examine the escalated issue with structural questions: "What system, environment, or commitment is producing this pattern? What structural change would eliminate it?" (4) 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 a default, restructure a time block, renegotiate a commitment, modify the environment. Weekly-level adjustments are insufficient by definition (they've already failed). (5) After implementing the structural fix, monitor for 4 weeks at the weekly level. If the pattern returns, escalate again to quarterly review for even deeper structural examination.