The Problem You Can See Is Not Always the Problem You Have

When something goes wrong, our attention naturally goes to the thing we can see.

Absence has increased.

A target has been missed.

People are leaving.

Complaints are rising.

A process keeps failing.

A team is not working well together.

These are real problems.

But they may not be the whole problem.

Sometimes, what we can see is a symptom of something else happening within the system.

That is where Systems Thinking becomes useful.

The obvious problem is not always where the problem begins

Imagine sickness absence starts to rise.

The obvious response might be to focus on absence.

Monitor it more closely. Review individual cases. Tighten the process. Ask managers to reduce it.

Some of those actions may be appropriate.

But what if rising absence is a symptom?

What if workload has increased?

What if vacancies are leaving fewer people to do the same amount of work?

What if people are becoming increasingly stressed?

And what if the resulting absence creates even more pressure on the people who remain?

Now we are looking at something different.

High workload may contribute to stress.

Stress may contribute to sickness absence.

Sickness absence reduces the number of people available.

That increases workload further.

The original problem is still there. But it may also have become part of a pattern that is reinforcing itself. Human System therefore asks us to distinguish between what we can observe, what we think may be happening and what we still need to investigate.

Simply telling managers to reduce absence would not necessarily address what is producing it.

This is what Systems Thinking asks us to do

Systems Thinking can sound abstract.

It isn't.

At its simplest, it means recognising that things are connected.

What happens in one part of an organisation can influence what happens somewhere else.

A decision made at senior level can change how a team works.

A poorly designed process can influence people's behaviour.

Pressure in one service can create consequences in another.

A measure designed to improve one outcome can unintentionally make something else worse.

The connections exist whether we look for them or not.

Systems Thinking simply asks us to look.

Instead of asking only:

What has gone wrong?

We can also ask:

What might be producing this?

What else is connected to it?

What influences it?

What does it influence?

Could this be a symptom rather than the whole problem?

That shift can make a significant difference to the way we respond.

The risk of fixing the visible symptom

When we assume the visible problem is the problem, we can become very good at treating symptoms.

A service misses a target, so we introduce another performance measure.

People make mistakes, so we provide more training.

Staff leave, so we focus on recruitment.

A process is not followed, so we create another process to make sure the first one is followed.

Sometimes those responses will be right.

But sometimes we are adding more to the system without understanding what the system is already producing.

People may already know what to do but lack the time, capacity or tools to do it.

The target may be missed because demand has changed.

Staff may be leaving because of something happening within the team or wider organisation.

The process may not be followed because it does not work properly in practice.

If we don't look beyond the visible problem, we can spend a great deal of time fixing the consequences while leaving the conditions that produced them untouched.

And occasionally, we can make the system worse in the process.

There may not be one simple cause

This is another reason Systems Thinking matters.

Organisations often want to find the root cause.

Sometimes there is a clear cause.

But complex problems do not always work that way.

There may be several connected factors, each influencing the others.

Workload.

Staffing.

Demand.

Management decisions.

Technology.

Communication.

Processes.

Culture.

Individual circumstances.

None of these necessarily explains the whole problem on its own.

But together, they may help us understand what is happening.

So rather than always asking:

What caused this?

Sometimes a better question is:

What patterns of interaction might be maintaining or amplifying this problem?

That is a more difficult question.

But it may be a more useful one.

Looking wider does not mean doing nothing

Systems Thinking is not an excuse for endless analysis.

We will not always have time to investigate every possible connection before acting.

Sometimes the immediate problem needs an immediate response.

If something is unsafe, we deal with the immediate risk.

If a service is failing, people may need support now.

Action and understanding do not have to be mutually exclusive.

Human System recognises that we sometimes have to act while uncertainty remains. But where possible, our response should leave room to learn more, review what happened and reconsider our understanding.

The point is not to delay action until we understand everything.

It is to avoid assuming that the first thing we see tells us everything we need to know.

This is where Systems Thinking fits within Human System

Human System is built on the idea that organisations are made up of connected people, decisions, structures, behaviours and systems.

What happens in one part can affect another.

A decision changes conditions.

Conditions influence behaviour.

Behaviour produces outcomes.

Those outcomes give us information.

And that information should help us understand, learn and adapt.

That is why Human System does not treat problems as isolated events by default.

When something goes wrong, the immediate issue matters. It may need to be dealt with quickly.

But the framework also asks us to look wider.

What happened?

What else might have influenced it?

What conditions were present?

What decisions, systems or behaviours may have contributed?

And what might this outcome tell us about the wider system?

That does not mean every problem is caused by the system, or that individuals have no responsibility.

It means we should not automatically assume that the person or event closest to the visible problem tells us the whole story.

In Human System, understanding comes before deciding.

And Systems Thinking helps us understand that what we are seeing may be an outcome of connections we have not yet examined.

So before we rush to solve the problem, perhaps we should ask:

Are we looking at the problem itself, or at a symptom of something else?

And then:

What in the system might be producing what we are seeing?

That is where Systems Thinking becomes part of Human System: helping us look beyond the visible symptom, understand the conditions and connections around it, and make better decisions about what to do next.