Budget 30 min to 2 hours weekly for system maintenance…
Calculate maintenance budget for entire operational system (30 minutes to 2 hours weekly) as binding constraint; reject additional components when aggregate maintenance would exceed sustainable capacity.
When This Fires
- Adding a new tool, automation, habit, or tracking system to your operations
- When existing maintenance feels like it's consuming too much time
- During quarterly reviews of your operational system's complexity
- After a system collapse caused by unmaintained components
Common Failure Mode
Adding components without accounting for maintenance: "This new tool will save me 20 minutes a day!" But it requires 15 minutes of weekly maintenance (data cleanup, sync verification, configuration updates). If your maintenance budget is already at capacity, the tool creates a net deficit — maintenance grows while the budget doesn't.
The Protocol
(1) List every component of your operational system (tools, automations, recurring practices, documentation). (2) Estimate weekly maintenance time for each (most are 2-10 minutes). (3) Sum to get aggregate weekly maintenance. (4) Set budget: 30 min (minimal system) to 2 hours (complex system). (5) If aggregate exceeds budget → simplify: remove components until maintenance fits. (6) For every proposed addition: does adding its maintenance keep the total within budget? If no → reject or trade (remove something to make room).