Complexity Debt
Complexity Debt (n.) The hidden cost of automation layers that nobody can fully explain or safely modify.
Explanation
Each automation adds a layer. Each layer interacts with others. Eventually the system is so complex that changing one rule risks breaking five others. Nobody touches it. It becomes untouchable legacy.
Operational Example
A pricing engine has 400 rules built over 5 years by 12 different people. Nobody knows which rules conflict. Changing one price tier requires a two-week impact analysis.
Why It Matters
Complexity debt slows innovation. Teams cannot move fast because they cannot predict what breaks.
What Most Teams Get Wrong
They add rules without removing old ones. They never simplify.
What Strong Teams Do Differently
Enforce a rule budget. For every new rule added, one must be retired. Document dependencies explicitly.