The Polite Failure of Process

It is an enduring myth of professional life that systems are inherently designed to work. That if something is in place, a form, a policy, a meeting rhythm, it must serve a purpose beyond simple self-preservation.

However, over time, and across various environments, I have come to realise that some of the most obstructive processes survive not in spite of their inefficiency but because of it. They create just enough structure to appear functional, just enough movement to be called a system, and just enough confusion to prevent anyone from being clearly accountable.

These are the processes that no one quite owns, yet everyone is expected to follow. They are often the ones that frustrate the most competent people, while quietly protecting those who would rather not think too hard.

You will hear the same phrases used to defend them:

"That is how we have always done it."

"It is not ideal, but it works for now."

"We are reviewing it soon."

Except the review rarely comes. Or if it does, it is purely cosmetic. A new name, a slightly altered workflow, and a fresh PowerPoint presentation that explains the same inefficiencies using improved fonts.

In some cases, the process is deliberately convoluted. Complexity, after all, is a sound shield. If no one fully understands it, then no one can be blamed when it fails. This creates a culture not of excellence or even adequacy but of polite survival, where the most important thing is that everything appears to be under control.

People in these systems learn quickly. They learn to route around inefficiencies rather than confront them. They create unofficial shortcuts, informal go-betweens, and whole categories of internal workarounds that are never documented but remain essential to keeping the lights on.

It is not always malicious. Sometimes these systems were built with better intentions, suited to different conditions. But few institutions are good at dismantling what they no longer need. Instead, these systems accrete like sediment until even the simplest task requires a detour through five meetings, three dashboards, and a compliance form that no one reads but everyone signs.

Meanwhile, the people most invested in doing things properly are the ones most worn down by them. They spend time and energy trying to make the system work as intended, while others learn to navigate the dysfunction with strategic ignorance. Over time, the wrong behaviour is rewarded, not because anyone says so directly, but because it is easier.

And that is the quiet danger. Not catastrophic failure, but slow erosion. Not scandal, but fatigue. Eventually, good people stop asking why things are the way they are. Or they leave.

Whenever I enter a new organisation, I find myself less interested in its stated values or brand language and more interested in its processes. That is where the real character resides, not in what people claim to believe, but in what they are required to do each day without complaint.

If a process is working, it should make good work easier. If it does not, it is not a process. It is a performance.