Every plant I’ve worked in has a dashboard. Reds and greens, trend lines, a KPI board someone updates every morning. And every plant I’ve worked in has at least one leader who thinks that dashboard is the plant.
It isn’t. The dashboard is a summary of the plant, written by whoever had time to fill it in, at whatever moment they happened to check. Gemba — going to the actual place where the work happens — is how you find out what the dashboard left out.
What the Report Can’t Tell You
A report tells you a machine was down for 22 minutes. It doesn’t tell you the operator improvised a fix that’s going to fail again next week, or that they didn’t call it in because the last three times they flagged something, nothing happened. You only get that by standing there and asking.
Three Questions I Ask on Every Walk
- What’s slowing you down right now that isn’t on anyone’s report?
- What did you have to work around today?
- If you could fix one thing without asking permission, what would it be?
None of these show up in a KPI review. All three have led directly to real fixes.
The Habit, Not the Event
The mistake I made early in my career was treating Gemba walks as an event — something scheduled, announced, prepared for. People clean up for an event. They don’t show you the real state of things; they show you the state they think you want to see.
Gemba only works as a habit. Unannounced, frequent, and short. Fifteen minutes, three times a week, beats two hours once a quarter every time.
Your dashboard will keep telling you what happened. Gemba is the only way to find out why — and what to do about it before it happens again.
The Operations Bridge 
Leave a comment