Skip to content

Failure & Recovery

What to Do When the System Breaks

Purpose

This playbook exists to answer one question:

What should I do when things fall apart?

Because they will.

This document assumes: missed work, lost weeks, low motivation, and unexpected life events.

Failure is expected. Recovery is designed.

flowchart LR
    subgraph recovery ["RECOVERY PROTOCOL"]
        S1["1. STOP<br/>the bleeding"]
        S2["2. SHRINK<br/>surface area"]
        S3["3. DIAGNOSE<br/>by layer"]
        S4["4. CHOOSE<br/>recovery mode"]
        S5["5. RESTART<br/>small"]
    end

    S1 --> S2 --> S3 --> S4 --> S5

    style S1 fill:#ef5350,stroke:#c62828,color:#fff
    style S2 fill:#ff7043,stroke:#e64a19,color:#fff
    style S3 fill:#ffa726,stroke:#f57c00,color:#fff
    style S4 fill:#66bb6a,stroke:#43a047,color:#fff
    style S5 fill:#42a5f5,stroke:#1e88e5,color:#fff
    style recovery fill:#fafafa,stroke:#bdbdbd

First Principle

Critical Rule

Do not change the system while dysregulated.

Most destructive changes happen while tired, frustrated, or ashamed.

Stabilize first. Then diagnose.

Step 1 — Stop the Bleeding

If overwhelmed:

  1. Ignore all goals
  2. Ignore all outcomes
  3. Ignore all projects
  4. Pick one tiny work unit
  5. Do it

Momentum before meaning.

Step 2 — Shrink the Surface Area

Delete or hide:

  • Overdue work units
  • Vague tasks
  • Aspirational commitments

The goal is relief, not completeness.

Step 3 — Diagnose by Layer

Ask:

  • Is direction unclear?
  • Is a goal misaligned?
  • Are outcomes too large?
  • Are work units too big?
  • Is the calendar dishonest?
  • Is feedback being interpreted as judgment?

Fix only the violated layer.

Step 4 — Choose Recovery Mode

Recovery modes:

flowchart TB
    subgraph modes ["RECOVERY MODES"]
        M1["<b>MINIMUM VIABLE</b><br/>One work unit per day<br/>Nothing more"]
        M2["<b>MAINTENANCE ONLY</b><br/>Keep existing commitments<br/>Add nothing new"]
        M3["<b>REST & OBSERVE</b><br/>No execution<br/>Just watch and recover"]
    end

    M1 --- M2 --- M3

    style M1 fill:#a5d6a7,stroke:#66bb6a,color:#000
    style M2 fill:#fff59d,stroke:#ffee58,color:#000
    style M3 fill:#ef9a9a,stroke:#ef5350,color:#000
    style modes fill:#fafafa,stroke:#bdbdbd
  • Minimum viable execution — One work unit per day, nothing more
  • Maintenance only — Keep existing commitments, add nothing new
  • Rest and observation — No execution, just watch and recover

Explicitly choose one.

Step 5 — Restart Small

The restart rule:

  • One outcome
  • One work unit
  • One day

No system rebuild. No fresh start fantasies.

What Not to Do

Never:

  • Rewrite all goals
  • Change tools impulsively
  • Add structure to solve exhaustion
  • Punish yourself with stricter rules

Signals You Are Recovered

  • Tasks feel neutral again
  • You can miss a day without spiraling
  • Planning feels optional, not urgent

Only then resume normal cadence.

Closing

A good system is not one that never breaks.

It is one that:

  • Breaks predictably
  • Recovers gently
  • Leaves no scars

This playbook exists so failure never becomes permanent.