A leadership team I sat with had spent two years convinced their platform was the problem.

The platform was old. The platform was slow. The platform required workarounds. The roadmap to replace it had been drawn up and redrawn. The case for replacement was internally accepted as obvious.

When we looked at what was actually happening, the platform was responsible for maybe thirty percent of the drag the leadership team was attributing to it. The other seventy percent was the escalation behavior around it.

What I mean by escalation behavior

When the platform produced an unexpected result, no one on the front line was allowed to make the call about what to do. The issue got passed up. The person above also could not make the call, because they had not been trained on what the platform was doing under the hood. So they passed it sideways to engineering. Engineering was already busy, and the issue waited.

While the issue waited, the customer waited. While the customer waited, the front-line person learned to anticipate the escalation and route the work around the platform entirely, by hand, using a spreadsheet.

After a year of that, the spreadsheet was the system. The platform was just where things got entered after the fact.

What replacing the platform would have done

It would have replaced the thirty percent.

The seventy percent (the escalation behavior, the absence of front-line decision rights, the gap between what the platform did and what humans on top of it understood) would have moved over to the new platform unchanged.

The replacement would have been considered a partial success, because the new platform was newer and prettier and the leadership team had committed to it publicly. After eighteen months, the same workarounds would have started accreting again, and the same shadow spreadsheets would have started growing.

How to tell the difference

The diagnostic is simple. Ask the people closest to the system: “If I gave you the authority to fix this without changing the technology, what would you change?”

If they have a clear answer, the platform is not the bottleneck. The escalation behavior is.

If they say “I would need a new system,” ask them what specifically the new system would let them do that they cannot do today. If the answer is “it would be faster” or “it would be cleaner,” that is a hint, not a diagnosis.

A platform replacement is a strong solution to a specific class of problem. It is a weak solution, sometimes a counter-productive one, to organizational behavior.

What this is really about

Technology investments often get used to avoid harder conversations about authority and accountability. Buying a platform is concrete and budgetable. Reorganizing decision rights is neither.

So organizations buy the platform. Twice. Three times. And the same patterns persist.

When does technology create capacity, and when does it create drag? Often the answer is that the technology is doing what technology does. The drag is being produced by the behavior around it.