· 5 min read

Available in: Norsk

Simplicity Is Also a Strategy

Simplicity Is Also a Strategy

When organizations encounter a problem, the most common reaction is to add something.

More teams. More processes. More meetings. More roles. More systems.

Very rarely is the first reaction to stop and ask:

Can we make this simpler?

And yet that question is often the one that creates the greatest value.

We talk a great deal about innovation, growth, and transformation. We discuss new opportunities, new capabilities, and new initiatives. Much less frequently do we talk about simplicity. Perhaps because simplicity can easily be mistaken for naivety or a lack of ambition. My experience has been the opposite. Simplicity is not the absence of strategy. Simplicity is often the result of good strategic choices.

Complexity Looks Smart

Complex solutions tend to appear more mature. They often come with detailed models, extensive terminology, sophisticated processes, and comprehensive governance structures. Everything looks well thought through and under control, which is precisely why it is easy to feel confident in such solutions.

The problem is that complexity often hides costs that are invisible at the moment the decision is made.

Complexity means more dependencies, more coordination points, more decisions, more sources of failure, higher costs, and less ability to adapt. Every new process, every new system, and every new organizational layer may seem reasonable when viewed in isolation. Yet complexity has a tendency to accumulate over time.

Nobody sets out to build an organization that is unnecessarily difficult to understand or change. Nevertheless, it happens. Not through one major decision, but through many small ones. Each of them logical. Each of them rational. Each of them a solution to a real problem.

In the end, organizations often find themselves spending more and more energy managing themselves.

Strategy Is Also About Choosing What Not to Do

Many people think of strategy as a list of things we are going to do.

I believe strategy is just as much about what we choose not to do.

If everything is important, nothing is important. If every initiative is strategic, there is no real strategy.

The essence of strategy is focus. Choosing one direction inevitably means choosing not to pursue others. That is exactly what makes strategic decisions difficult. The problem is rarely a lack of good ideas. The problem is that there are too many of them.

This is why simplicity often emerges as a consequence of good strategy. When we become clearer about what truly matters, it also becomes easier to remove what does not.

From Many Topics to a Few Choices

In any strategy effort, it is easy to end up with a long list of initiatives, projects, and improvement areas. AI, data, analytics, personalization, automation, partnerships, platforms, and integrations all represent important opportunities.

The challenge begins when everything is presented as equally important.

At that point, the organization gains more priorities, more dependencies, and more discussions, but not necessarily more direction.

One of the most valuable outcomes of a successful strategy process is therefore not what gets added. It is what gets reduced. From many topics to a few areas of focus. From many goals to a few priorities. From many discussions to a few decisions.

Simplification is not about ignoring complexity. It is about understanding complexity well enough to identify what truly matters.

The Hidden Cost of Complexity

Complexity is not free.

Yet it is often treated as if it were.

When we introduce a new system, we do not merely create new functionality. We also create new skills that must be developed, new integrations that must be maintained, new decisions that must be made, and new dependencies that must be managed.

The same applies to processes, governance forums, and organizational models.

Many organizations are good at measuring the benefits of what they add. Far fewer measure the cost of the complexity they introduce at the same time. Perhaps we should do that more often.

A useful question might be:

What lasting complexity does this decision create?

That question is rarely as popular as questions about growth and benefits.

Yet it may be just as important.

Simplicity Requires Courage

The paradox is that simplicity is often more difficult than complexity.

It is relatively easy to add a new meeting. It is much harder to remove one. It is easy to create a new process. It is harder to challenge whether the process is necessary at all. It is easy to create exceptions. It is harder to hold the line on a standard.

That is why simplicity is rarely the result of chance.

Simplicity requires discipline. And often a little courage.

The courage to challenge accepted truths. The courage to walk away from good ideas. The courage to say no when the organization would rather say yes. And the courage to accept that more options do not necessarily make us better.

Five Questions That Can Reduce Complexity

When facing a new problem or a new decision, it can be useful to stop and ask a few simple questions.

  1. Is there a simpler solution?
  2. What complexity does this introduce?
  3. Does the benefit justify the additional complexity?
  4. Can the problem be broken down into smaller parts?
  5. What can we choose not to do?

The questions are simple.

That does not mean the answers are.

Complexity Happens Naturally. Simplicity Must Be Chosen.

Many organizations improve by adding.

Some improve by removing.

The best often do both, but they are highly conscious of the difference.

They understand that every new component, every new team, every new process, and every new layer of governance comes with a cost. They know that complexity is not necessarily a sign of maturity. And they know that simplicity is not a lack of ambition.

Quite the opposite.

Simplicity is often the result of the most difficult and most important strategic choices.

Because the best strategies are not about doing everything.

They are about understanding what matters most and having the courage to focus on exactly that.

Share this article

LinkedIn
Hugo Moen

Hugo Moen

Lead Architect

Writes about platform architecture, enterprise architecture and the interplay between technology and organization.

Follow on LinkedIn

Related articles