Every Tool in a Bloated Software Stack Passed a Business Case

← Back · ACT I · Chapter 6: Tech Bloat as Governance Failure

Walk through any enterprise software stack and you will find the same things: three tools answering one question, modules that were licensed and never opened, renewals that go through because nobody is quite sure what breaks if they do not. The usual answer is a rationalization project. Inventory everything, cut what is unused, consolidate the rest.

Here is what that project cannot fix. Every one of those tools passed a business case and was approved, budgeted, and signed. The step that was missing came before any of that: nobody wrote down what the purchase was supposed to do, what evidence would show it was doing it, and when someone would check.

Each of those business cases had an author, and the profession that produces them is the subject of The Business Case for Your Purchase Was Written Without You.

That is the difference between governing a budget and governing value. Approval settles whether we can spend the money and says nothing about what the money has to do. When buying runs on approval alone, the stack grows by itself, and once the second question is asked too, every tool has to earn its place, one purchase at a time.

Seen this way, a rationalization project is the definitional question asked years too late. What do we still need is the same question as what will this do and how will we know, except one gets asked before the money moves and the other after it is gone.

The cost also goes beyond licenses. Overlapping systems mean integration work, maintenance, and a quieter problem: each redundant tool produces its own version of the numbers, and nobody audits the numbers you buy. A bloated stack costs more, and it also makes the organization harder to know.

So before the next renewal clears, it is worth asking one question: what definition was this bought against? If nobody can produce one, the renewal carries forward a decision that was never actually made, and the fix starts before the money moves, with the buyer setting the definition.

Keep reading: ACT I · Chapter 6: Tech Bloat as Governance Failure