Gemba Walk
The practice of going to where work actually happens to observe processes firsthand and identify improvement opportunities.
Also known as: Gemba, Go and See, Genchi Genbutsu, Management by Walking Around
Category: Leadership & Management
Tags: lean, management, improvement, leadership, japanese-concepts
Explanation
A Gemba Walk (from Japanese 'gemba' meaning 'the real place') is the practice of going to the place where value is created to observe the actual work process firsthand. Rather than relying on reports, dashboards, or secondhand information, leaders go to the source.
## The philosophy
Taiichi Ohno, architect of the Toyota Production System, insisted that managers must go to the factory floor to truly understand what was happening. He reportedly drew circles on the floor and made engineers stand in them for hours, simply observing. The principle: you cannot improve what you do not understand firsthand.
## How to conduct a Gemba Walk
1. **Go to the workplace** - The shop floor, the development team's area, the customer service center
2. **Observe** - Watch the actual process without judgment or interference
3. **Ask questions** - Understand why things are done the way they are
4. **Listen** - The workers closest to the process have the deepest knowledge
5. **Show respect** - You're there to learn, not to audit or criticize
6. **Take notes** - Document observations for later analysis
7. **Follow up** - Act on what you learned
## What to observe
- **Flow** - Does work move smoothly or are there bottlenecks?
- **Waste (muda)** - Are there unnecessary steps, waiting, or rework?
- **Workarounds** - Are workers circumventing official processes? Why?
- **Problems** - What issues are workers dealing with daily?
- **Standards** - Are standard procedures being followed? Are they adequate?
## Gemba in software development
The concept translates beyond manufacturing:
- **Pair programming** - Observing how developers actually write code
- **Shadowing users** - Watching how customers use your software
- **Sitting with support** - Hearing real customer problems firsthand
- **Attending standups** - Understanding what blocks the team
- **Reviewing pull requests** - Seeing the actual code changes
## Common mistakes
- **Going to blame** - Using observations to criticize rather than improve
- **Solving on the spot** - Jumping to solutions instead of deeply understanding
- **Infrequent visits** - A one-time event rather than a regular practice
- **Staying in the office** - Trusting metrics over observation
- **Not following up** - Observing without acting on findings
The key insight of gemba is that reality often differs significantly from what reports and dashboards suggest. Direct observation reveals the waste, workarounds, and frustrations that data can't capture.
Related Concepts
← Back to all concepts