Have Your Systems Become More Complex Than They Need to Be?

Most systems don’t become inefficient because they break.

They become inefficient because they grow.

A new step gets added.
A new layer is introduced.
A new process is created to improve something that once worked.

And over time, what started as a functional system becomes a complex one.

Not intentionally.

But gradually.

Research in organizational design shows that many businesses struggle not because of lack of strategy—but because of unnecessary complexity and poorly aligned systems.

And once that complexity sets in, performance begins to slow—not dramatically, but consistently.

The question is no longer:
“Is this system working?”

The question becomes:
“Is this system built the right way?”

Key Takeaways

• Most inefficiencies are caused by accumulated complexity—not broken systems

• Not all complexity is valuable—much of it creates friction

• Systems must align with behavior, not fight against it

• Leaders must evaluate how work actually flows—not how it was designed

• Simplification is a leadership discipline—not a one-time event

How Complexity Quietly Takes Over

No leader sets out to create a complicated business.

But complexity builds in predictable ways:

• Growth introduces new roles

• Problems introduce new processes

• Exceptions introduce new steps

Each addition makes sense in isolation.

But systems are not experienced in isolation.

They are experienced as a whole.

And over time, that whole becomes heavier.

The Difference Between Necessary and Unnecessary Complexity

From an organizational design perspective, there are two types of complexity:

1. Necessary Complexity

• Adds value

• Supports growth

• Enhances capability

2. Unnecessary Complexity

• Exists due to layers, silos, or outdated decisions

• Creates friction without adding value

• Slows execution

High-performing organizations don’t eliminate complexity.

They manage it intentionally.

Why Most Systems Don’t Perform as Expected

One of the most important insights from modern organizational design:

Systems fail when they don’t align with human behavior.

In other words:

If a process requires people to:

• Work around it

• Ignore parts of it

• Or constantly adjust it

Then the issue is not execution.

It’s design.

Because well-designed systems:

• Make the right behavior easier

• Reduce the need for oversight

• Support clarity and flow

Where Complexity Hides in Business Systems

1. Layers That Don’t Add Value

Extra roles or approvals that slow decisions without improving outcomes

2. Processes Built on Exceptions

Systems designed around rare scenarios instead of everyday needs

3. Disconnected Workflows

Departments or teams operating in silos instead of coordinated flow

4. Overdefined Roles

Too many boundaries, not enough collaboration

The Hanlon Renewal Audit™

To evaluate systems effectively, we use a four-part filter:

Eliminate → Simplify → Strengthen → Protect

1. Eliminate

What no longer needs to exist?

2. Simplify

What can be made easier, faster, or clearer?

3. Strengthen

What is working and should be reinforced?

4. Protect

What must remain to maintain performance and consistency?

This is not about tearing systems down.

It’s about refining them intentionally.

Why Leaders Struggle with Simplification

Simplifying systems sounds straightforward.

But it’s difficult because:

• Existing systems feel familiar

• Teams adapt to complexity over time

• Removing steps can feel risky

So instead of simplifying…

Leaders maintain.

And maintenance allows complexity to grow.

From Activity to Flow

Many organizations measure activity.

But performance is driven by flow.

• How smoothly work moves

• How quickly decisions are made

• How clearly responsibilities are defined

When systems are complex:

➡️ Flow is disrupted

When systems are refined:

➡️ Flow improves naturally

The Leadership Responsibility

Leaders are not just responsible for outcomes.

They are responsible for:

➡️ The systems that create those outcomes

And those systems must be:

• Clear

• Connected

• Intentional

Because complexity does not correct itself.

It compounds.

Final Thoughts

Most systems don’t fail because they are poorly built.

They fail because they are never refined.

Over time, complexity accumulates.

Layers build.
Processes expand.
Flow slows.

And eventually, the system that once supported performance begins to limit it.

The opportunity is not to rebuild everything.

It’s to step back…

…and ask:

What no longer needs to be this complicated?

Because the strongest systems are not the most detailed.

They are the most intentional.