Healthcare teams solve problems every day. A patient falls despite precautions being in place. A discharge is delayed. A clinic overruns. Medication isn’t available when it’s needed. A complaint arrives from a frustrated patient or family member.
In every case, people respond. Meetings are held, actions are agreed, reminders are sent and processes are adjusted.
Yet despite everyone’s best efforts, many of the same problems return. Not because people don’t care. Not because they aren’t working hard enough. But because solving today’s problem is not always the same as preventing tomorrow’s.
One of the biggest differences between organisations that continuously improve and those that simply react is where they focus their attention. Reactive organisations fix what they can see. Improving organisations work to understand why it happened in the first place.
Healthcare is built around the need to respond quickly.
When a patient deteriorates, clinicians intervene immediately. When an incident occurs, leaders want reassurance that action is being taken.
When waiting lists increase or performance falls, organisations naturally look for solutions that can be implemented quickly. That urgency is entirely understandable. Patients cannot wait while organisations spend weeks analysing every problem.
However, urgency has an unintended consequence.
The first question often becomes: “What should we do?”
Long before anyone asks: “Why did this happen?”
The result is that teams frequently implement changes designed to address the immediate issue rather than the conditions that allowed it to occur. Sometimes those actions work. Often they don’t. Or they work for a while before the problem quietly returns.
Every problem has visible symptoms.
Long waiting times. Delayed discharges. Patient complaints. Medication errors. Missed appointments.
These are the issues people experience, measure and report. They are important, but they are rarely the problem itself. Instead, they are usually the result of deeper issues within the system.
Consider delayed patient discharge. The visible symptom is straightforward: Patients are waiting to leave hospital. It’s tempting to conclude that pharmacy is too slow, transport is unavailable or discharge paperwork is taking too long. While any of those factors might contribute, they may not explain why delays occur so consistently.
Perhaps discharge planning starts too late. Perhaps expected discharge dates are not routinely discussed. Perhaps communication between teams is inconsistent.
The visible problem is the final outcome of a much longer chain of events. Unless that chain is understood, improvement efforts often focus on making the symptom less painful rather than preventing it altogether.
It’s easy to assume that recurring problems happen because organisations fail to investigate properly. The reality is more complicated.
Human beings are naturally wired to solve visible problems. When something goes wrong, our brains immediately start searching for solutions. That instinct is valuable in emergencies. It becomes less helpful when improving complex systems.
Visible problems attract attention. Recent incidents feel more important than underlying trends. The first explanation often feels convincing because it fits our existing experience.
Under pressure, it is entirely reasonable to choose the solution that appears quickest to implement. None of this reflects poor leadership or a lack of commitment. It reflects the reality of working in busy healthcare environments where time, capacity and resources are always limited.
The challenge is recognising when a quick fix is appropriate, and when a deeper investigation will ultimately save far more time, effort and frustration.
Organisations that improve consistently ask different questions.
Instead of beginning with solutions, they begin with understanding.
Rather than asking: “What should we change?”
they first ask: What actually happened? What evidence do we have? What conditions allowed this to happen? What in the system contributed to this outcome?
These questions encourage curiosity rather than assumption. They also recognise an important principle of improvement science: Most problems are created by systems rather than individuals.
That doesn’t mean people never make mistakes. It means that understanding why mistakes become possible is usually more valuable than simply reminding people not to make them again.
This shift in thinking moves improvement away from blame and towards learning.
The difference between treating symptoms and improving systems becomes clearer when viewed through real-world examples.
A ward experiences an increase in patient falls.
The immediate response is to remind staff to complete falls risk assessments and reinforce existing procedures. Training is delivered and awareness increases. For a few weeks, the number of falls decreases.
Then they begin to rise again.
A deeper investigation reveals that high-risk patients are often moved between beds during busy periods, making planned observation routines difficult to maintain.
The issue was never simply staff awareness. It was the way observation processes worked within a changing ward environment.
Patients regularly wait several hours for discharge medication.
The initial response focuses on reducing pharmacy turnaround times. Additional pressure is placed on pharmacy staff and performance improves temporarily.
However, delays continue.
Further investigation shows that discharge planning routinely begins on the morning patients are expected to leave hospital. By the time prescriptions reach pharmacy, delays have already become inevitable.
Improvement efforts shift towards earlier discharge planning rather than faster dispensing. The bottleneck moves upstream.
An outpatient department receives repeated complaints about poor communication.
Managers remind staff to keep patients updated. Despite everyone’s best intentions, complaints continue.
Observing the clinic reveals something different. Patients often wait for long periods with no visible indication of expected delays. Staff assume patients understand what is happening because they are busy managing clinical work.
The improvement isn’t better customer service training. It’s introducing simple, consistent communication processes that keep patients informed throughout their visit.
In each example, the visible symptom pointed towards one solution. Understanding the system revealed another.
Experienced improvement teams rarely rely on one tool to understand complex problems. Instead, they use a range of complementary tools, each answering a different question.
|
Question |
Improvement Tool |
|---|---|
|
Which problems deserve our attention? |
|
|
Where does the problem occur within the process? |
Process Mapping |
|
What factors might be contributing? |
Fishbone Diagram |
|
Why is this particular problem happening? |
|
|
What changes should we make? |
Driver Diagram |
|
Are those changes leading to improvement? |
PDSA Cycles and Measurement |
Each tool builds on the previous one. Together, they help teams move from identifying problems to understanding them, testing solutions and sustaining improvement.
No single tool provides every answer. The real strength of improvement comes from combining the right methods at the right time.
One of the simplest ways to improve investigations is not by collecting more data or introducing more meetings. It’s by asking better questions. Instead of accepting the first explanation, experienced improvement teams remain curious.
When an answer is given, they ask: “Why did that happen?”
When another answer emerges, they ask again. Not because there is a magic number of questions. But because each question helps uncover another layer of understanding.
This mindset sits at the heart of techniques such as the 5 Whys.
The value of the method is not the number itself. Its value lies in encouraging teams to pause before jumping to conclusions and to understand the processes, decisions and conditions that shaped the outcome.
Sometimes the investigation confirms the team’s original assumption. Often it doesn’t.
Perhaps the greatest benefit of looking beyond symptoms is the effect it has on organisational culture.
When investigations focus primarily on who made a mistake, people naturally become cautious. Mistakes are hidden. Near misses go unreported. Learning becomes more difficult.
When investigations focus instead on understanding the system, conversations change. Questions become less about assigning responsibility and more about discovering opportunities to improve. People feel safer sharing what really happened. Teams become more willing to experiment with new ideas. Learning accelerates.
Continuous improvement depends on this kind of culture.
Not because organisations ignore accountability, but because they recognise that understanding systems is usually the fastest route to preventing problems from happening again.
Healthcare organisations will always face pressure to respond quickly when problems arise. That pressure isn't going to disappear.
The organisations that improve most successfully are not those that react fastest. They are the ones that take the time to understand why problems occur before deciding how to solve them.
Looking beyond symptoms requires curiosity, evidence and a willingness to question assumptions. It also requires recognising that most improvement opportunities lie within the way work is designed, not simply in the actions of individuals.
Techniques such as the 5 Whys help teams develop this way of thinking, encouraging them to investigate problems more deeply and create improvements that address the underlying causes rather than the visible effects. Because lasting improvement rarely comes from fixing today’s problem. It comes from building systems that make tomorrow’s problem less likely to happen at all.