When pipeline maintenance costs more than the pipeline…
When information pipeline maintenance consumes more cognitive resources than the pipeline saves, the system economics have inverted and simplification is required, not optimization.
When This Fires
- When your information system feels like a chore rather than a tool
- When system maintenance time exceeds the time saved by the system
- When you're maintaining features you rarely use "because they might be useful someday"
- Complements Measure pipeline health by processing days in the last 30… (processing days metric) as the economic health check alongside the execution health check
Common Failure Mode
Optimization reflex: "The system is expensive to maintain, so I need to optimize the maintenance workflow." This preserves the over-engineered system and just makes the overhead more bearable. The correct question isn't "How can I maintain this more efficiently?" but "What would I lose if I removed this entirely?" If the answer is "not much," remove it.
The Protocol
(1) Estimate your weekly maintenance cost: how many hours do you spend on system upkeep (organizing, tagging, reviewing, migrating, troubleshooting)? (2) Estimate your weekly value produced: how many hours has the system saved you through faster retrieval, better decisions, avoided rework? (3) If maintenance > value → the economics are inverted. Don't optimize. Simplify. (4) Simplification targets: remove features you maintain but rarely use. Eliminate categories that require maintenance but don't aid retrieval. Reduce the number of tools to the minimum that serves your actual workflow. (5) After simplifying, re-measure. The goal is maintenance cost < 30% of value produced, giving a comfortable margin where the system clearly earns its keep.