Moving Beyond Containment: Solving Problems at the Three Levels for Sustainable Operational Excellence
In many organizations, the instinctive response to problems is containment. Teams focus on stopping the immediate impact, stabilizing operations, and restoring output as quickly as possible. This approach is understandable. Leaders are under pressure to deliver, and operational disruptions can have significant financial and customer consequences. But containment alone does not make an organization stronger. At best, it buys time. At worst, it lulls teams into believing the issue is resolved when, in reality, the conditions that created it still exist.
I’ve seen this pattern in healthcare, manufacturing, and service industries. Problems are addressed at the surface while deeper systemic weaknesses remain untouched. Teams work hard to put out fires, but those fires return—sometimes in the same form, sometimes in a new one. The organization experiences repeated frustration, inefficiency, rework, wasted resources, and rising costs. Leaders call for more accountability and more urgency, yet the underlying issues persist.
This is not a failure of effort. It is a failure of method.
Operationally excellent organizations understand that problems exist at multiple levels. Each level provides a different lens into what went wrong and what must be strengthened. When teams learn to analyze problems through these levels—specific, detection, and systemic—they move from firefighting to building reliability, resilience, and long-term capability.
This multi-level approach is foundational to Lean thinking and essential for organizations striving to deliver high-quality, predictable performance. It creates a culture where learning becomes daily work and where problems, rather than being seen as threats, become opportunities to build stronger processes and more capable teams.
In this article, I will break down the three levels of problem-solving, explain the purpose of each, and illustrate how they work together to create sustainable improvement. Whether you lead a frontline team or an entire enterprise, understanding these levels is essential to building the kind of operating system that consistently fulfills commitments to customers and engages people in meaningful improvement.
Level 1: The Specific Problem – Understanding What Happened
The first level focuses on the event itself. What occurred? Why did it happen? What conditions or actions led to the problem? This is the level most teams are familiar with, and it often receives the most attention. The goal is to prevent this particular issue from happening again.
The most effective organizations rely on structured problem-solving methods. Tools such as Root Cause Analysis, 5 Whys, or A3 thinking help teams avoid jumping to conclusions or settling for superficial explanations. The aim is to understand the mechanisms behind the problem, not to find someone to blame.
At this level, countermeasures must be irreversible. Temporary fixes—workarounds, reassigning staff, redoing the work, issuing reminders—do not prevent recurrence. They simply restore flow in the moment. True countermeasures eliminate the root cause and redesign the process so the problem cannot reappear in the same form.
Standardized work plays a crucial role at this level. When a process is documented, taught, maintained, and followed, variation decreases. Stability increases. Errors become visible rather than hidden. And teams gain clarity about what should happen versus what actually happens, which is essential for effective problem-solving.
Addressing the specific problem is necessary, but it is not sufficient. Many organizations stop here, believing they have achieved resolution when, in reality, they have only addressed one instance of a much broader issue.
Level 2: The Detection Problem – Understanding Why It Was Not Found Earlier
Even when a specific problem occurs, the impact can be minimized if the organization detects it quickly. Many failures become harmful or expensive not because they occur but because they go unnoticed until it is too late.
This is the second level: the detection problem.
Every organization needs systems that surface abnormalities immediately. These systems can take many forms—visual controls, real-time monitoring, alerts, quality checks, leader standard work, and daily huddles. Their purpose is simple: reveal problems early so teams can respond before consequences grow.
A robust detection system does not eliminate problems at the source. Instead, it limits their impact and accelerates learning. It creates the conditions for early intervention, allowing teams to analyze issues before they propagate. And in many cases, strong detection systems reveal patterns and trends that would be invisible if teams focused solely on individual events.
Detection work is often underestimated. Leaders sometimes assume that reducing variation or improving training will eliminate the need for detection. But even in highly mature systems, problems still occur. Detection systems represent the safety net—the organizational immune system—that prevents small errors from becoming large failures.
Organizations that invest in real-time visibility—rather than relying on delayed reports or retrospective analysis—are better positioned to maintain reliability, protect customers, and build momentum in improvement work.
Level 3: The Systemic Problem – Understanding Why the System Allowed the Problem to Occur
The deepest and most powerful level of problem-solving examines the system itself. At this level, the question shifts from “what happened” to “why does our system allow this type of problem to occur?” When the organization learns to ask this question consistently, it moves from reactive problem management to proactive operational design.
Systemic problems involve policies, workflows, decision-making structures, accountability, culture, and leadership behaviors. They often reflect unclear ownership, inconsistent standards, misaligned priorities, inadequate training, or the absence of a management system that supports daily problem-solving.
Culture matters deeply at this level. Organizations that tolerate workarounds, reward heroics over process discipline, or fail to create psychological safety for reporting issues will inevitably experience recurring failures. Without deliberate attention to these systemic factors, no amount of frontline problem-solving can lead to sustained improvement.
Systemic problem-solving often requires cross-functional work. Most serious failures originate not within one department but in the handoffs and interdependencies between them. Addressing these issues requires collaboration, patience, and a willingness to challenge long-standing assumptions about how work should be organized.
Leadership engagement is essential. Leaders must model curiosity, support structured problem-solving, and reinforce routines that build discipline. Without this engagement, systemic issues remain unaddressed, and the organization remains vulnerable to repeated failures.
Integrating the Three Levels into Daily Work
The real power of this framework emerges when organizations integrate all three levels into their operating system. Each level reinforces the others.
The specific level offers immediate resolution. The detection level prevents escalation. The systemic level prevents recurrence at scale.
When used together, these levels shift the organization from reactive to proactive, from episodic improvement to continuous learning, from isolated fixes to system-wide reliability.
Integrating the three levels requires:
- Clear expectations for how teams respond to problems.
- Standardized routines for problem-solving and follow-up.
- Daily management systems that make abnormalities visible.
- Leadership behaviors that prioritize learning over blame.
- A culture of curiosity, transparency, and shared accountability.
Organizations that build this capability see dramatic improvements in quality, flow, safety, cost, and employee engagement. They become more resilient in the face of challenges and more agile in adapting to new demands.
Tools That Support Multi-Level Problem-Solving
Several proven Lean tools strengthen an organization’s ability to work at all three levels:
- 5 Whys encourages deep inquiry into root causes and system conditions.
- A3 thinking provides structure and alignment for complex problems.
- Visual management surfaces abnormalities in real time.
- Leader standard work embeds problem-solving into daily routines.
- Daily huddles support communication, reflection, and follow-up.
- Standardized work stabilizes processes and reduces variation.
These tools are not standalone solutions. They work best when integrated into a cohesive management system grounded in purpose, process, and people.
Building a Culture That Strengthens Problem-Solving Capability
Tools alone cannot transform an organization. What makes problem-solving sustainable is the culture leaders cultivate. Psychological safety encourages teams to speak up. A learning orientation ensures that problems are treated as opportunities, not failures. Collaboration ensures that departments share insights rather than operating in isolation. Discipline ensures that standard work is followed, so deviations become visible and solvable.
Organizations that consistently solve problems at all three levels create a virtuous cycle of learning. Their people become more capable. Their systems become more reliable. Their customers receive better outcomes. And their leaders gain confidence that daily operations are aligned with the organization’s strategic intent.
Key Takeaways
- Containment is helpful but insufficient.
- Detection prevents problems from becoming crises.
- Systemic solutions build long-term reliability.
- All three levels must be integrated for sustainable improvement.
- Leadership engagement is essential for capability building.
Reflection and Action
Consider the problems your organization has faced in recent months. Were they resolved only at the specific level? Are your detection systems revealing issues early enough to prevent harm? Do systemic factors continue to enable recurring failures? Are leaders consistently coaching problem-solving? Are lessons learned being shared across departments?
If the answer to any of these questions is no, then it may be time to rethink—and redesign—how your organization approaches problem-solving. When teams learn to operate at all three levels, they gain the capability to deliver predictable results while building a culture of continuous improvement.
If you’d like help strengthening your problem-solving capability or integrating multi-level problem-solving into your management system, I’d be glad to support you.
Comments