Simplicity Is a Leadership Choice

No organization sets out to become unwieldy.

It happens gradually. A new process is added to reduce risk. A new approval to improve consistency. A reporting requirement to increase visibility. A handoff because one team is not quite comfortable letting go. Another exception because “this case is different.”

Each step makes sense in the moment. Then one day you look up and realize the organization is spending more energy navigating itself than serving its purpose.

That is when complexity becomes most dangerous, not because of what it costs to operate, but because of what it costs to change.

There is a special kind of trap that comes from inherited complexity. A process exists because it has always existed - the people who are charged with maintaining the business process might not understand why it’s there at all. A control remains because no one wants to be the one to remove it - we haven’t incentivized the change so it remains. The structure survives because it is easier to work around it than rethink it. Eventually, people stop asking why.

Good leaders have to ask why, but asking is not enough. The instinct most leaders have when facing complexity is to streamline: cut steps, tighten the process, reduce overhead. That feels like simplification. It usually is not.

Removing steps from a process that is poorly understood risks making things worse. People (and AI) need enough structure to do the work well. Strip too much away and people will fill the gaps themselves. Those gaps get filled with workarounds and informal knowledge that never gets documented, which is how inherited complexity starts in the first place. Worse still, automation may fail at scale - with unpredictable results.

Designing for simplicity is different. It means deliberately building processes that are genuinely easy for people to understand and execute. It means asking not just whether a step can be removed, but whether the overall design actually makes the work easier. It means treating the people closest to the work as co-designers, not recipients.

This distinction is where I’ve seen some organizations get it wrong. Well-meaning leaders might overestimate how simple their processes really are (or need to be), and they slash and burn complexity away. What they are left with may look cleaner, but it often works worse. The people doing the work feel that immediately. And the gaps that follow are exactly where complexity starts to build again.

Simplicity is a prerequisite for modernization. And AI will not fix your processes.

Organizations are investing heavily in intelligent automation and agentic AI. But a pattern is emerging: we are buying orchestration technology before we have a coherent understanding of the work we are trying to orchestrate, and why. That is not a technology problem. It is a process clarity problem. If your processes are inconsistent, poorly defined, and full of exceptions nobody can explain, automating them does not make them better. It makes them faster, more expensive, and harder to fix. Nobody wants that.

The sequence matters: understand the process first, then decide what to automate. Organizations that skip that step are not accelerating transformation. They are accelerating the wrong thing.

Complexity also raises the cost of every future change. Processes can be redesigned on paper quickly. People cannot absorb change that fast, especially when the environment is already overloaded with unclear priorities and competing controls. The more dependencies you carry, the harder it is to move.

That is leadership work. Complexity has a way of protecting itself if you let it. Before asking technology to operate your systems, make sure your systems actually make sense. Simplicity is not the opposite of sophistication. In many cases, it is the evidence of it.

The best organizations are not the ones with the most layers, the most approvals, or the most elaborate process maps. They are the ones that know what matters, design around it, and make it easier for people to do good work.

That kind of simplicity does not happen by accident. It is a leadership choice.