Ideas The diagnosis

The Fallacy of One

One platform. One suite. One partner. One “solution.” The relief in the room is the tell.

In 30 seconds

  • Buying one thing simplifies the paperwork, not the work.
  • The interfaces never disappear. A monolith moves them inside — harder to see, harder to fix, and billed by the day.
  • You cannot correct the Fallacy of One with a bigger, better One.

The warm air of a single number

There is a moment in almost every large IT decision when a tired room falls in love with a single number. Not 1:200. The number is one.

Someone says, ”We just need one system,” and you can feel the relief move around the table like warm air. The fighting stops. The complexity everyone has carried for years suddenly has somewhere to go.

That relief is the tell. It is the sound a hostage makes when they stop fighting for what they need and start defending the structure that constrains them.

Why it is so comforting

Faced with a hard question — how do we manage the real diversity of our businesses? — the exhausted brain quietly swaps in an easier one: who is the one strategic partner we can buy from? Three survival-grade biases do the rest:

  • The comfort of monoculture. One kind of system is restful in a way a fleet of specialized applications never is.
  • The illusion of control. If everything lives inside one fortress, it feels transparent from the boardroom.
  • Risk aversion dressed as strategy. Nobody gets fired for buying the industry giant. ”At least we’ll have one throat to choke” optimizes for the post-mortem, not the living business.

What actually happens

Conway’s Law says organizations build systems that mirror their communication structures. Force one rigid monolith onto a maze of silos and the body rejects the transplant. Teams don’t revolt — they quietly return to their spreadsheets. The complexity didn’t disappear. It moved underground.

And the Fallacy of One keeps changing costume: the eleventh committee created to govern the first ten, the vendor offering to host your company’s brain for you. Once you see it, you see it everywhere.

The way out

Not a bigger, better One. Untangle the complexity, own the seams between systems, and stop paying outsiders to tell you what your own company does. No vendor has your intent in stock.

The real move is to change how the organization knows itself — which is where the Organizational Brain comes in.

“Forty-three ERP instances is not a failure to consolidate. It is twenty years of successful consolidations.”

— Corporate Stockholm Syndrome