I used to treat bad weeks as personal failure.
Now I treat them like production incidents: acknowledge impact, stabilize quickly, identify root causes, and change the system.
This post is the recovery protocol I use when judgment quality drops.
Symptoms I watch for
- everything feels urgent,
- shallow replies replace thoughtful decisions,
- I avoid hard tasks and over-index on chat,
- I end the day tired but unclear on what moved.
When these signals cluster, I stop pretending it is “just a busy week.”
24-hour recovery: stabilize
Goal: prevent further damage.
- Cancel non-critical commitments.
- Protect one 90-minute deep-work block.
- Write a single-page “state of system” note:
- what is actually broken,
- what is delayed,
- what can wait.
This restores control of attention.
72-hour recovery: diagnose
Goal: find repeatable failure patterns.
I ask three questions:
- Where did context switching explode?
- Which commitments were accepted without scope?
- Which decisions were postponed because I was mentally depleted?
Then I map causes into two buckets:
- structural (calendar design, unclear ownership, interruption policy),
- behavioral (people-pleasing yes, unclear boundaries, poor sleep discipline).
7-day recovery: redesign
Goal: make relapse less likely.
I make at least three concrete changes:
- response windows instead of all-day chat,
- explicit escalation criteria,
- weekly review of “decisions made vs decisions deferred.”
Small operational changes outperform motivational promises.
What changed for me
The point is not to eliminate hard weeks.
The point is to recover faster, with less self-damage, and with better learning each cycle.
A bad week is data.
If I can read it well, next week gets cheaper.