Who Owns the Check?
Why Food Manufacturers Need to Stop Building Safety Nets and Start Building Accountability
I spent eight years as QA Director at Aldi GB and Ireland. Of everything I took away from that time, the thing I keep coming back to is not a system or a specification. It is a way of thinking about people.
Aldi runs on a version of Herzberg's two-factor model. Frederick Herzberg argued that the things which stop people being unhappy at work (pay, conditions, policy, supervision) are not the same as the things that make them want to do the job well. The real motivators are responsibility, achievement, recognition and the work itself. Aldi took that seriously in a way I have not seen elsewhere. Every person has a role. The role has a clearly defined task and the expectation is that they own it.
The consequence, which surprised me at first, is that a leader stepping in to do someone's job is treated as a problem, not as helpfulness. When a manager takes over, they “take back the responsibility”. The person is no longer accountable for the outcome, because somebody else has just demonstrated that they are. It is disempowering, and over time it is demotivating. Good leaders at Aldi set the expectation and the way of working, then got out of the way. The caveat is when there is an emergency, then the leader should step in to support the employee and recover the situation, protecting the business. After the issue has been resolved then the leader can provide constructive feedback, understand any training needs and clarify expectations in the role.
What this looks like in a Food Factory
I now spend my time in the businesses that supply retailers, and I see the opposite pattern far more often than I would like.
It usually starts innocently. A line operative misses a metal detector check, so a supervisor is asked to verify the checks. A supervisor misses something, so QA starts sampling the paperwork. QA misses something at audit, so the technical manager signs everything off personally. At every step, someone senior has quietly taken back responsibility, and at every step the person who was supposed to own the task has learned that their check does not really matter, because somebody else will catch it.
Then within a year or two the culture has shifted. Line teams do their checks because they are told to, not because they own the result. Supervisors push decisions up rather than making them. Managers push them further up and eventually the norm is that the most senior person in the building makes every decision of consequence, because that is what everyone has come to expect. The organisation has become a pyramid of fallback checks, and the people at the bottom of it have been told, in effect, that they are not trusted.
This is how QA becomes QC again. Quality assurance is meant to be the discipline of building processes that produce the right result first time, with the people doing the work owning that result. Quality control is inspecting output to see whether it is acceptable. When line teams abdicate responsibility for doing their checks correctly, a "checker" becomes a valid job. The business then pays for the same check twice and gets less assurance than it had before, because the first check has stopped being done properly.
The management themes underneath
Reading back over that pattern, I think there are five themes worth naming.
Responsibility is a motivator, and taking it away has a cost. Herzberg was right. Every time a manager steps in, the message received is not "I am helping". It is "you cannot be trusted with this".
Fallback checks create the failures they are designed to catch. A second check does not add to the first. It replaces it. People rationally stop investing effort in a check they know will be repeated. In one example people in a factory were paid for the responsibility of completing a check, botched it and it was given back to QA (in reality QC) but kept on receiving the pay. So in effect were paid for failure.
Decisions drift upward unless leaders actively push them back down. Escalation feels safe for the person escalating and flattering for the person receiving it. Neither of those is a reason to allow it.
Clear expectations are the alternative to supervision. Aldi does not run its stores with a supervisor watching every till. It runs them with a precise, well communicated way of working that everyone understands and is expected to deliver, day in day out. There is a clear way of communicating routinely that cascades to all staff across the business – filtered based on role responsibilities.
Communication failures are accountability failures in disguise. When people do not know exactly what is theirs, they cannot own it, and they will quite reasonably wait for someone to tell them.
Lean got here first
None of this is new to anyone who has worked with lean manufacturing, and it is worth saying so, because the food industry has borrowed Lean's tools far more readily than its principles.
Toyota's idea of jidoka, building quality into the process so that problems are caught at source by the person doing the work, is the direct opposite of the "checker" model. The andon cord exists so that the operative stops the line, not so that a supervisor decides whether the operative was right to. Deming's fourth point told management to cease dependence on inspection to achieve quality. Standard work, properly done, is a clear expectation written down and owned by the people who perform it, not a document QA produces to satisfy an auditor. And in lean terms, a duplicated check is over-processing, one of the classic wastes. It costs labour, it costs time, and it delivers nothing the customer would pay for.
The principle underneath all of it is respect for people. Not the poster on the canteen wall, but the operational assumption that the person closest to the work is the person best placed to control it, and should be trusted and equipped to do so.
What a 21st century food business should aspire to be
If I try to describe the organisation I would want to build, or help a client build, it looks something like this.
It is self-organising at the level of the task. Every role has a defined purpose, the standards for that role are explicit, and the person in it is expected to deliver without being watched. Whether the workforce is unionised or not makes no difference to this. A union agreement can define pay, hours and grievance procedures. It cannot define whether an operative cares about the result of their metal detector check, that comes from how they are led.
It runs true QA rather than quasi QC. The technical function designs the process, sets the standard, trains, verifies by exception and investigates when something goes wrong. It does not sit at the end of the line re-doing what the line operative was supposed to do. Verification is a sample and a challenge, not a repeat.
It pushes decisions to the lowest competent level, Line Leaders decide line things, Supervisors decide supervisory things, Managers decide managerial things. The site director hears about it afterwards, if at all because it is managed at the right level of responsibility.
It treats the whole business as the unit of optimisation. A duplicated check on the line, a second sign-off by technical and a third review at Group/Head Office are each locally sensible and collectively wasteful. Running thoughtfully for the good of the whole business means removing the fallbacks and investing the saving in making the first check reliable. That is where the real cost saving and efficiency sits, not in headcount reductions, but in taking out the work that only exists because nobody trusted the work before it. When something fails, the default should not be to put another check in place by someone else. It is to understand the reason for the failure and correct it source.
Why this matters more now than it did
There is a practical reason this is becoming urgent rather than merely desirable. Food safety and ESG are converging into a single compliance landscape. The EU Deforestation Regulation is the clearest example. It requires operators placing cocoa, coffee, palm oil, soya, cattle products, rubber and wood on the EU market to demonstrate that those commodities are deforestation free and legally produced, with geolocation data down to the plot of land, and it carries penalties that can reach a meaningful percentage of turnover. Alongside it sit corporate sustainability reporting, packaging and extended producer responsibility, Scope 3 emissions data that retailers are now demanding from suppliers, and the ongoing tightening of retailer codes of practice.
Every one of these requirements depends on data that originates at the front line, in the goods-in office, the intake check, the batch record, the supplier approval file. If the person completing that record does not own its accuracy, no amount of checking further up the chain will make it reliable, and the business will discover this in front of a regulator or a retail technical manager rather than in its own review. You cannot inspect your way to a compliant EUDR due diligence statement. The information either comes in right first time or it does not.
Businesses that have built accountability into their front line will absorb these requirements as an extension of how they already work. Businesses that have built a pyramid of checkers will find that every new requirement adds another layer to the pyramid, another cost and another point of failure.
The uncomfortable bit for leaders
The hardest part of all this is not the operatives. It is the managers, stepping in feels productive and escalation feels safe. While signing things off personally feels like control. Letting go of all three requires a leader to believe that the way of working they have set is good enough to trust, and to accept that when it fails, the answer is to fix the way of working rather than to add themselves as the fallback.
That is what I saw work at Aldi, and it is what I now try to bring to the manufacturers I work with. If you recognise your own business in the pyramid I described, I would be glad to talk about how to start dismantling it.
