Backlog · Deviations
It clears very well with reinforcements: a few months of sprint, a catch-up plan, and the counter comes down. Then it goes back up. Because a queue says one thing and one thing only: what comes in exceeds what goes out. And nobody has touched what comes in.
In > out
A queue is the accumulated difference between an inbound flow and an outbound one. Any action that changes neither produces a temporary effect, by definition.
Hence the only useful question to ask in front of a backlog: how many deviations do you open per month, and why that number? Until it is asked, any clearance plan is a plan to exhaust the team — effective for six months, then costly for a long time, because it plants the idea that the problem was how fast people work.
The belief that costs you
"We need two more people."
Sometimes true, and never sufficient. Two reinforcements increase the outbound flow, which is necessary when the queue threatens regulatory deadlines. But if 30% of your deviations come from an incoherent document set and 20% are recurrences of causes never addressed, you have just recruited to absorb a problem you keep manufacturing. The return on that investment is nil at two years.
The method
You do not negotiate with regulatory deadlines, and an old file is one nobody remembers: the quality of its investigation degrades with time. So the queue is handled fast, by risk-based triage, grouped treatment of files sharing a cause, and an explicit decision on those that call for no corrective action.
In parallel, the analysis of what comes in: what share is recurrence, what share is documentary, what share should never have been opened. These three families are handled differently, and that is where the lasting result is won. Without this second programme, the first is a cycle that will repeat.
The order matters: clear the queue, then fix what produced it — never the other way round. Starting with the cause while the queue runs puts the site at regulatory risk, and loses the credit needed for the second programme.
Our conviction
A deviation backlog is not a quality topic: it is an industrial one. It immobilises batches, lengthens release lead times, ties experts up in administration and ends up hitting customer service. Presenting it as a quality resourcing problem condemns it to be arbitrated last — and therefore to come back.
What you gain
Deadlines
Meeting regulatory closure deadlines stops being an end-of-month exercise. It is the first thing an inspector looks at, and the easiest to evidence objectively.
Analysis quality
A team that is no longer under water can finally run serious investigations. It is a virtuous circle: better analyses reduce recurrence, and therefore the inbound flow.
Working capital
Blocking files weigh directly on release. Every week saved on handling a blocking deviation is a week less of stock sitting in quarantine.
Frequently asked
Two days on your history is enough to separate recurrences, documentary causes, and deviations that should never have been opened.
