Calculate optimization breakeven time — if payback exceeds…
When evaluating whether to optimize an existing system, calculate breakeven time by dividing optimization effort by weekly time savings—if payback exceeds the system's expected remaining lifespan, redirect effort to the actual constraint instead.
When This Fires
- Before any optimization project — calculate breakeven first, then decide
- When tempted to automate, streamline, or refactor a process
- When someone proposes a "quick improvement" to a system — check the math
- During quarterly system reviews when prioritizing optimization efforts
Common Failure Mode
Optimizing systems that are about to be replaced: spending days perfecting a workflow that will be superseded by a tool migration next quarter, or automating a report that will be handled by a new platform next month. The optimization work is lost when the system changes, and the hours can never be recovered. Check remaining lifespan before investing in optimization.
The Protocol
(1) Before optimizing, estimate three numbers: Optimization cost: how many hours will the improvement take? Weekly savings: how many hours per week will the improvement save? System lifespan: how many weeks until this system is likely to be replaced, restructured, or rendered obsolete? (2) Calculate breakeven: cost ÷ weekly savings = weeks to breakeven. (3) If breakeven < system lifespan → the optimization produces net positive returns. Proceed. (4) If breakeven > system lifespan → the optimization is a net loss. Redirect the effort to the actual constraint (When performance is stable with no bottleneck, stop…) or to a system with a longer remaining life. (5) For borderline cases, add a safety margin: double the estimated optimization cost (projects always take longer than estimated) and halve the estimated savings (benefits always appear more dramatic in planning). If it still breaks even → proceed.