Using Gemba Walks to Improve Operations
Gemba is a Japanese word that means “the actual place.” A Gemba Walk is when a leader goes to the floor — the kitchen, the serving line, the storage room, the dish room — to observe work as it really happens and talk to the people doing it.
Most operational problems can’t be seen from a dashboard or a manager’s office. Gemba walks exist to close that gap. InspectU’s Gemba audit template gives the walk a structure so findings are documented and followed up on, not just discussed and forgotten.
When to Use It
- When you want to understand how a process actually works, not how it’s supposed to work
- When you keep seeing the same issue but haven’t figured out why
- When onboarding a new manager to a site — a Gemba walk builds real understanding fast
- As a regular leadership routine: weekly for site managers, monthly for directors
- When preparing for a major change — new menu, new equipment, new layout
Example Questions
| Example Question | Response Type | Why It Matters |
|---|---|---|
| Is the process being observed clearly defined for this walk? | Yes / No | Focused walks surface more useful findings than open-ended ones |
| Are employees following the expected steps, recipe, or SOP at the time of observation? | Yes / No / N/A | Process compliance is best verified in the moment |
| Does work move smoothly through this area, or are there visible delays, congestion, or backtracking? | Yes / No / N/A | Flow problems are often invisible unless you’re watching |
| Are there visible examples of waste: overproduction, waiting, excess motion, or rework? | Yes / No | Waste identification is a core Gemba skill |
| Do employees have what they need to perform the work without workarounds? | Yes / No / N/A | Workarounds mean the system isn’t supporting the people |
| Were actionable improvement opportunities identified during this walk? | Yes / No | If nothing was found, try a different area or a more focused walk |
Questions to Ask During the Walk
Gemba walks are about listening, not just observing. These prompts help surface real barriers:
- “What’s making this step harder than it should be?”
- “Where do delays or repeat problems happen most often?”
- “What are you currently working around to get the job done?”
- “What changed recently — staffing, menu, equipment, volume?”
- “What one thing would make this area work better today?”
What Good Looks Like
Signs of a strong Gemba walk The walk has a clear focus. Observations are specific and tied to a process step. Employee feedback is captured, not just noted. Every significant finding has an action item with an owner and a due date. The next walk includes a check on whether last time’s actions were completed. |
What Happens After
- Findings are logged in InspectU’s Observation and Action Log, tagged by issue type and impact level
- Each action item is assigned to a named person with a due date and tracked to closure
- Trend tags (Safety, Quality, Flow, Training, Equipment, etc.) help you see which categories surface most often across walks
- Over multiple walks, patterns emerge that guide training decisions, process redesigns, and equipment investments
| Best frequency | Weekly for site managers; monthly for directors and district managers |
| Who runs it | Managers, directors, team leads, or anyone in a leadership role |
| Time to complete | 30–60 minutes for a focused area walk |
| Key output | Observation log, issue tags, action items with owners and due dates |