Before solving the problem, make sure it is the problem

A problem comes up in a meeting. Delivery is slipping. Customers are unhappy. Two teams are frustrated with each other. A decision that was meant to be settled is back on the agenda again.

Someone says, “We need to fix this.”

Usually, that is when the room moves quickly. Ideas come out. A new process. A clearer message. A new owner. Another meeting. A plan with actions and dates.

It can feel productive. People leave with something to do. The problem has been named, and now it looks as though it is being handled.

Then, a few weeks later, it comes back.

Maybe not in exactly the same form. But close enough for people to recognise it. The delivery is still slow. The teams still do not seem to understand each other. The decision is still not holding. People are tired of talking about it, but nobody is quite sure why it keeps returning.

That is often the point where it is worth asking a different question.

Are we solving the right problem?

When action becomes the easy part

Most people do not jump into solutions because they are careless. They do it because they care about the work and want things to move.

There is pressure from customers, colleagues, deadlines and leaders. There is usually another issue waiting behind this one. People want to be useful, and doing something feels better than sitting with a problem that is still unclear.

But action can also become a way of getting away from the harder work.

A team sees a delay and decides it needs a better planning process. But the delay is really caused by a decision that nobody owns.

A leadership group sees poor collaboration and decides people need to communicate better. But the real issue is that two functions are working towards priorities that pull them in different directions.

A manager sees that people are not following a new way of working and repeats the message. But the work is still difficult because an important dependency has not been sorted out.

The visible issue gets attention. The pattern underneath keeps going.

The visible problem gets attention. The pattern underneath keeps going.

This is one reason recurring problems are so costly. The organisation is not doing nothing. People are often working hard to improve the situation. But the effort goes into the part of the problem that is easiest to see, while the thing creating it is left in place.

Then the same issue returns, and it costs more time, more energy and more trust than it did the first time.

Looking at what is underneath

There is a difference between slowing work down and taking enough time to understand what is happening.

Not every issue needs a long investigation. Sometimes something is broken, and the answer is clear. Fix it.

But when the same issue keeps coming back, it is usually worth pausing before adding another solution.

• Where does the issue show up?
• What keeps repeating?
• What has changed, and what has stayed the same?
• Who is seeing the problem from a different place?
• What is it costing in rework, missed decisions, delays, frustration or trust?

These are simple questions. In a busy organisation, they can be hard to ask because they do not give an immediate answer. They ask people to stay with the uncertainty for a little longer.

But that is often where the useful work starts.

The people closest to a problem usually hold different parts of the picture. One team sees the customer impact. Another sees the system limitation. A manager sees the pressure coming from above. Someone else sees the workarounds people have built because the normal process does not work.

No one person has the whole view.

When people are working from separate fragments, they can all make sensible decisions that still do not solve the issue. Each response may be reasonable from where that person is standing. The problem is that the wider pattern remains unseen.

Making the pattern visible

The work is to bring more of the picture into the room.

Not to make the problem bigger than it is. Not to turn every meeting into a deep reflection. Just to make what keeps happening visible enough that people can act on it together.

When a group can see where the work gets stuck, what assumptions are different and what it is costing, the conversation changes. People spend less time defending their own part of the story. Ownership becomes easier to clarify. Decisions become more grounded because they are based on more than one slice of the situation.

The next move may still be difficult. It may require a trade-off, a decision that has been avoided or a conversation nobody has wanted to have.

But at least the group is working on the issue that is actually there.

Sometimes the quickest way forward is to pause first.

This is where disciplined curiosity becomes practical. It helps people notice when they are moving quickly because the answer is clear, and when they are moving quickly because the uncertainty feels uncomfortable.

It is not about asking questions forever. It is about asking enough of the right questions before committing time, energy and people to a solution that may only treat the symptom.

The next time a problem comes up, the first question may not need to be, “What should we do?”

It may be, “What is really happening here?”