The Organisational Understanding Series

Article Four:

Better questions reveal the problems that really need solving.

Every Problem Looks Urgent

Every organisation experiences problems. This scenario will feel familiar to many leaders. A customer raises a complaint. A project overruns and deadlines begin to slip. Quality falls below expectations. Costs begin to rise. Before long, key members of staff start to feel overwhelmed. Eventually someone asks the obvious question:

“How do we stop this happening again?”

It’s an entirely reasonable response.

In fact, most organisations pride themselves on responding quickly when problems arise. Meetings are arranged. Actions are agreed. Responsibilities are allocated. Progress is monitored. Everyone leaves believing the issue has been addressed.

Yet, a few weeks or months later, something remarkably similar happens again.

Perhaps the customer is different. Or maybe it’s another project, or the issue appears in another department. The details have changed, but the pattern hasn’t.

Many organisations don’t repeatedly solve the same problem because they lack capable people. They do so because the problem they fixed wasn’t the one that caused the issue in the first place. The visible problem was simply the first one they noticed, the one making the most noise at the time.

Symptoms Shout. Causes Whisper.

When something goes wrong, the symptoms demand attention.

A delivery is late.
A customer is unhappy.
An invoice is incorrect.
A machine stops.
A report highlights poor performance.

The symptoms are immediate, visible and often impossible to ignore. The causes behave very differently. They rarely announce themselves; they develop quietly over time. A process becomes slightly more complicated, and a workaround is introduced. Information starts being recorded in different places and responsibilities become unclear.

One team changes the way it works without realising the effect on another.

None of these things creates a crisis on its own.

Together, however, they slowly build the conditions in which problems become inevitable.

That’s why symptoms shout, while causes whisper. By the time the organisation notices the symptom, the underlying cause has often been present for weeks, months or even years.

Action Feels Like Progress

When a problem appears, leaders naturally want to act because customers expect answers, employees expect decisions, and key stakeholders expect reassurance. Therefore, doing something feels productive, whereas pausing to understand the problem can feel like a delay. That instinct is understandable.

Decisive leadership matters.

But there is an important distinction between acting quickly and acting wisely. The faster an organisation moves towards a solution, the less opportunity it has to understand whether it is solving the right problem.

This isn’t a criticism of leadership. It’s simply how people are wired. Visible problems create visible pressure. That pressure encourages visible action. Today’s action often becomes tomorrow’s complexity.

A workaround solves an immediate issue. An additional approval reduces one particular risk. A spreadsheet is created because the existing report can’t quite provide what’s needed. A weekly meeting is introduced to improve communication. Each decision makes perfect sense at the time.

Each solves a genuine problem. Collectively, however, they gradually make the organisation more difficult to understand than it was before.

When Firefighting Becomes Normal

Most organisations don’t decide to become reactive; that is something that happens gradually and often unnoticed. People become good at solving today’s problems because they are urgent.

Tomorrow brings another, then another. Eventually, the organisation becomes exceptionally good at responding.

Teams work hard. Managers stay busy. Problems are resolved. Customers are looked after.

On the surface, everything appears under control. Underneath, something more subtle is happening. The organisation gradually becomes better at responding than preventing.

Firefighting begins to feel like effective management; it becomes part of the culture. People are praised for rescuing difficult situations. The individuals who can solve problems quickly become indispensable.

Teams become accustomed to reacting rather than learning.

Few people stop to ask why the same types of problems keep returning. Not because they don’t care. Because they’re already busy solving the next one.

Every Department Sees a Different Problem

One reason recurring problems are so difficult to solve is that every part of the organisation experiences them differently.

Sales believes Operations is slowing delivery.

Operations believes Sales is making promises that are difficult to fulfil.

Finance sees rising costs. Customer Service hears growing frustration from customers. IT receives requests for yet another system enhancement. Human Resources notices increasing pressure on employees.

Every department is describing something real. Every observation is valid. Yet none of them is looking at the organisation as a whole. Each sees the symptom that arrives on its doorstep.

Very few people can see the complete journey the work has taken to get there. This is why well-intentioned organisations sometimes introduce solutions that improve one area while unintentionally creating problems somewhere else.

The local problem disappears. The organisational problem simply moves somewhere else.

Looking Beyond the Obvious

The most effective leaders develop a habit that sets them apart.

When everyone else is asking,

“How do we fix this?”

they quietly ask something different.

“Why has this become necessary?”

That question changes everything.

Instead of immediately searching for a solution, it creates space for understanding. Instead of focusing on the event itself, it explores the conditions that made it possible. Instead of assigning blame, it seeks insight.

The answer is not always comfortable.

Sometimes it reveals that the issue has existed for much longer than anyone realised. Sometimes it shows that several perfectly sensible decisions have gradually combined to create an unintended outcome. Sometimes it highlights that nobody has done anything wrong at all.

The organisation has simply evolved. And with that evolution, its understanding has failed to keep pace.

Better Questions Change the Conversation

The way an organisation responds to problems says a great deal about how it thinks. When something goes wrong, the first questions are often predictable.

“Who made the mistake?”

“How do we stop this happening again?”

“What new control do we need?”

Each question is understandable. Each is asked with the best of intentions. Yet they all begin from the same assumption, that the problem is sitting directly in front of us.

Sometimes it is.

Often it isn’t.

The organisations that improve consistently develop a different habit. Before searching for solutions, they become curious about the conditions that allowed the problem to develop in the first place. Instead of asking:

“Who is responsible?”

they ask:

“Where did the difficulty begin?”

Instead of asking:

“What went wrong?”

they ask:

“What was happening before it went wrong?”

Instead of asking:

“Which department owns this?”

they ask:

“How did the work move through the organisation?”

Those questions rarely produce instant answers. They do, however, produce something far more valuable. Understanding.

Looking Beyond Individual Events

One complaint may be an isolated incident. Several complaints that look different on the surface may share exactly the same underlying cause.

A delayed delivery.
An incorrect invoice.
A customer chasing an update.
A frustrated member of staff.

They appear to be separate issues. Viewed individually, each demands its own solution. Viewed together, they may reveal a single weakness that no one had previously recognised.

This is why effective leaders resist the temptation to investigate problems in isolation. They look for patterns. Patterns reveal relationships. Relationships reveal opportunities for improvement.

Improvement Begins with Understanding

There is an understandable temptation to believe that improvement starts when changes are made. In reality, improvement usually begins much earlier. It begins when the organisation sees itself more clearly.

Without that understanding, improvement becomes guesswork. One team changes the way it works. Another introduces a new report. A manager creates another approval stage. A different department invests in another software tool.

Each initiative may bring genuine benefits. Yet if nobody understands how those changes affect the wider organisation, they can unintentionally create new problems while solving old ones.

The quality of the improvement depends upon the quality of the understanding that comes before it.

Seeing the Organisation as a Connected System

One of the most significant shifts a leadership team can make is to stop viewing problems as isolated events. Instead, they begin to see the organisation as a connected system. Work does not begin and end within departments. Information flows between people. Decisions influence later decisions.

Delays in one area often create pressure elsewhere. A small change made with good intentions can have unexpected consequences several steps further along the journey.

The more clearly leaders can see those connections, the easier it becomes to improve the organisation without creating unnecessary complexity elsewhere. That is why understanding must always come before improvement.

Progress Is Measured by Learning

Many organisations measure success by the number of problems they solve. There is nothing wrong with that. But truly resilient organisations measure something else as well.

They ask whether each problem has helped them understand the organisation more deeply than they did before.

If every challenge leaves behind greater clarity, then each difficulty becomes an opportunity to strengthen the organisation rather than simply recover from another setback.

Over time, those lessons accumulate. The organisation becomes more capable. More confident. More resilient. Not because fewer problems occur.

One Question Worth Asking

Think about the last significant problem your organisation solved. Did you solve the event? Or did you uncover the conditions that allowed it to happen?

The answer may reveal more about your organisation than the problem itself.

How Map Your Process Helps

At Map Your Process, we believe meaningful improvement begins with meaningful understanding.

Before introducing new controls, changing systems, or redesigning how people work, we help organisations understand how work is actually carried out today. By making those connections visible, leadership teams gain the insight needed to improve with confidence, reduce unnecessary complexity and build capability that lasts.