Table of Contents
A dashboard can tell you that a process missed its target. It cannot show you the form employees complete twice, the approval that waits because no one knows who owns it or the workaround quietly holding the day together. Those details live where the work happens.
A Gemba walk takes leaders to that place. They observe the process, speak with the people closest to it and understand what is helping or hindering the work. The aim is to learn before deciding what needs to change.
Done well, a Gemba walk can reveal delays, safety concerns, unclear procedures and avoidable effort that reports rarely explain. Done poorly, it becomes a leadership tour followed by a forgotten list of observations. This guide covers how to plan a Gemba walk, what to look for, which questions to ask and how to turn what you learn into action.
Key takeaways
A Gemba walk is a learning practice. Leaders observe work where it happens and speak with the people closest to the process. The aim is to understand the operating reality before proposing a change.
The process is the focus. A Gemba walk looks for unclear standards, bottlenecks, rework and unnecessary effort. It should never become an evaluation of an individual employee’s performance.
Preparation gives the walk direction. A defined theme, selected value stream and flexible Gemba walk checklist prevent the exercise from becoming an unfocused tour.
Good questions expose what reports miss. Open-ended questions help leaders understand why workarounds exist, where handoffs fail and how the documented process differs from the real one.
The walk creates value when observations lead to action. A meaningful issue needs an owner, priority, deadline and visible proof that the corrective action worked.
What is a Gemba walk?
A Gemba walk is a Lean management practice in which leaders observe a process where the work actually happens, speak with the people performing it and identify opportunities for improvement. Gemba is a Japanese word that means “the actual place” or “the real place.”
In a manufacturing business, the Gemba may be the production floor. In healthcare, it could be patient intake or discharge. In a professional services firm, it may be a client onboarding workflow. The location changes, but the principle stays the same: understand the process through direct observation and respectful inquiry.
Lean practitioner John Shook captures the approach in three short instructions:
“Go see, ask why, show respect.”
A Gemba walk creates a clearer picture of the current process. Leaders see where work waits, where employees improvise and where a seemingly minor inconvenience causes problems further downstream.
Gemba, Gemba walk and Gemba audit
These terms are connected, but they serve different purposes.
A Gemba walk may uncover a compliance problem, but its primary purpose is learning. A Gemba audit starts with defined requirements and checks whether the process meets them. Mixing the two can make employees feel inspected and reduce the quality of the conversation.
Why Gemba walks matter for operational excellence
Operational problems often become visible in results long after they first appear in the work. Gemba walks shorten the distance between leaders, frontline teams and the process they are trying to improve.
- Reports show the result; observation reveals the cause. A cycle-time report may show that approvals are late. A Gemba walk may reveal that the approver receives incomplete information or that ownership changes based on the value of the request.
- Frontline knowledge becomes part of improvement. The people performing a process know where they wait, repeat work or compensate for an unclear instruction. A productive walk gives that knowledge a route into operational decisions.
- Workarounds expose gaps in standard work. A workaround is often treated as noncompliance. It may actually signal that the documented process no longer reflects operating conditions. Comparing the real process with standard work and SOP guidance helps teams decide whether the employee or the procedure needs support.
- Small problems become visible earlier. Repeated corrections, minor delays and unofficial handoffs can look harmless in isolation. Seen across the full process, they may explain a larger quality, cost or customer problem.
- Leaders connect improvement goals with operating reality. A Gemba walk grounds operational excellence in evidence instead of assumptions.
McKinsey’s operational-excellence research found that only 21% of surveyed organizations conducted employee check-ins at least weekly. It also found that fewer than half actively involved employees in developing operational improvements. Regular Gemba walks can create a more deliberate listening and learning cadence, provided the resulting concerns receive visible follow-through. Read the McKinsey research.
Related read: What is operational excellence? Principles, examples and a practical roadmap
How to conduct a Gemba walk in seven steps
A useful Gemba walk has enough structure to remain focused and enough flexibility to follow an unexpected observation. The following seven-step Gemba walk process covers preparation, observation and follow-through.
1. Choose a purpose and theme
Begin with a specific reason for the walk. The theme may be safety, quality, customer experience, waiting time, rework, compliance or another operational priority.
A clear theme determines which process to observe, who should participate and what evidence matters. It also keeps the group from collecting a long list of unrelated issues.
Avoid choosing a conclusion before the walk begins. “Find out why invoice approvals take five days” is a useful purpose. “Prove that the finance team needs automation” already assumes the answer.
2. Select the process and follow the value stream
Choose one recurring process, customer journey or product family. Follow the work in sequence, including the handoffs between departments, systems and external participants.
For example, a client onboarding Gemba walk might begin when a contract is signed and continue through document collection, internal review, account setup and the first service milestone. Looking at only one team would hide the delays between those stages.
A value stream map can help define the route. During the walk, compare the documented value stream with the path the work actually takes.
Related read: Value stream mapping explained: Visualize, analyze and optimize your workflows
3. Decide who should participate
A Gemba walk usually includes the process owner and a small number of people who can learn from the process. Depending on the theme, the group may also include:
- Frontline employees who perform the work
- Operational excellence or continuous-improvement leaders
- Safety, quality or compliance representatives
- Subject-matter experts
- Managers responsible for adjacent handoffs
- Suppliers, contractors or external partners involved in the process
Keep the group manageable. A large leadership delegation can make the walk feel like an inspection and discourage honest feedback.
Tell employees why the walk is happening. Explain what will be observed, how notes will be used and when they can expect an update. This preparation helps build trust before the first question is asked.
4. Prepare a flexible Gemba walk checklist
A Gemba walk checklist provides prompts, not conclusions. It should guide attention without reducing the walk to a box-ticking exercise.
Before the walk, document:
- The purpose and theme
- The beginning and end of the process
- The current standard or expected result
- Recent performance signals
- People who should be consulted
- Areas or handoffs to observe
- Open-ended Gemba walk questions
- Evidence that can be captured appropriately
- The method for recording and reviewing actions
A safety walk will need different prompts from a customer-service walk. Adapt the checklist to the process and involve employees in refining it over time.
5. Observe the process and ask why
Follow the work as it moves. Resist the urge to jump straight to a solution. First understand what happens, what should happen and why the difference exists.
Look for:
- Flow: Where does work wait, stop or move backward?
- Handoffs: What information is lost when responsibility changes?
- Standardization: Are people following the documented process? If not, what makes the standard difficult to use?
- Rework: Which tasks, forms or decisions are routinely repeated?
- Motion and effort: Are employees switching systems, searching for information or entering the same data more than once?
- Customer impact: Which internal delay creates additional effort or uncertainty for the customer?
- Safety and quality: Which operating conditions increase risk or make errors more likely?
- Decision rights: Do employees know what they can resolve and what must be escalated?
The tone matters. “Why did you skip this step?” can sound accusatory. “What makes this step difficult to complete?” invites an explanation.
Frontline employees may reveal that a required field is unavailable at that stage, an approval rule is ambiguous or a workaround prevents a longer delay. Those details help distinguish a training problem from a process-design problem.
6. Capture evidence and define the next action
Notes such as “approval process is slow” are difficult to investigate. Capture enough information to make the observation specific.
Useful Gemba evidence may include:
- Timestamps
- Queue or backlog counts
- Examples of incomplete submissions
- Photos or video, where appropriate and permitted
- Employee comments
- Screenshots of system errors
- Process deviations
- Defect or rework counts
- Customer complaints or repeated questions
- Relevant SOP versions
Evidence should support learning, not surveillance. Follow privacy, safety and consent requirements when recording people, customer information or restricted operating areas.
Once the issue is understood, describe the next action clearly. A recurring defect may need a root cause analysis before the team chooses a corrective action. A simple ownership gap may only require a decision and an updated procedure.
7. Assign ownership, follow up and repeat
A Gemba walk ends when the team understands what happens next, not when everyone leaves the work area.
Every confirmed action should include:
- A named owner
- Priority or severity
- A due date or SLA
- The expected result
- Required evidence
- Current status
- An escalation path
- Proof that the action worked
Review open actions weekly or biweekly. Escalate blocked items that require funding, authority or cross-functional support. Share progress with the employees who participated in the walk, including the reasons an idea was postponed or rejected.
This feedback loop matters. People stop raising concerns when observations disappear into a spreadsheet. Visible follow-through shows that their participation led to a decision.
A regular review cadence also connects Gemba walks with continuous process improvement. Teams can study recurring themes across different walks, update their checklists and verify whether a completed action produced the intended result.
Related read: How visual management and daily huddles drive alignment and accountability
Gemba walk checklist: What to observe
The best checklist reflects the process being studied. The following snapshot provides a practical starting point.
Safety deserves its own attention. OSHA published detailed information on more than 890,000 injury and illness cases across more than 91,000 workplaces for calendar year 2023. That figure reflects the scope of OSHA’s submitted case data, rather than the performance of an individual employer. It shows how much operational evidence can exist behind a broad safety metric. Review the OSHA release.
Gemba walk questions that uncover useful answers
The strongest Gemba walk questions invite employees to explain what they experience. They begin with “what,” “why” or “how” and leave room for an answer the leader did not expect.
- Questions about purpose: What outcome is this process meant to create? Which steps contribute directly to that outcome? Which step feels disconnected from it?
- Questions about flow: Where does work wait? Which handoff creates the most uncertainty? What must happen before you can continue?
- Questions about standard work: Which steps are difficult to follow as written? What workarounds have become normal? When was this procedure last reviewed with the people using it?
- Questions about problems: What repeatedly goes wrong? What makes the issue difficult to resolve permanently? What tends to happen immediately before the problem appears?
- Questions about improvement: If you could change one part of this process, what would it be? What has already been tried? What stopped the previous solution from lasting?
- Questions about support: Which information, tool or decision would make this work easier? What do you need from the previous team in the process?
- Questions about customers: Where do customers wait, repeat themselves or ask for clarification? Which step creates the most avoidable effort?
Avoid leading questions such as, “Would automation fix this?” The question narrows the discussion before the cause is understood. Ask what makes the work difficult first. Evaluate solutions after the evidence is clear.
Gemba walk examples across industries
Gemba walks began in Lean manufacturing, but the practice applies wherever people create value through a repeatable process.
Customer-facing Gemba walks can connect operational observations with customer satisfaction. A repeated request for the same document may look like an internal inconvenience. For the customer, it creates effort, uncertainty and less confidence in the service.
The point is to observe the full experience. A process can meet its internal SLA and still frustrate the customer if updates are unclear or the same information is requested more than once.
Common Gemba walk mistakes and how to correct them
A few predictable mistakes can turn a useful learning practice into an uncomfortable tour or an action list no one owns.
- Treating the walk like an inspection. Employees become cautious when they expect to be evaluated. Explain the learning objective and focus questions on the process.
- Looking for individual mistakes. Ask what conditions allowed the error or workaround to occur. This keeps attention on the system and produces more useful corrective actions.
- Starting with a predetermined solution. Observe the process and understand the cause before choosing technology, training or policy changes.
- Following the checklist mechanically. Use the checklist to guide attention. Follow an unexpected answer when it reveals an important problem.
- Bringing too many senior leaders. A smaller group creates a more natural conversation and reduces disruption.
- Solving every problem during the walk. Record the issue and investigate the cause unless an immediate safety response is required.
- Collecting more actions than the team can manage. Prioritize issues by risk, customer impact and operational value. A short list of completed actions is more useful than a long backlog.
- Failing to close the loop. Tell participants what changed, what remains under review and why a suggestion was not adopted.
Turn Gemba walk observations into accountable improvements
Observation starts the improvement cycle. The action log connects what the team saw with what someone must do next.
The proof-of-closure column prevents an action from being marked complete simply because a task was performed. Updating an SOP is an activity. Showing that employees use the new version and that the original error has declined is evidence of improvement.
How business orchestration keeps Gemba actions moving
A Gemba walk may uncover the right problem and still fail to improve the process. The gap appears after the walk, when evidence, decisions and corrective actions begin moving across teams, systems and external participants.
Moxo is a business orchestration platform that can provide the execution layer for this follow-through. Teams can capture observations through structured forms, attach supporting files, assign corrective actions and set review or approval stages inside one coordinated workflow.
Each action can carry an owner, deadline and escalation path. A delayed safety correction can be routed to the responsible manager. A change to an operating procedure can move through review, approval and acknowledgement. The workflow preserves the evidence and decisions connected with the action, so teams do not have to reconstruct the history from email.
Suppliers, contractors and other external participants can contribute through Magic Links without entering a complicated account-creation process. Moxo integrations can connect the action workflow with the systems that already hold operational records. Management Reporting can then surface completion rates, overdue actions and recurring bottlenecks across different walks.
Technology does not replace direct observation or frontline judgment. It keeps the resulting commitments visible, coordinated and traceable until the improvement has been verified.
From seeing the work to improving it
A Gemba walk brings leaders closer to the process they are responsible for improving. Its value comes from careful observation, respectful questions and a willingness to understand why work behaves differently from the documented plan.
The practice works across factory floors, patient journeys, warehouses and service workflows. Wherever value is created, leaders can learn by seeing the work, listening to the people doing it and closing the loop on what they discover.
Moxo supports this by giving teams a structured place to turn observations into coordinated actions across everyone involved.
FAQs
What is a Gemba walk?
A Gemba walk is a Lean management practice where leaders observe work at the place it happens, speak with the people performing it and identify opportunities for improvement.
What does Gemba mean?
Gemba is a Japanese term meaning “the actual place” or “the real place.” In Lean management, it refers to the location where value-creating work occurs.
What are the seven steps of a Gemba walk?
Choose a purpose, select the process, identify participants, prepare a checklist, observe and ask questions, capture evidence and assign actions with visible follow-through.
What questions should you ask during a Gemba walk?
Ask open-ended questions about purpose, flow, standard work, recurring problems, customer impact and needed support. Questions beginning with “what,” “why” and “how” usually produce more useful answers.
What is the difference between a Gemba walk and a Gemba audit?
A Gemba walk focuses on learning how the process works and identifying improvements. A Gemba audit checks whether the process meets defined requirements or standards.
Who should participate in a Gemba walk?
Participants commonly include the process owner, frontline employees and a small number of relevant operational, safety or quality leaders. Include external partners when they perform an important part of the process.
How often should Gemba walks happen?
The right frequency depends on the process and risk. Some teams conduct focused walks weekly, while broader cross-functional walks may happen monthly or quarterly. Consistency and follow-through matter more than frequency alone.
How do you follow up on Gemba walk actions?
Record each action with an owner, priority, deadline, expected result and proof of closure. Review open actions regularly, escalate blocked work and report progress to the employees who participated.
Can Gemba walks be conducted virtually?
Yes. Teams can observe digital workflows, remote service interactions and system handoffs through screen sharing, process records and employee interviews. Virtual walks should still focus on the real process rather than a presentation about it.
