Somewhere along the line, a perfectly straightforward piece of work has acquired a rather fussy and unnecessary entourage. Instead of a direct line from idea to execution, we find ourselves trying to negotiate a set of bloated rules and checkpoints. Individually, each check and balance seems reasonable enough, yet their collective weight tends to turn a simple act of progress into a grueling test of endurance.

This isn’t a failure of any specific department, but rather a profoundly human response to the creeping complexity of modern work. As our projects grow more intricate, our natural instinct is to smother them with structure by adding layers and defining stages, or perhaps by introducing said checkpoints as a sort of architectural safety net. We tell ourselves we are preventing things from slipping through the cracks, but given enough time, the cracks simply relocate. They move from the work itself to the spaces “in-between”.

From a leadership perspective, this is where a subtle but pervasive drift begins. It isn’t a dramatic collapse that sets off alarm bells, but rather a gradual thickening of the air. Decisions take a little longer to travel from one point to the next while ownership becomes a misty, ambiguous thing. Eventually, people find they are spending more energy navigating the system than they are doing the very thing the system was designed to support. If your setup makes it more comfortable to wait than to move, you have inadvertently built friction into the heart of the business.

It’s seldom an intentional act of sabotage. These hurdles usually grow out of perfectly sensible conversations where someone asks (quite rightly) how we might ensure a past mistake isn’t repeated. A step is added here and an approval point is introduced there, until the path to delivery turns into a series of persistent hurdles. The trouble is that once structure is added, it has a habit of justifying its own existence. Removing a redundant step can feel like losing something vital, even when that step provides nothing more than a fleeting sense of reassurance.

In the meantime, the real work often carries on through side conversations and back channels simply to maintain momentum. Most important decisions are still being made in those hurried, informal moments, such as a quick message to fix a direction or a bit of sharp judgment applied under pressure. The formal system sits alongside this, diligently maintained, yet often entirely divorced from where the actual movement happens.

This is why so many teams eventually mistake the presence of process for the presence of insight. They assume that more scaffolding leads to more lucidity, but the reality is often the opposite. An overabundance of steps usually suggests that ownership is a muddle, just as a mountain of documentation often reveals that a clear decision hasn’t actually been made.

A flowchart, after all, is just a very polite work of fiction. It assumes everyone behaves as instructed and that every handover is seamless, whereas the truth is that people must constantly interpret and adapt just to get the job finished. While there is a certain comfort in building tangible systems that can be presented and polished, the harder, more valuable work lies in being clear about who is in charge and having the nerve to say “no” to unnecessary fluff.

The most effective teams are rarely the most elaborate. They excel by being decisive about ownership. They keep their priorities short enough to remember without a dashboard, and they use their tools with boring consistency (and only the bits of the tool they really need). When a system begins to require its own care and feeding, separate from the work itself, the balance has tipped too far in the wrong direction.

The real discipline lies in subtraction, which means pruning the handoffs and making it obvious what “good” looks like without needing a manual. The goal is never to build an impressive system, but to get good work out of the door with as little friction as possible.