Complexity is often created, not inherited

Complex organisations are not always designed to be complex.

More often, complexity develops gradually.

A problem occurs, so a new check is introduced. Something goes wrong, so another approval is added. Information is difficult to find, so another report is created. Communication fails, so another meeting appears in the diary.

Each decision may be entirely reasonable at the time.

The difficulty is that organisations are often much better at adding things than removing them. The original problem changes or disappears, but the process created in response to it remains.

Over time, yesterday's solutions can become today's complexity.

One reasonable decision at a time

Complexity rarely arrives through one obviously bad decision.

It accumulates through dozens, sometimes hundreds, of decisions that made sense individually and at a particular point in time.

A manager wants greater visibility, so a report is introduced. A mistake creates concern, so an additional approval is required. A team needs information from another department, so a regular meeting is established. A system cannot perform a particular task, so somebody creates a spreadsheet to bridge the gap.

None of these responses is necessarily wrong.

But organisations change. Systems improve. Teams restructure. Risks change. Information becomes available in different ways.

What is often missing is the point at which somebody goes back and asks whether the response is still necessary.

The result is accumulation. And accumulation creates waste: wasted resource, financial costs from avoidable steps and actions, and risks created by processes that are no longer properly understood.

Reports sit alongside newer reports. Meetings continue despite their original purpose having disappeared. Approvals remain long after the risk that created them has changed. Temporary spreadsheets become permanent operational tools. And when the person who understands why a workaround exists eventually leaves, that knowledge can leave with them.

Complexity rarely arrives all at once. It accumulates one reasonable decision at a time.

When organisations forget why

One of the clearest signs of unnecessary complexity is when people know what they have to do, but nobody can confidently explain why they have to do it.

The report has always been produced.

The meeting has always happened on Tuesday.

The spreadsheet has always been updated.

The approval has always been required.

At that point, the organisation retains the activity, but may have lost the reasoning behind it.

This is a form of organisational memory without organisational understanding.

It can be surprisingly difficult to challenge because familiarity itself begins to provide legitimacy. If something has existed for years, people understandably assume there must be a reason for it.

Sometimes there is.

But longevity is not evidence of value.

Ask why

One of the simplest questions in operational improvement is also one of the most useful:

Why?

Why do we produce this report?
Why does this decision require three approvals?
Why is this information entered twice?
Why does this meeting need to happen every week?
Why does this workaround still exist?

Techniques such as the Five Whys, commonly used within Lean Six Sigma and root-cause analysis, provide a simple discipline for moving beyond the first explanation.

The point is not to ask “why?” mechanically five times. It is to keep questioning until the underlying reason for the activity becomes clearer.

A report may exist because a senior manager once needed information that is now available elsewhere.

An approval may have been introduced because of a specific failure that has since been addressed through a better system.

A spreadsheet may exist because two systems did not communicate when they were first implemented.

A meeting may have been created during a period of organisational change and simply continued afterwards.

Root-cause questioning does not assume that an activity is unnecessary. Sometimes it demonstrates precisely why a control, process or check remains important.

But sometimes it reveals that the organisation is continuing to solve a problem that no longer exists.

Complexity has a cost

Unnecessary complexity is not simply irritating. It consumes organisational resources.

The costs are not always immediately visible, but they appear in several ways:

Time: additional approvals, meetings, reconciliations, reporting and administration all consume working hours.
Capacity: skilled people spend time servicing internal processes rather than delivering the work for which their expertise is most valuable.
Decision-making: additional layers can slow decisions and make it less clear who actually has the authority to make them.
Accountability: when too many people become involved in a process, individual ownership can become harder to identify.
Confidence: people become reluctant to act independently when they are unsure which process, approval or expectation applies.
Money: every unnecessary hour, duplicated activity, delayed decision and avoidable workaround ultimately has a financial consequence.

Individually, these costs may appear small.

Across an organisation, repeated every day, they can become significant.

Workarounds have a habit of becoming systems

Most organisations need workarounds occasionally.

A system fails. A process does not quite work. Information is unavailable. Something needs to be delivered before a permanent solution can be implemented.

The workaround solves the immediate problem.

The risk comes when temporary solutions lose their temporary status.

Someone creates a spreadsheet “for now”. Another person learns how to maintain it. A checking process develops around it. Instructions are written. Eventually, new employees are trained to use it.

What began as a temporary response has become part of the operating model.

This does not mean workarounds are inherently bad. They can be pragmatic and necessary.

But every workaround should eventually lead to another question:

Do we still need this?

Without that question, organisations can become extremely proficient at maintaining solutions to problems they should instead have resolved.

More control does not always mean more control

When something goes wrong, adding another control can feel reassuring.

Sometimes it is exactly the right response.

But additional controls do not automatically create stronger governance.

If a process contains too many checks, ownership can become diluted. People may assume somebody else will identify the problem. Decisions can move through several layers without it being clear who is ultimately accountable for them.

The presence of a control is not the same as the effectiveness of a control.

Good governance should make responsibility clearer, risk more visible and decision-making more reliable.

If a control adds activity without achieving those things, its purpose deserves to be questioned.

Simplification is not the absence of governance

There is an important distinction between simplifying an organisation and stripping away necessary controls.

Good organisations need processes.

They need governance.

They need appropriate checks and balances.

And in regulated or higher-risk environments, some processes will inevitably be more complex because the consequences of getting something wrong are greater.

The objective should not therefore be to make everything as simple as possible.

It should be to make complexity proportionate and purposeful.

A useful test is not simply:

Can we remove this?

It is:

What purpose does this serve?
What risk or outcome does it address?
Is that risk still present?
Is this still the most effective way of addressing it?
Does the value of the process justify the effort it requires?
Could we achieve the same outcome more clearly or efficiently?

Sometimes the answer will be that the process should remain exactly as it is. That is still a valuable conclusion because the organisation now understands why.

Making work easier to do well

Good operational design should make the right way of working easier to understand and easier to follow.

People should not need years of organisational knowledge simply to navigate routine processes. They should not need to know which unofficial spreadsheet contains the real information, which meeting actually makes the decision or which person can bypass a process when it stops working.

Where complexity is necessary, its purpose should be understandable. Where it is unnecessary, it should be challenged. And where a temporary response has quietly become permanent, it should be reviewed.

Simplification is not about removing structure. Done properly, it creates better structure by making responsibilities, processes and decisions clearer.

Question what has accumulated

Organisations naturally look forward.

New priorities. New systems. New projects. New controls. New reporting requirements.

Operational improvement also requires occasionally looking backwards.

What have we accumulated?
What are we still doing because of a decision made several years ago?
Which temporary solutions became permanent?
Which controls still manage a genuine risk, and which simply survived the problem that created them?
Which activities would we choose to introduce today if they did not already exist?

These are not questions about cutting for the sake of cutting. They are questions about purpose.