Simplification Is Costly

Simplification is about elimination.

Cutting clutter. Reducing unnecessary options. Removing unnecessary decisions.

It is about being strategic.

We tend to talk about simplification as if it were a tidy-up. Clear the desk, trim the menu, shorten the process, and everything runs better. Who could argue with that? Everyone wants things to be simpler. Very few organisations actually become simpler.

There is a reason for that gap. Simplification is costly.

What elimination really means

To simplify, you have to make choices. And every real choice involves letting something go.

That is the part we prefer to skip. Eliminating an option means some people will no longer have it. Removing a product line means losing the revenue it brings, however small. Retiring a service means some customers will walk away. Narrowing focus means closing doors that might have led somewhere.

We make these choices knowing that we may lose revenue, customers and options. Simplification asks us to accept that loss before we see the benefit.

That is why it is strategic. Strategy is not only deciding what to do. It is deciding what not to do, and living with the consequences.

Necessary, but not easy

As much as simplification is necessary for a product, a service or a business, it is not easy business.

Complexity rarely arrives all at once. It accumulates. A special request here. An exception there. A report built for a manager who left years ago. A process step added after one bad incident and never removed. Each addition made sense at the time. Each had someone who asked for it, and someone who still depends on it.

So when we try to remove it, we are not removing clutter in the abstract. We are removing something that someone values.

The hard and harsh decisions

Simplification requires some hard and harsh decisions.

I see this most clearly in ERP programs. An organisation moves to a new system with the promise of standardising its processes. Then the requests begin. This team needs its own approval path. That department has always coded things differently. A particular charge has always been handled in a unique way, and it must be preserved.

Each request is reasonable on its own. Together, they rebuild the old complexity inside the new system, at greater cost.

The program that actually simplifies is the one where someone says no. Not to everything, but to enough. This approval path goes. That coding exception is retired. That report is no longer produced. These are not comfortable conversations. Some of them are harsh. People feel their way of working has been dismissed.

But without them, the new system is just the old organisation with a new login screen.

The cost nobody budgets for

Simplification requires cost.

Not just money. The cost of dealing with change, as people let go of familiar ways of working. The cost of dealing with politics, because every piece of complexity has an owner, and every owner has influence. And the cost of dealing with unknowns, because once something is removed, we cannot always predict what else depended on it.

These costs are real, and they land early. The benefits arrive later. That timing is exactly why so many simplification efforts stall. The pain is visible now. The payoff is a promise.

So complexity stays. Not because anyone chose it, but because nobody was willing to pay to remove it.

A hard path, and the right one

It is a hard path to walk, but at the same time the right path.

Hard, because it asks us to give something up before we see what we gain. Right, because the alternative is to keep carrying weight that slows every decision, every change and every person who has to work around it.

Complexity has a cost too. It is simply paid quietly, every day, by everyone.

Simplification asks us to pay once, openly and on purpose.

What is the one thing in your organisation that everyone agrees should go, but nobody is willing to pay to remove?

Are you ready for it?