The Lesson Can Be Shared. The Vulnerability Must Be Investigated Locally.
When another organization experiences a failure, the question is not whether our system is the same, but whether it could produce the same outcome. Discover why lessons can be shared, but vulnerabilities must be investigated within the actual conditions of each system.
PROBLEM SOLVING
The Lesson Can Be Shared. The Vulnerability Must Be Investigated Locally.
When a serious failure occurs in a hospital, a manufacturing plant, or any other organization, it is natural to wonder whether something similar could happen in our own system.
We review the report. We compare procedures. We examine the root cause identified by the other organization and try to determine whether it exists in ours.
If our process is different, we may feel reassured.
But perhaps we are asking the wrong question.
The question should not be:
Is our system the same as the system where the failure occurred?
It should be:
Given our own conditions, could our system produce the same outcome?
The difference may appear subtle, but it changes the entire investigation.
The same outcome does not require the same cause
Two hospitals can experience the same adverse event without following the same procedure. Two manufacturing plants can produce the same defect without using the same technology. Two teams can lose the same information even though their work processes differ.
The outcome may appear identical. The path that led to it may be entirely different.
Every system has its own combination of standards, decisions, workloads, interfaces, assumptions, and abnormal conditions. Even when two organizations appear to perform the same work, their local circumstances are rarely identical.
That is why importing another organization’s root cause can create a false sense of security.
We might check whether that cause exists in our system, confirm that it does not, and conclude that the problem could never happen here.
Yet our system might arrive at the same outcome through a different path.
Learning from others does not mean copying their conclusions
This does not mean external reports are useless. Quite the opposite: sharing experiences prevents organizations from having to learn exclusively through their own mistakes.
But an external lesson should begin an investigation, not end it.
Another organization’s incident does not give us our root cause. It gives us a possibility worth examining.
Instead of asking only whether we use the same procedure, the same equipment, or face the same failure, we might ask:
What would have to happen here for us to reach the same outcome?
Which barriers should prevent it?
Do those barriers work under real operating conditions?
What happens when workloads increase, information is missing, or abnormal conditions arise?
Which local assumptions are we accepting as safe without verifying them?
These questions do not attempt to reproduce someone else’s investigation. They use another organization’s experience to examine our own system.
Barriers operate under real conditions
We often evaluate a system by observing how it is supposed to work. We review the procedure, confirm that a control exists, and verify that someone is responsible for carrying it out.
But a barrier is not effective simply because it appears in a document.
Its ability to prevent an unwanted outcome depends on the conditions under which it must operate: available time, accessible information, clear signals, workload, coordination between departments, and the response to exceptions.
A barrier that works during normal operations may weaken when several conditions change simultaneously. This is precisely where an external experience can help: not by telling us what our cause is, but by reminding us that an outcome that once seemed unlikely is possible.
Local investigation must explore that possibility at the gemba, following the actual work and understanding how the conditions within our own system interact.
Share the lesson. Investigate the vulnerability.
The identified causes belong to the conditions of the system in which the failure occurred. They cannot automatically be transferred from one organization to another.
But the observed outcome can still serve as a useful warning.
We can learn from what happened elsewhere without assuming that its explanation also applies to us. We can acknowledge that our processes are different without using that difference as a reason to stop investigating.
The most useful question is not whether our system is the same.
It is whether our system, under its own circumstances, could produce the same outcome.
The lesson can be shared. The vulnerability must be investigated locally.
Do not ask whether your system is the same. Ask whether it could produce the same result.