The real quality problem? What you let slip by every day
A seal that leaks a little, a label that peels off, a tool that’s never in its place, a value that flirts with the limit without crossing it. Nothing serious, so nothing is reported. Until the day one of these little things becomes a deviation.
Bird’s pyramid, pharmaceutical version
In safety, everyone knows Bird’s pyramid: for every serious accident, there are dozens of minor incidents and hundreds of near misses. Most sites have a method for reporting and handling these risky situations.
In Quality, that’s rarely the case. An event is only handled when it presents a risk to the product or the patient, in other words when it has already become a deviation. That’s the very definition of reactive Quality. Yet when a deviation occurs, it’s often because dozens of smaller warnings weren’t taken into account before it.
Why weak signals don’t get reported
- They seem unimportant: “it’s probably nothing, and I’m already running late”.
- There’s no simple channel: opening a deviation for an irritant seems disproportionate, so nothing is said.
- Reporting has never changed anything: when a warning goes unanswered, the next one is never raised.
- Fear of blame: reporting a drift sometimes means admitting a mistake.
Capture: a simple means, not yet another form
The system has to be simpler than saying nothing: a short sheet, a board near the line, a few words at the team huddle. Task observations and the discussions in “15 minutes for Quality” are also excellent sensors, provided you have created a climate where people can speak without fear.
Handle: quickly, simply, visibly
A weak signal shouldn’t trigger a CAPA. It calls for a quick, low-cost action, decided as close to the shop floor as possible. What matters is showing that it has been heard: the signal reported, the action carried out, feedback given to the person who raised it. That’s what makes people want to do it again.
Manage, without drowning
Setting up weak signal management takes stamina. The pitfalls are well known: too many signals at the start, then not enough; actions that don’t follow; results never communicated. A few rules help:
- group signals by theme to bring out trends;
- track a simple indicator, such as the number of signals handled in the week;
- regularly celebrate the improvements achieved thanks to reports.
What it changes
Once in place, the effect is felt quickly: practices that improve, irritants that disappear, and fewer deviations. Above all, teams change their stance: they no longer endure problems, they anticipate them. That’s exactly the move from a culture that endures to a culture that anticipates.
