Mapping Where Quality Problems Are Created Across a System
When a quality problem is found, it is tempting to fix it at the point where it was noticed. That response addresses the symptom, but it does not always address where the problem was created. A deviation raised on the shop floor may have originated in an unclear handover between teams, a decision right that was never assigned, or a step that assumed information which was not actually available at the time.
Why the point of detection is rarely the point of origin
Work moves through people, process, information, and technology in sequence. A gap introduced early in that sequence, such as an ambiguous responsibility or an assumption that no longer matches practice, often only becomes visible once it reaches a later, more scrutinised step. Treating the later step as the whole problem can lead to a fix that does not prevent the same gap recurring somewhere else.
A practical way to trace the path
Tracing where a quality problem was created does not require a large-scale audit. It can start with a small number of practical questions applied to one recurring issue:
- Where did the information or decision that led to this problem first enter the process?
- Who was responsible for that step, and was that responsibility clearly assigned?
- Did the system or procedure in place at that step reflect how work actually happens?
- What would have made the gap visible earlier, before it reached the point of detection?
Answering these questions with the people who actually do the work, not only the people who review it afterwards, tends to surface where the real gap sits.
Use the pattern, not just the incident
A single incident review can miss a repeating pattern. Reviewing several related issues together often reveals that they share the same point of origin, even when the visible symptom looks different each time. That shared origin, not the individual incident, is the more useful place to make a proportionate change.
Where this leads next
Once the point of origin is understood, the next practical question is usually how to improve the surrounding flow without weakening the controls that are already working. That question is covered separately in improving flow without weakening control .
This page is part of systems thinking for regulated operations , which explains how people, process, information, technology, decisions, and feedback work together across a regulated operation.
Discuss where your quality problems are created
If the same type of quality issue keeps recurring in different forms, a discovery conversation can help trace it back to its actual point of origin.
Book a discovery call to discuss a recurring quality issue in your operation.