One of the most powerful things a leader can do is create an environment where their team is empowered to solve problems. Not just escalate them, not just report them — but genuinely own them and work through them systematically.
This is at the heart of continuous improvement. And yet, in many organisations, problem solving is something that happens reactively — when things go wrong, when a customer complains, when a deadline is missed. The rest of the time, teams are too busy firefighting to step back and address root causes.
The Hospital Nurses Example
I often use an example from a hospital setting to illustrate how powerful team-based problem solving can be. A ward was struggling with medication errors — not catastrophic ones, but a consistent pattern of small mistakes that created risk and consumed time to correct.
The traditional response would have been to add more checks, more sign-offs, more oversight. Instead, the ward leader brought the nursing team together and asked them to map the medication process from start to finish. Not a theoretical process map — the actual process, as it really happened on a busy shift.
What they found was illuminating. The root cause wasn't carelessness or lack of training. It was interruptions. Nurses were being interrupted an average of six times during each medication round — by colleagues, patients, phone calls, and other tasks. Each interruption increased the probability of an error.
The team designed their own solution: a simple visual signal (a coloured vest) that indicated when a nurse was on a medication round and should not be interrupted unless it was urgent. The result was a significant reduction in errors, achieved without adding any new processes, technology, or costs.
The key insight isn't the solution itself — it's that the people closest to the work were the ones who identified the problem and designed the fix. That's continuous improvement in action.
What Continuous Improvement Really Means
Continuous improvement isn't a programme or a project. It's a way of working. It means building the expectation — and the capability — that every team, at every level, is constantly looking for ways to do things better.
This requires a few things to be in place:
- A common language for problem solving. Whether you use A3 thinking, PDCA, 5 Whys, or something simpler — the team needs a shared approach to identifying problems, understanding root causes, and testing solutions.
- Time and permission. If people are running flat out all day, they won't have the headspace to improve. Leaders need to create time for improvement activities and signal that it's valued, not a distraction from "real work."
- Visibility. Problems need to be visible — not hidden. This means creating an environment where it's safe to surface issues without fear of blame. Visual management tools like huddle boards, Kanban boards, and performance dashboards all help.
- Follow-through. Nothing kills a continuous improvement culture faster than asking people for ideas and then doing nothing with them. When a team identifies a problem and proposes a solution, there needs to be a clear process for testing, implementing, and reviewing it.
The Role of Leadership
Leaders set the tone for continuous improvement. If a manager's default response to a problem is to find someone to blame, the team will quickly learn to hide problems rather than surface them. If a leader consistently bypasses the team to impose their own solutions, people will stop trying to contribute.
The most effective leaders in a continuous improvement culture do a few things consistently:
- They ask questions rather than give answers. "What do you think is causing this?" is more powerful than "Here's what you need to do."
- They coach rather than direct. They help their team develop problem-solving skills rather than solving every problem themselves.
- They celebrate the process, not just the outcome. Recognising the effort of investigating a problem thoroughly is as important as celebrating the result.
- They make improvement visible. They share wins, track progress, and create forums where teams can learn from each other.
Bringing It All Together
Problem solving and continuous improvement aren't separate from the day job — they are the day job. The businesses that build this into their DNA don't just get incremental efficiency gains. They build more engaged teams, better customer experiences, and organisations that can adapt to change rather than being overwhelmed by it.
If you're not sure where to start, pick a problem that your team knows about but hasn't been able to fix. Bring them together, map the process, find the root cause, and let them design the solution. You might be surprised at what they come up with.