Audits and Gemba walks look almost identical from a distance. Someone senior walks the floor, looks at things, writes things down, and something happens afterwards. The difference is entirely in what the floor believes is being evaluated.
In an audit, the area is being evaluated. In a walk, the process is. Everything else follows from that.
The staging problem
If people believe their area is being scored, they will make the area look good. This is not dishonesty, it is competence — anyone who does not do it is disadvantaging their own team.
The result is that you see a version of the floor that exists for about ninety minutes a month. The tote that normally blocks the aisle is moved. The workaround jig is in a drawer. The problems you most needed to see are precisely the ones that get tidied away before you arrive.
An inspection gets you a clean floor. A walk gets you the real one. You cannot have both from the same visit.
Six tells
Look at your own walk and ask which column it falls in.
- Announced or not? A scheduled inspection is fine. A scheduled walk should be routine enough that nobody bothers preparing.
- Does anything get a score? Scores attach to areas. Areas have owners. Owners optimise for scores.
- Who talks most? If it is you, it is an inspection. On a walk, the person doing the work should be doing most of the talking.
- What gets recorded — findings or observations? "Non-conformance in bay 4" versus "the label is unreadable under these lights". One assigns blame, the other describes a problem.
- Who owns the follow-up? If every action lands on the area supervisor, you are auditing. Real fixes often belong to maintenance, engineering or procurement.
- What happens to a repeat? On an audit, a repeat finding is a failure by the area. On a walk, a repeat is information that the first fix addressed a symptom.
You still need audits
None of this is an argument against auditing. Safety, regulatory compliance and quality systems need real inspections with real consequences, and pretending otherwise is how people get hurt.
The mistake is running one activity and hoping it does both jobs. It cannot. The behaviours that make an audit effective — announced standards, scoring, escalation — are exactly the behaviours that make a walk produce a staged floor.
Run both. Keep them visibly separate. Different names, different paperwork, ideally different people, and never let a walk observation feed an audit finding. The first time it does, everyone learns, and your walks stop working permanently.
The signal you are on the right side
One question tells you almost everything: does anyone show you a problem you would not have found?
An operator pulling you aside to show you the jig that takes three tries to seat is not something that happens on an inspection. It happens when people have concluded that showing you a problem leads to the problem being fixed rather than to their area being marked down.
If that never happens on your walks, the walk is being read as an audit, whatever you are calling it.