What Happens After Something Goes Wrong?

Something goes wrong.

A decision produces a poor outcome.

A process fails.

A mistake is made.

A target is missed.

Someone raises a concern that should have been taken more seriously.

The immediate response is often predictable.

We investigate.

We discuss what happened.

We identify responsibility.

We decide what should happen next.

And then, eventually, we move on.

But moving on is not the same as learning.

Neither is having a meeting about what happened.

Neither is writing a report.

Neither is agreeing that we should do better next time.

The important question is:

What will be different because we now know this?

Experience does not automatically create learning

Organisations gain experience every day.

Things go well.

Things go badly.

People make decisions.

Those decisions produce consequences.

Unexpected things happen.

Problems repeat themselves.

But experience only becomes learning when it changes something useful.

A mistake can happen ten times.

If we respond in the same way each time, we may have plenty of experience.

We have not necessarily learned.

That is an important distinction within Human System:

An explanation is not yet learning if nothing useful changes. 

Learning might change how we understand something.

It might change a decision.

It might change behaviour.

It might change a process.

It might reveal that an assumption was wrong.

It might tell us that something we thought was working actually isn't.

But if the experience changes nothing, we should be careful about calling it learning.

First, understand what actually happened

Before we can learn from something, we need to be reasonably clear about what we are learning from.

That means returning to some of the questions that have appeared throughout the previous Insights:

What actually happened?

What did we know at the time?

What did we assume?

What context mattered?

What was reasonably within people's control?

What responsibility existed?

What was different from what we expected?

Those questions matter because learning from the wrong explanation is not much better than failing to learn at all.

If we decide somebody was simply careless when the real issue was that the information they needed was unavailable, we may teach ourselves the wrong lesson.

If we blame a process without examining how it was actually being used, we may change the wrong thing.

If we judge a decision entirely by its outcome, we may confuse poor judgement with bad luck.

Human System therefore asks us to examine what happened before deciding what it means. Outcomes matter, but they need to be understood in relation to the information, assumptions, decisions, implementation and conditions that produced them.

A bad outcome does not always mean a bad decision

This is particularly important.

Something can go wrong even when people made a reasonable decision.

Unexpected circumstances can intervene.

Information can change.

Implementation can fail.

A connected part of the system can produce consequences nobody anticipated.

Equally, a decision can produce a good outcome even when the judgement behind it was poor.

Sometimes we get lucky.

That means learning has to look beyond a simple question:

Did it work?

We may also need to ask:

Was the decision reasonable given what we knew at the time?

What did we expect to happen?

What actually happened?

What was different?

Why was it different?

What does that tell us now?

That gives us a better chance of learning something useful rather than simply rewarding good outcomes and punishing bad ones. Human System deliberately separates decision quality from outcome quality because a reasonable decision can still produce a poor result, while a poor decision can occasionally succeed through luck.

The review is not the end

This is where organisations can sometimes lose the thread.

Something happens.

We review it.

We identify lessons.

Actions are agreed.

Everyone leaves the meeting feeling that something productive has happened.

But what happens next?

Does anything actually change?

Are the actions completed?

Did the change work?

Did it create another problem?

Did people understand what was changing and why?

Was the learning embedded, or did it disappear once attention moved somewhere else?

A lesson that never changes anything is difficult to distinguish from a good intention.

Human System treats review as part of a cycle rather than an ending. Decisions create outcomes, outcomes create information, and that information should influence what happens next through review, refinement and embedding before the system returns to understanding again.

Learning can mean stopping something

When we talk about learning, we often imagine adding something.

New training.

A new process.

Another meeting.

Another layer of oversight.

But sometimes the most useful learning is to stop doing something.

Perhaps a report tells us nothing useful.

Perhaps a process creates more problems than it solves.

Perhaps a measure has become disconnected from what actually matters.

Perhaps a decision made sense at the time but no longer does.

Learning should leave us open to all of those possibilities.

The question is not:

What can we add because something went wrong?

It is:

What should we keep, stop or change because we understand more now?

That may be a much more difficult question.

It can also be more useful.

Repeating a mistake is not always a failure to learn

There is another distinction worth making.

Sometimes organisations assume that if a problem happens again, nobody learned anything.

That may not be true.

Learning can reduce the likelihood of a problem without making it impossible.

People work in changing conditions.

New people arrive.

Different circumstances emerge.

Risks that were managed successfully ten times may still materialise on the eleventh.

The test is not necessarily:

Did this ever happen again?

The better question may be:

Did our understanding, behaviour, decisions or systems change in a useful way because of what happened before?

If they did, learning may have taken place even if the organisation still encounters difficulty.

Human System is not a promise that the same problem will never return.

It is a discipline for making experience useful when it does.

Human System expects the cycle to continue

This is where Post 9 sits within the wider framework.

Human System does not end when something goes wrong.

It does not end when responsibility has been established.

And it does not end when someone has said:

We have learned from this.

The real test comes afterwards.

What changed?

What did we do differently?

What did we stop doing?

What did we understand now that we did not understand before?

What will we review to see whether the change actually worked?

Human System is deliberately cyclical because decisions create outcomes, outcomes create information, and information should influence what happens next. A system that cannot learn is eventually forced to repeat its own mistakes.

That is why learning is not something added after the real work is finished.

It is part of the real work.

What will be different?

For me, that is the question that matters most.

After the investigation.

After the difficult conversation.

After the decision.

After the mistake.

After something went wrong.

What will be different because we now know this?

Not what will we say we learned.

Not what will we write down.

Not what actions will appear in the meeting minutes.

What will actually be different?

Because Human System is not interested in collecting lessons.

It is interested in whether experience changes what happens next.

Something going wrong gives us experience. Understanding what happened gives us information. Learning begins when that information changes something useful.

And that is how Human System turns outcomes — good or bad — into another opportunity to understand, decide and act differently.