Sustainable Systems
Systems that outlast my motivation.
How do I build systems that survive my exhaustion, distraction, and shifting focus?
In short: Discipline is unreliable. Systems, if designed well, run on autopilot. This module builds infrastructure that works even when I don't.
The Core Insight
Willpower is a finite resource that depletes under stress. A sustainable system does not require willpower to maintain – it requires friction to remove. This module builds the architecture of automatic execution.
The Practices
Each practice is a focused investigation. Click through to read the full protocol.
Create Distance
Increase friction for unwanted behaviors. Reduce friction for wanted ones. The 20‑second rule and environmental design.
Read practiceUse Compartments
Separate contexts into distinct containers. Physical spaces, user accounts, browser profiles, and time blocks. Each context gets its own compartment.
Read practiceBuild Redundancy
A single point of failure is a system waiting to break. Redundancies are not inefficiencies; they are resilience built in advance.
Read practiceMake It Legible
If the system cannot be read, it cannot be used. Documentation, naming conventions, and visible state reduce cognitive load.
Read practicePay the Maintenance Cost
Every system has an ongoing cost. Denying the cost does not eliminate it – it just delays it into a larger, more painful bill. Budget for maintenance.
Read practiceThe System That Runs Itself
Automation, delegation, and elimination. The goal is a system that requires only the minimum viable attention to keep running.
Read practiceThe Counterfeit
"I have built a beautiful system and called it progress." A system that is not used is not a system – it is performance. If the system is more complex than the problem it solves, it is a distraction.