I have become increasingly suspicious of complexity. Not because difficult problems are not real. Businesses are complicated. People are complicated. Technology is complicated. Leadership regularly requires us to make decisions without complete information.
But there is another kind of complexity that we create ourselves.
We take relatively simple ideas and make them unnecessarily complicated. We create processes around processes, add meetings to manage the meetings, invent terminology for things everyone already understands, and build elaborate scorecards when three numbers would probably tell us what we need to know.
Somewhere along the way, the complexity itself begins to feel like evidence that we are doing important work.
Sometimes complexity is necessary. Sometimes it is simply ego wearing business clothes.
Complexity Can Make Us Feel Important
There is something psychologically satisfying about being the person who understands something nobody else does. If a system requires your explanation, you become necessary. If a process is complicated enough that only you know how it works, you become valuable. If a presentation requires forty slides, three diagrams, and a glossary, the work certainly looks substantial.
That can become seductive.
We begin adding sophistication not because it improves the outcome, but because it improves our sense of importance.
Imagine spending two weeks analyzing a problem and returning to the room with a very simple conclusion: “We need to answer customers faster.”
That does not sound particularly impressive. So instead, we might create a “client responsiveness optimization framework,” establish multiple workstreams, create a dashboard, and schedule a monthly steering committee.
Now it feels like serious work.
But the underlying problem has not changed. We still need to answer customers faster.
Sometimes the hardest thing a leader can do is resist the temptation to make a simple truth sound more impressive than it is.
Simple Does Not Mean Easy
Simplicity is often misunderstood because we confuse “simple” with “easy.”
Exercise consistently. Simple, but not easy.
Spend less than you earn. Simple, but not easy.
Do what you said you would do. Simple, but not always easy.
Treat people well. Simple, but certainly not always easy.
Many of the most important principles in life and business are remarkably simple to explain and remarkably difficult to execute.
That may be one reason we are drawn to complexity. Complexity can become a sophisticated form of procrastination.
If the answer is complicated, we can keep studying it. We can schedule another meeting, redesign the process, purchase another tool, hire another consultant, or continue debating the terminology.
If the answer is simple, eventually someone has to do the work.
That is considerably less comfortable.
Understanding Produces Simplicity
There is a reason the best teachers can explain difficult subjects clearly: they understand them.
People who only partially understand something often hide behind terminology. Acronyms, frameworks, technical language, and complicated explanations can provide cover for incomplete understanding.
The person who truly understands the subject can usually say, “Here is what actually matters.”
That is a different kind of expertise.
An experienced engineer knows which ten variables do not matter. A great physician knows which symptoms deserve attention. An effective leader knows which three priorities actually matter this quarter. A good technician can explain a complicated technical problem to a customer without making the customer feel stupid.
Expertise is not demonstrated by showing people everything you know.
It is demonstrated by knowing what they need to know.
That is why simplicity is often a sign of mastery rather than a lack of sophistication.
Ego Loves Complexity
Ego struggles with simplicity because simplicity removes opportunities to display ourselves.
The smartest person in the room often feels a need to prove it. Instead of answering the question, we demonstrate our knowledge. Instead of solving the problem, we explain how difficult the problem is. Instead of making the process easier for everyone else, we build something that requires our continued involvement.
This happens in leadership as well.
Managers create unnecessary approval structures because decisions flowing through them reinforce their importance. Organizations build layers of reporting because leaders want visibility into everything. Teams create complicated procedures because someone wants to account for every possible exception.
Eventually the organization becomes slower, even though everyone involved can explain why each individual piece of complexity exists.
Ego rarely announces itself by saying, “I want everyone to think I am important.”
It sounds much more reasonable.
“We need better governance.”
“We need more visibility.”
“We should add another level of review.”
“We need to account for every scenario.”
Sometimes those things are true.
Sometimes they are sophisticated ways of saying, “I am uncomfortable letting this work without me.”
Every Exception Creates Complexity
One of the easiest ways to destroy simplicity is to continually design around exceptions.
We establish a good process. Then someone has a special circumstance, so we modify it. Another unusual situation appears, and we add another rule. A customer wants something slightly different, so we build another workaround.
Eventually the process becomes so complicated that nobody can remember how it works.
Then we blame people for not following it.
The problem may not be the people. The problem may be that we created a system only its designer could understand.
Good systems should handle the overwhelming majority of normal situations simply and clearly. Truly unusual circumstances can be handled as unusual circumstances.
Not every exception deserves a permanent rule.
Sometimes the best policy is simply: this is how we normally do it, and when something genuinely unusual happens, use good judgment.
That requires trust.
And trust is often much simpler than control.
Simple Organizations Move Faster
Every layer of complexity has a cost.
Another approval slows the decision. Another meeting consumes time. Another metric divides attention. Another tool requires training. Another handoff creates an opportunity for misunderstanding. Another policy requires someone to administer it.
Individually, each addition may appear reasonable. Collectively, they can make an organization almost incapable of moving.
This is one reason smaller organizations can sometimes outperform much larger competitors. They do not necessarily have more talent, better ideas, or greater resources. They simply have less distance between a problem and a decision.
Someone notices something. They talk to the right person. A decision gets made. The team acts.
As organizations grow, leaders often assume that maturity means adding structure. Sometimes it does. But maturity should not become bureaucracy.
The purpose of structure is to make execution easier, not to demonstrate that the organization has structure.
Start With the Outcome
One of the best defenses against unnecessary complexity is a very simple question:
What are we actually trying to accomplish?
Why do we have this meeting?
What decision is supposed to come out of it?
Why are we tracking this metric?
What behavior is it intended to encourage?
Why does this approval exist?
What risk is it actually reducing?
Who reads this report, and what do they do differently because of it?
Those questions can be uncomfortable because sometimes the answer is, “We have always done it this way.”
Or worse: “I do not know.”
Activity has an incredible ability to survive long after its purpose has disappeared.
Simplicity requires continually reconnecting what we are doing to the outcome we are trying to create. If an activity does not meaningfully contribute to that outcome, perhaps we should stop doing it.
That sounds obvious.
Yet most organizations are full of things nobody would intentionally create today but everyone continues doing because they already exist.
Great Leaders Create Clarity
One of the most valuable things a leader can do is make the world simpler for the people around them.
Not by pretending difficult things are easy, but by creating clarity.
Here is where we are going.
Here are the few things that matter most.
Here is what good looks like.
Here is what you own.
Here is the decision that has been made.
Here is what we are intentionally not worrying about right now.
People already carry enormous cognitive loads. They have customers, deadlines, families, projects, inboxes, notifications, meetings, financial concerns, and dozens of competing priorities.
They do not need leaders adding unnecessary ambiguity.
A good leader absorbs complexity and distributes clarity.
A poor leader does the opposite.
Simplicity Takes Courage
There is another reason simplicity is difficult: simple decisions are exposed.
When you reduce ten priorities to three, everyone can see what you chose. When you replace an elaborate performance system with a few clear expectations, accountability becomes obvious. When you shorten the presentation to the five things that matter, there is nowhere to hide.
Complexity gives us cover.
If everything is important, nobody can accuse us of choosing the wrong thing. If every possible scenario is included, nobody can say we forgot something. If twenty people approve a decision, responsibility becomes wonderfully blurry.
Simplicity forces choices.
Choices create accountability.
That is why simplicity requires courage.
Ask What You Can Remove
We usually approach improvement by asking what we should add.
What new process do we need? What new tool? What new meeting? What new metric? What new policy?
Perhaps the better question is:
What can we remove?
What meeting no longer creates value? What report does nobody actually need? What approval exists only because nobody has challenged it? What policy was created around an exception that no longer matters? What could be explained in one page instead of ten? What could one person decide instead of five?
Subtraction is one of the most underused tools in leadership.
Sometimes improvement is not creating something new.
Sometimes it is removing everything standing between people and good work.
The Minimum Complexity Necessary
There is danger in taking simplicity too far.
Some problems genuinely are complicated. Some systems require controls. Some decisions deserve careful analysis. Certain environments require documentation, redundancy, oversight, and review.
The goal should not be simplicity at any cost.
The goal should be the minimum complexity necessary to solve the problem well.
No more.
That distinction matters.
The question is not whether something is complicated. The question is whether every piece of that complexity is earning its keep.
If it is, keep it.
If it is not, remove it.
Simplicity Is an Act of Humility
I increasingly believe simplicity has something to do with humility.
It requires being willing to admit that the answer may not be very sophisticated. That we may not need another framework. That we may not need another meeting. That the process may work perfectly well without us. That everyone already understands the problem and we simply need to act.
Those conclusions do not always make us feel important.
But making ourselves feel important was never supposed to be the objective.
The objective was to solve the problem.
Build the business.
Serve the customer.
Help the teammate.
Make the decision.
Do the work.
Sometimes the most intelligent thing we can do is stop demonstrating how complicated something is and start asking how simple it could become.
Complexity can make us look smart.
Simplicity makes us effective.