Morsa publishes this guide. Morsa is software with an AI agent that works in your ERP, email and Teams; it follows up walk actions, and a person approves what goes out.
How a gemba walk works, step by step
Lean thinkers use “gemba” for the place where value is created, such as a factory floor, a construction site or a sales floor [1][2]. A walk is not random wandering. It has a frequency, a goal and a structure [2]. A manager or a supervisor walking their own area counts. Six steps:
Pick one theme. A process, a line, or a topic such as safety, quality or downtime [3].
Tell the team. Schedule it and say why, so nobody thinks they are in trouble [4][5].
Follow the flow. Walk one product or order from start to finish, across departments. James Womack of the Lean Enterprise Institute suggests bringing everyone who touches the process and discussing purpose, process and people [1].
Watch first, then ask. Ask open questions. Do not fix or correct on the spot [4][5].
Write it down. Notes and photos show patterns across walks [4][5].
Follow up. Turn what you saw into actions people can see happen [3].
Gemba walk checklist: questions to ask
Take 8 to 10 of these, not all. Most are adapted from Fabrico’s and SafetyCulture’s lists [3][4]; the last two are ours.
What are you working on, and how do you know it is going well?
What is the standard for this task, and is it being followed?
How did you learn this task?
What makes this task harder than it should be?
Where do delays, defects or rework usually happen?
What happens if equipment, tools or materials are not there?
If you had it your way, how would you do this task?
What would make your job safer or easier?
What did you ask for last time that you still do not have?
What is this process waiting for, and what is waiting for it?
Add the 5 Whys when you find a problem (root cause analysis) [4].
Gemba walk template: a log for what you find
Set up a sheet with these columns: date, area and theme, what I saw, what I asked, action, owner, due date. A filled-in row:
12 November, Press 4, theme changeovers. Saw the operator walk to the tool crib twice per changeover. Asked what makes this harder than it should be. Action: keep a die-set cart at the press. Owner: tooling lead. Due: 26 November.
At the next walk, open the log first and ask about every action that is open. That is the part most walks skip.
Your first walk, next week
Pick one line and one theme, such as a stop-heavy station or changeovers.
Book 30 minutes and tell the team why you are coming.
Bring the log columns and three or four of the questions above.
Write two actions, each with an owner and a date.
At your next walk, open the log before you do anything else.
Gemba walk vs audit vs walking around
Practice | Purpose | Structure |
|---|---|---|
Gemba walk | Understand how work really goes; people-focused | Planned, with a theme and a frequency [2] |
Audit | Check compliance with a standard | Formal, finds faults |
Management by walking around | Be visible | Typically not planned or structured [2] |
Augmentir, a software vendor, says gemba walks are informal and collaborative, where formal audits look for faults [5].
How plants and distributors use it
There is no fixed rule on frequency. Many sites walk weekly and keep it short; consistency matters more than length [3]. SafetyCulture describes one site where the most senior person and the department managers walk the production boards at 9 a.m. every day, and any discussion over 3 minutes gets an owner and a follow-up meeting [4].
Two examples of ours. A plant manager walks Line 2 every Tuesday for 30 minutes on one theme, with the maintenance lead. A distributor’s operations manager follows one customer order from receiving to the shipping dock and asks each person where it waited.
Common gemba walk mistakes
No theme. You see everything and fix nothing. Pick one.
Unannounced. People feel inspected and show you the tidy version [4].
Correcting people on the spot. You get compliance, not the truth. Ask instead.
No notes. By Friday you remember two things.
Actions without an owner and a date. Nothing changes, and people stop talking to you.
Judging people, not the process. The aim is the process [5].
Pointing the walk at the right line and closing the loop
The walk is only as good as where you point it and what happens after. Morsa does both ends:
Its morning brief shows plan against actual per line, with the reason for each stop, so the walk starts at the line that missed.
After the walk, you send your findings in Teams or text. It turns each into an action with an owner and a due date, which the manager approves.
It follows each action to done, nudges the owner from your mailbox, and lists open ones in the next brief.
To see it on your plant, book a 30-minute walkthrough.
Related terms
Operations glossary: every term.
Production monitoring: live data to decide where to walk.
Andon: the signal that calls for an immediate walk to the line.
Takt time: the pace you check against on the walk.
Lead time: a walk that follows one order shows where its days go.
Sources
Lean Enterprise Institute, Gemba Walk: https://www.lean.org/lexicon-terms/gemba-walk/ (read 12 November 2026)
Wikipedia, Gemba: https://en.wikipedia.org/wiki/Gemba (read 12 November 2026)
Fabrico, What Is a Gemba Walk? Purpose, Steps, and Questions (a vendor guide): https://www.fabrico.io/blog/gemba-walk/ (read 12 November 2026)
SafetyCulture, Gemba Walk: Meaning, Process, and Examples: https://safetyculture.com/topics/gemba-walk/ (read 12 November 2026)
Augmentir, Gemba Walk in Manufacturing (a vendor glossary page): https://www.augmentir.ai/glossary/gemba-walk-manufacturing (read 12 November 2026)

