Knowing Is Not the Same as Understanding

We know more than ever.

Organisations have access to dashboards, reports, KPIs, surveys, audits, financial information and vast amounts of data.

We can measure performance in remarkable detail.

And yet, having information is not the same as understanding what is actually happening.

You can know that a target has been missed.

That does not mean you understand why.

You can know that staff absence has increased.

That does not mean you understand what has changed.

You can know that a service is underperforming.

That does not mean you understand the pressures, decisions, relationships or systems contributing to it.

You can know that somebody made a mistake.

That does not mean you understand the situation in which they made it.

This distinction matters.

Because organisations are often very quick to move from knowing that something has happened to deciding what to do about it.

Sometimes we need to slow down.

What do we actually know?

There is nothing wrong with information.

Good information is essential.

The problem comes when we mistake information for the complete picture.

A dashboard can tell us that something has changed.

A report can show us a trend.

An audit can identify that a requirement has not been met.

A survey can tell us what people have said.

All of those things are useful.

But they are only part of the picture.

Information can tell us what.

Understanding requires us to explore why.

And often, that means going beyond the information already in front of us.

It means asking questions.

Listening to people.

Looking at context.

Considering what we might be missing.

And being prepared to accept that our first explanation may not be the right one.

The danger of quick conclusions

We are all capable of seeing something and immediately forming a view about what it means.

A target is missed, so somebody must not be performing.

A deadline slips, so somebody must not have managed their time properly.

A process is not followed, so somebody must have ignored it.

Sometimes those conclusions will be right.

Sometimes they won't.

The difficulty is that once we think we know what the problem is, it becomes very easy to start solving the wrong problem.

We can introduce a new process when the real issue was a lack of capacity.

We can provide more training when people already knew what to do but didn't have the right tools.

We can hold an individual accountable for something that was influenced by decisions or conditions well beyond their control.

We can respond to the visible outcome without understanding the system that produced it.

And then wonder why the problem has not gone away.

Understanding takes curiosity

For me, understanding starts with being willing to say:

I know something has happened. I don't yet know everything about why.

That requires curiosity.

Not the performative kind, where we ask people for their views after we have already decided what we think.

Real curiosity.

The willingness to ask questions and genuinely listen to the answers.

Questions such as:

• What is actually happening here?

• What do we know?

• What are we assuming?

• What might we be missing?

• Who is closest to this and what can they tell us?

• What else could explain what we are seeing?

These questions do not guarantee that we will reach the right answer.

But they give us a better chance of understanding the situation before deciding what to do.

Understanding is not about knowing everything

Of course, we will rarely have complete information.

In real organisations, decisions often have to be made before every question has been answered.

Waiting until we understand everything is not realistic.

But there is a difference between accepting that we cannot know everything and assuming that we already know enough without testing our understanding.

Human System is not about delaying decisions indefinitely.

It is about recognising that understanding comes before deciding.

Not perfect understanding.

Not complete certainty.

But enough understanding to give us confidence that we are responding to the situation we actually have, rather than the one we have assumed.

Knowing should be the beginning

Perhaps this is the distinction.

Knowing something has happened should not always lead immediately to action.

Sometimes it should lead to another question.

What does this actually mean?

Because knowing that something is wrong and understanding what is wrong are not the same thing.

And knowing what has happened is not the same as understanding why it happened.

The more complex the situation, the more important that distinction becomes.

We can collect more information.

We can build more detailed reports.

We can add more measures and indicators.

But none of those things automatically create understanding.

That still requires us to think.

To ask.

To listen.

And occasionally to admit:

We know what we are looking at. But do we actually understand it yet?

In Human System, these ideas are connected:

Purpose gives us something to remain answerable to; understanding helps us see what is actually happening before we decide what to do.