The best process improvement tool isn't software. It isn't a spreadsheet. It isn't a framework with a clever acronym. It's your feet.
Gemba is a Japanese word meaning "the actual place" — the place where work happens. A gemba walk is exactly what it sounds like: going to where the work is done, observing it firsthand, and learning from the people who do it.
It sounds almost insultingly simple. That's why most leaders skip it. And that's why most improvement efforts miss the mark.
Why Gemba Walks Matter
Every process exists in two forms: the way people think it works and the way it actually works. Conference room discussions, flowcharts drawn from memory, and reports based on system data all describe the first version. Only direct observation reveals the second.
The gap between these two versions is where waste lives.
Workarounds nobody documented. The operator who jiggles the machine handle a specific way because it jams otherwise. The nurse who writes patient notes on paper first because the EHR is too slow during rounds. These workarounds are invisible from a desk.
Waiting that doesn't show up in data. Systems track processing time. They rarely track the five minutes someone spends looking for a tool, waiting for an approval, or walking to a different building for a form.
Friction between steps. Handoffs between departments, shifts, or systems create friction that's felt on the floor but invisible in process maps.
How to Walk a Gemba
A gemba walk is not a management inspection. It's not an audit. It's not a chance to catch people doing things wrong. Get this wrong and you'll destroy trust and learn nothing.
1. Go with questions, not answers. You're there to learn, not to fix. Bring curiosity: "What makes this step difficult?" "What would you change if you could?" "Where do you spend time waiting?"
2. Observe before asking. Watch the process for a full cycle before interrupting. Note what you see — the sequence of steps, the movements, the pauses, the interruptions. Your observations are data.
3. Respect the expertise. The person doing the work knows more about that work than you do. They've adapted to problems you don't know exist. Listen more than you talk.
4. Focus on the process, not the person. "Why does this step take so long?" is a process question. "Why are you so slow at this step?" is a blame question. One generates insight. The other generates resentment.
5. Take notes, not action. Write down what you observe and what you hear. Don't make changes on the spot. Improvements should come from analysis and collaboration, not from a manager's drive-by observation.
What to Look For
Train your eye on the eight wastes (DOWNTIME):
- Defects — Rework, corrections, errors being caught and fixed
- Overproduction — Work being done ahead of need or in excess
- Waiting — People idle, materials queued, approvals pending
- Non-utilized talent — Skills and ideas not being leveraged
- Transportation — Unnecessary movement of materials or information
- Inventory — Piles of work-in-progress, full inboxes, stacked palettes
- Motion — Unnecessary physical movement by people
- Extra processing — Steps that add effort but not value
From Observation to Action
A single gemba walk generates observations. Regular gemba walks generate patterns. Those patterns point to systemic issues that no dashboard or report would reveal.
After your walk:
- Compile your observations. What did you see? What surprised you?
- Identify themes. Are the same wastes appearing across different areas?
- Prioritize. Which issues have the biggest impact on flow, quality, or cost?
- Collaborate. Bring your observations back to the people you watched. Validate your understanding. Co-develop solutions.
- Model the change. Before implementing, simulate the proposed improvement. Quantify the expected impact.
Make It a Habit
The leaders who get the most from gemba walks do them regularly — weekly at minimum. Not as a formal event with clipboards and entourages, but as a natural part of how they lead. Walk the floor. Watch the work. Talk to the people. Learn.
The answers to your biggest process problems are not in your inbox. They're on the floor, waiting for someone to come look.