Track operational debt explicitly — what was deferred…
Maintain an operational debt register that records what was deferred, when, why, and the estimated cost of continued deferral, reviewing it during weekly rhythms to distinguish strategic from accidental debt.
When This Fires
- When you consciously defer a maintenance task, documentation update, or system cleanup
- During weekly reviews when assessing operational health
- After discovering unexpected problems caused by deferred maintenance
- When prioritizing work and needing to balance new features against debt repayment
Common Failure Mode
Deferring without recording — "I'll get to it later" without writing it down. The deferral enters the invisible debt pool, compounds interest silently, and resurfaces as an emergency. The register's primary value is making deferrals conscious and trackable, not solving them immediately.
The Protocol
When deferring any maintenance or operational task: (1) Add it to the debt register with four fields: what, when, why (strategic/accidental), estimated recovery cost if deferred another week/month. (2) During weekly review: scan the register. For each item, update the recovery cost estimate — has it grown? (3) Items where recovery cost has crossed 3x immediate cost (see When deferred maintenance costs 3x more to fix later…) get promoted to this week's priority. (4) Items deferred strategically with low interest can remain. Items deferred accidentally should be scheduled for the next available capacity slot.