TL;DR: Gemba walks aren’t about walking around — they’re about learning how work actually happens, building trust with frontline teams, and turning observations into sustained improvement.

Gemba walks have become a widely adopted management technique. Leaders gain valuable insights into organizational value stream flow and often discover improvement opportunities by directly visiting the work environment. This collaborative approach involves employees sharing details about their tasks and the reasons behind them.

Why are Gemba Walks Important for Organizational Success?

Gemba walks are important for several reasons. They provide leaders with a firsthand understanding of the work environment, allowing them to observe processes and interactions directly. This enables the identification of inefficiencies, bottlenecks, and opportunities for improvement.

Gemba walks foster a collaborative approach by involving employees in discussions about their tasks and processes, encouraging open communication and idea-sharing. The insights gained during Gemba walks contribute to informed decision-making and strategic planning as leaders develop a deeper appreciation for the challenges and successes occurring at the operational level. Gemba walks are a key practice for continuous improvement, enhancing transparency, employee engagement, and overall organizational effectiveness.

W. Edwards Deming estimated that over 90 % of an organization's problems are caused by flawed processes and systems, not by the people working in them. Gemba walks are how leaders see those system-level problems firsthand -- the kind that never surface in status reports or dashboards.

The Qualitative and Quantitative Benefits of Gemba Walks

The operational benefits of Gemba walks are straightforward: leaders who see the work firsthand find inefficiencies that never surface in reports. That translates to reduced downtime, shorter lead times, lower costs, and better quality. But the less obvious benefits are often more valuable over time. Regular Gemba walks build trust between leadership and frontline teams. Employees who see their managers show up, ask real questions, and act on what they learn become more willing to share problems openly -- which means issues get caught earlier and ideas flow more freely. The compounding effect is a leadership team that makes better decisions because they understand how work actually happens, and a workforce that believes improvement efforts are genuine rather than performative.

Listen to the post:

Steps to Prepare for an Effective Gemba Walk

Great results depend on thoughtful planning, execution, and follow-up. Here are the most important steps you can take to ensure that your next Gemba walk is successful.

1. Prepare the Team

It is crucial that team members participating in the Gemba walk have a clear understanding of its purpose and benefits. They should recognize that the ultimate goal is to eliminate obstacles hindering their ability to contribute the maximum value. Discussing the walk in advance helps create a comfortable and open atmosphere, ensuring everyone is prepared and receptive to the interaction.

One easy way to do that is to send out this free eBook about Gemba walks to the team who will be participating:

2. Have a Plan

Gemba walks should not be confused with Management by Walking Around (MBWA), a different approach in which leaders simply wander about and get involved in what employees are doing. A Gemba walk should have a defined purpose, often associated with a specific concern related to a KPI.

During a Gemba Walk, the manager asks very in-depth questions about the process being observed. Who is involved? What materials are used? What do you do? How do you know what to do? When does the task take place? What depends on the outcome? MBWA does not involve that degree of depth, nor does it usually have the same focus on asking open-ended questions.

In fact, Dr. W. Edwards Deming, often called the Father of Quality Evolution, said in his 1982 work, Out of the Crisis, “ ‘Management by walking around’ is hardly ever effective. The reason is that someone in management, walking around, has little idea about what questions to ask, and usually does not pause long enough at any spot to get the right answer."

Organizations that effectively use Gemba Walks will create structure. For example, ThedaCare has created "STAT sheets" that provide consistent questions to be used by leaders at each level. Leaders also spend time at the Gemba to make sure they better understand the work... but at the same time, they don't worry about becoming experts in the work, because they can rely on the insights and expertise of front-line staff.

We break down the difference in detail in Gemba Walk vs. Management by Walking Around. 

3. Follow the Value Stream

Frequently, the most significant improvement opportunities arise at the interfaces between processes, departments, or individuals. By tracing the flow of value, these critical points, prone to potential waste, can be observed, and underlying issues can be uncovered.

Encouraging employees to propose processes, shifts, or work areas for a Gemba Walk is a valuable approach. This not only may reveal opportunities for improvement that might have been overlooked but also transform the process into a collaborative effort. Since frontline employees are actively engaged in the work, they are likely to provide insights into processes and areas that could benefit from an additional perspective. It's essential to recognize that the value brought to the table lies in offering a fresh perspective on existing processes. By involving people in identifying where this perspective would be most beneficial, you engage them in the improvement process and convey a supportive rather than critical approach.

For distributed teams, video-based Gemba walks are a practical substitute -- a live walkthrough of a workspace or screen-share of a digital process. The observation and questioning are the same; only the medium changes. 

4. Always Focus on the Process, Not People

A Gemba walk is not intended as an employee performance evaluation; its purpose is to observe, comprehend, and ultimately enhance processes. The walk should never carry a punitive tone, and it is not the appropriate time for engaging in employee task management.

Preparing employees for the Gemba walk is beneficial by informing them that you'll be asking numerous questions about how, when, and why tasks are executed. Emphasize that you are not seeking "right" answers; rather, you value responses that are honest and comprehensive. If tasks do not align with the standard, you want them to acknowledge rather than conceal it. It's crucial for them to recognize that your inquiries stem from a genuine desire to comprehend, devoid of any accusatory or confrontational intent.

5. Document Your Observations

Because there's a lot going on during a Gemba walk and you'll want to remember it all later, it's important to bring along tools to log your observations, including:

A way to log observations in real time -- The time to act on what you observe is after the walk, not during it. But if observations go into a notebook and then sit on your desk, they're dead. KaiNexus lets leaders log observations directly from a mobile device during the walk -- each one captured as a trackable item with an owner, a due date, and a link back to the process area where it was identified. Nothing gets lost between the walk and the follow-up.

A camera – It may be very useful later to browse through a gallery of images or maybe even a few quick bits of video. Be sure to be respectful of any people you might photograph. If cameras are not appropriate for your workplace, some graph paper for sketching out the layout of people and equipment may be useful.

An open mind – You don’t want your observations to be tainted by preconceived notions. For example, don’t assume that work is being performed to the Standard or that each person performs each task in the same manner.

6. Ask Questions

During a Gemba walk, one of the challenges is setting aside preconceived notions about why work is conducted in a specific manner. Avoid assuming that everything adheres to the standard procedure. Instead, inquire with employees about the reasons behind their work processes. Ask about the documentation of tasks, their approach to handling exceptions, and the rationale behind the sequence of operations.

The 5 Ws provide an excellent structure for the questions you want to ask and answer during your Gemba Walk.

• Who – Who are the people involved in the processes that you observe? Who provides input for the processes? Who are the “customers” of the process? Pro tip: You shouldn't be asking who to blame for problems...
  
  
• What – What are the inputs and outputs of the process? What obstacles inhibit flow or produce waste?
  
  
• Where – Does the space where the work is performed conform to 5S? Are necessary materials and equipment conveniently located? Do you notice the waste of motion?
  
  
• When – Are process inputs available when needed? Is work from this process being pulled through by the next, or do outputs sit idle? Is the waste of waiting observed?
  
  
• Why - What value does this work add for the customer?

For a deeper list, see 16 Questions to Ask on Your Next Gemba Walk

7. Don’t Suggest Changes During the Walk

A Gemba walk provides an observational opportunity rather than an immediate call to action. While the temptation to swiftly implement solutions is strong, it is essential to refrain and allow a period of reflection before making changes. Introducing solutions abruptly undermines individuals' capacity to learn and practice independent problem-solving. Implementing an improvement cycle like DMAIC or PDSA ensures that any changes made are well-considered and targeted to eliminate the identified issues, with involvement from the individuals directly engaged in the work.

For more on what to avoid, see The Top Ten Worst Things You Could Do on a Gemba Walk.

8. Walk in Teams

While not every Gemba walk needs to be a team endeavor, bringing along a leader from a different functional area of the organization can be a good way to get another point of view. People who are less familiar with a process might ask a different set of questions that shed light on the work in a new way.

Who should come along on a Gemba walk? Consider:

A peer from another department – It is easy to become so conditioned to problems that we see frequently that we don’t even notice them. A second set of eyes, less familiar with the processes and tasks of your team might be very valuable, especially if you take frequent Gemba walks.

A vendor – If your team uses equipment, consumable products or software, it might be useful to invite the vendor along on your walk. They may be able to suggest best practices or notice errors in how the product is being used. They may even uncover ways that they could improve the product to better fit your needs.

A customer – This might be controversial, and it certainly isn’t always a good idea, but today’s customers value transparency and they are often interested in seeing how the sausage is made, so to speak. They may also be able to identify things that they value less than you think.

One of your sales representatives – It is important that the people who pitch your product to customers know how it is created and understand how every part of the process relates directly to customer value.

9. Mix Up the Schedule

We strongly advocate for leaders to schedule Gemba walks in their calendars, but it should not become a routine occurrence set for the same time each month. To gain a comprehensive understanding of the process, it is advisable to conduct Gemba walks at varying times of the day, days of the week, and different parts of the month.

KaiNexus includes habit tracking for leader standard work, so organizations can monitor whether Gemba walks are actually happening at the planned frequency -- and spot when the practice starts to slip before it disappears entirely.

10. Follow-up with Employees

Sometimes, the results of a Gemba walk will be immediately obvious as changes are made or an improvement cycle is started, but even if there will be no immediate action as a result of a particular walk, it is important to follow up with employees. Share what you have learned and communicate what next steps, if any, will occur.

This is where most Gemba walks fall apart. The observation happened. The conversation was productive. And then nothing changes -- because there's no system connecting what was seen to what gets done. KaiNexus closes that gap. Observations logged during the walk become improvement items with owners, deadlines, and status tracking. Leaders can assign follow-up work to individuals or teams immediately. Smart notifications keep everyone accountable without requiring managers to chase updates manually. And because the work is visible, frontline employees see that their input led to action -- which is the single most important thing you can do to make the next walk more productive than the last one.

11. Return to the Gemba

If changes are implemented following a Gemba walk, be sure to return to the Gemba to observe those changes and verify that the desired result has been achieved. KPIs can give you some idea of how well the improvement is working, but nothing is as useful as first-hand observations.

A big objection to this that a lot of people have is that they're too busy for regular Gemba walks.

My answer to that is that many of the activities that take up so much time can be eliminated by Gemba Walks. You don’t need to send emails back and forth or form a committee to hold a meeting to address many common process or workspace issues. A first-hand look can save many hours of reading second or third-hand accounts about an issue. The human brain processes images way more quickly than text, after all. Anything that speeds your understanding of what’s happening on the front lines reduces the amount of time you have to spend trying to figure it out from afar.

Examples of Improvements Resulting from Gemba Walks

Specific improvements resulting from Gemba walks can vary depending on the industry and context, but here are some examples across different sectors.

For a real customer example, see how Four Seasons Produce uses Gemba walks with KaiNexus.

Manufacturing:

Reduction in machine downtime: Gemba walks identified maintenance issues, leading to improved preventive maintenance schedules and minimized downtime.

Enhanced production line layout: Observations on the shop floor led to a more efficient layout, reducing material handling time and improving overall production flow.

Healthcare:

Improved patient flow: Gemba walks in a hospital revealed bottlenecks in patient flow, leading to changes in scheduling and resource allocation for quicker and more efficient patient care.

Enhanced medication dispensing process: Observations in a pharmacy led to a redesign of the medication dispensing process, reducing errors and improving overall accuracy.

Office Environment:

Streamlined document approval process: Gemba walks in an office setting identified delays in document approvals, leading to the implementation of a more efficient approval workflow.

Improved communication channels: Direct observations highlighted communication gaps, resulting in the adoption of better communication tools and practices.

Retail:

Optimized shelf stocking process: Gemba walks in a retail store revealed inefficiencies in restocking shelves, leading to a redesigned stocking process for quicker and more organized shelf replenishment.

Enhanced customer service: Observations in customer service areas identified opportunities to improve response times and service quality, resulting in increased customer satisfaction.

Service Industry:

Faster order processing: Gemba walks into a service center and identifies delays in order processing, leading to the implementation of digital tools and process changes for quicker and more accurate order fulfillment.

Improved customer support workflow: Observations in a call center led to changes in the customer support workflow, reducing resolution times and improving customer experience.

These examples demonstrate how Gemba walks can pinpoint specific areas for improvement, leading to tangible enhancements in efficiency, quality, and overall performance across diverse industries.

From Observation to Organizational Learning

A single Gemba walk can surface a useful insight. A sustained Gemba practice -- where observations are captured, tracked, resolved, and shared -- builds an organization that learns faster than its problems can multiply.

The difference between the two is infrastructure. Not more walking. Not more checklists. A system that connects what leaders see to what the organization does about it.

KaiNexus connects Gemba walks to the rest of your improvement system. Observations become trackable items. Follow-up work gets assigned, monitored, and measured. Leaders see which walks are happening, which observations led to action, and what impact those actions produced. If your walks generate good conversations but inconsistent follow-through, that's not a discipline problem -- it's a systems problem. See how it works or talk to our team.

Frequently Asked Questions

What is a Gemba walk?

A leadership practice where managers go to where work happens to observe processes, ask questions, and understand current conditions firsthand. The term comes from the Japanese word "Gemba," meaning "the real place." The goal is direct observation rather than relying on reports or secondhand accounts.

What is the difference between a Gemba walk and management by walking around?

A Gemba walk is structured -- the leader has a specific focus area, asks open-ended process questions, and documents observations for follow-up. Management by walking around is informal and unstructured, focused on general visibility rather than systematic observation and improvement.

How often should leaders do Gemba walks?

Weekly at the frontline leader level, monthly at the senior leader level. Vary the day and time to see how work flows under different conditions. Consistency matters more than frequency -- a monthly walk with follow-through beats a weekly walk that produces no action.

What should you not do during a Gemba walk?

Don't evaluate individual performance, suggest fixes on the spot, or assume what you see matches the documented standard. The walk is for observation and learning. Problem-solving happens afterward, in collaboration with the people doing the work.

How do you follow up after a Gemba walk?

Log observations into a system that tracks them to completion. Communicate what you saw and what actions will result. Return to the Gemba after changes are made to verify results. The follow-up is what separates a productive walk from a well-intentioned tour.

Are Gemba walks only for managers?

No. Anyone can benefit from observing work in a different area. Peer Gemba walks -- where a leader from one department observes another -- surface problems that insiders have become blind to. Some organizations also use Gemba walks for onboarding, giving new employees a structured way to understand how work flows across the organization.

Can you do a Gemba walk remotely?

Yes. For distributed or hybrid teams, a live video walkthrough of a workspace or a screen-share of a digital process serves the same purpose. The observation, questioning, and documentation are identical -- only the medium changes. The key is maintaining the structure: defined focus area, open-ended questions, and documented follow-up.