Gemba Walk: Stop Managing From the Conference Room and Go See the Work.

Your dashboard says productivity is down 8%. The warehouse manager says labor is the problem, Finance thinks overtime is too high, and Operations wants another automation project. Everyone has data, everyone has an opinion, and everyone may still be missing what is actually happening. Sometimes the smartest thing a leader can do is leave the conference room, go to the place where the work happens, and see the process firsthand.

That is the idea behind a Gemba Walk. Gemba is a Japanese term meaning “the real place,” and in Lean thinking it refers to the place where value is actually created. That could be a factory floor, warehouse, distribution center, office, maintenance area, hospital, store, or anywhere else people are doing the work that ultimately serves the customer. A Gemba Walk sounds simple because the concept is simple, but the value comes from doing it with purpose, curiosity, and respect for the people performing the work.

What Is a Gemba Walk?

A Gemba Walk is a structured visit to the place where work happens so leaders can observe the actual process, talk with the people doing the work, identify obstacles, and understand opportunities for improvement. The objective is not to walk around and see whether employees are staying busy. It is to understand how the process really works and determine how leaders can help make that work safer, easier, more efficient, and more effective.

That distinction changes the entire conversation. A manager asking, “Why aren’t you hitting the target?” creates a very different environment from a leader asking, “Can you show me what makes it difficult to hit the target?” The first question can feel like an investigation of the employee, while the second begins investigating the process. Strong Lean leaders learn to separate the person from the problem and focus their attention on the system surrounding the work.

The Dashboard Is Not the Gemba

Modern businesses have more information than ever. ERP systems, warehouse management systems, transportation platforms, planning tools, dashboards, artificial intelligence, and real-time analytics can give leaders extraordinary visibility into performance. Those tools are valuable, but numbers still cannot show everything that happens inside a process.

A dashboard may show that order picking takes too long. Walking the warehouse may reveal that employees spend a large portion of every shift searching for products, walking around poorly positioned inventory, waiting for replenishment, or dealing with scanners that regularly lose connectivity. The metric identifies the symptom, while the Gemba Walk helps explain the reality behind it.

This is why data and direct observation should complement each other. The numbers can tell leaders where performance is changing, but going to the Gemba helps them understand why. The goal is not to choose between analytics and observation. The strongest leaders use the data to know where to look, then go see what is actually happening.

A Gemba Walk Is Not an Inspection

One of the most important things to understand is that a Gemba Walk should not feel like an employee inspection. If workers believe leadership is walking the floor to catch people doing something wrong, they will behave differently the moment managers arrive. Problems will be hidden, uncomfortable questions will disappear, and leaders will see a cleaner version of reality than the one employees experience every day.

The objective should be to understand the process rather than evaluate the person. When something is not working, leaders should look at procedures, tools, training, material flow, information, equipment, layout, staffing, standards, approvals, and handoffs before automatically assuming the employee is the problem. Respect for people is not separate from continuous improvement; it is one of the conditions that makes continuous improvement possible.

What Should You Look for During a Gemba Walk?

Walking through an operation without a purpose can quickly turn Gemba into nothing more than a plant tour. A strong Gemba Walk should focus on a process, problem, flow, or business objective so leaders know what they are trying to understand.

Depending on the operation, useful things to look for include:

Waiting for materials, information, approvals, or equipment
Unnecessary walking or transportation
Excess inventory or work-in-process
Rework and recurring quality problems
Bottlenecks and queues
Workarounds employees have created
Safety concerns
Equipment downtime
Duplicate data entry
Confusing instructions or unclear standards
Problems that employees have learned to live with
Activities that consume time without creating customer value

The goal is not to produce the longest possible list of problems. It is to understand the process the way the people doing the work experience it every day. Leaders often discover that the biggest improvement opportunities are hidden in activities everyone has become accustomed to accepting.

Ask Better Questions

A strong Gemba Walk is driven as much by curiosity as observation. Leaders should resist the temptation to arrive with solutions already decided and instead ask questions that help employees explain how the process actually works. The people doing the work hundreds of times every week often understand frustrations, bottlenecks, shortcuts, and opportunities that never appear in reports.

Useful Gemba Walk questions include:

Can you show me how this process works?
What is supposed to happen next?
What usually gets in your way?
Where do you spend the most time waiting?
What causes errors or rework?
What do you have to work around every day?
How do you know whether the process is performing correctly?
What happens when something goes wrong?
What is one thing you would change if you could?
What would make your job easier while improving the result?

After asking the questions, leaders need to listen. A Gemba Walk creates a mechanism for bringing frontline knowledge into the improvement process, but that only works if employees believe their observations are being taken seriously.

Look for the Workaround

One of the most valuable things to find during a Gemba Walk is a workaround. Workarounds are often treated as employee problems, but they can actually be clues about where the official process is not meeting reality.

If employees created an unofficial spreadsheet, built their own cart, repositioned materials, developed a shortcut, or bypassed part of a process, ask why. Sometimes the workaround is unsafe or creates another problem and needs to be corrected. Other times it exists because the original process is too slow, too complicated, or simply does not work well in the real operating environment.

Instead of immediately asking why people are not following the process, ask why the process makes people feel they need another way. That shift in thinking can lead directly toward root cause.

Follow the Flow, Not the Organization Chart

Supply chains operate horizontally even though companies are usually organized vertically. A customer order may move through Sales, Planning, Procurement, Manufacturing, Warehousing, Transportation, and Finance before the process is complete. A Gemba Walk can help leaders see those handoffs rather than viewing each department independently.

Follow an order, material, product, or piece of information from beginning to end. Watch where it stops, changes hands, waits for approval, gets entered again, or becomes unclear. Some of the biggest opportunities are not inside individual departments but in the spaces between them.

This is why Gemba is especially valuable for supply chain leaders. It forces the organization to stop optimizing isolated functions and start seeing the entire flow. A department can be performing well on its own metrics while still creating problems somewhere else in the system.

Gemba Walks in a Warehouse

Imagine a distribution center struggling with picking productivity. Management could respond by increasing productivity targets, adding labor, or purchasing new automation. A Gemba Walk might reveal that the real problem has little to do with employee effort.

The highest-volume products may be located far from packing. Employees could be walking hundreds of unnecessary feet per order, while replenishment activity blocks pick aisles during the busiest part of the shift. Inventory records may also be inaccurate, forcing workers to search for products that the system says should be there.

Once leaders see the work, the questions change. Can high-volume products be re-slotted? Can replenishment occur at different times? Why is inventory accuracy poor? What is creating unnecessary travel? Instead of telling people to work faster, the organization begins improving the system surrounding the work.

Gemba in Procurement and Planning

Gemba is not limited to factories and warehouses. The “real place” can also be an office process. Procurement, planning, customer service, and finance all contain workflows that can benefit from direct observation.

A procurement Gemba Walk might follow a purchase requisition from request through approval, sourcing, purchase order creation, supplier acknowledgement, receipt, and payment. Leaders may discover duplicate approvals, emails replacing system workflows, poor master data, long queues, and employees manually correcting the same problems repeatedly.

Planning offers similar opportunities. Sit with a planner and watch how a forecast becomes an executable plan. Notice how many systems they open, spreadsheets they maintain, exceptions they investigate, and manual adjustments they make. Understanding a process diagram is not the same as understanding the actual work required to execute that process every day.

The Most Important Part Happens After the Walk

A Gemba Walk can actually damage trust if leaders repeatedly ask employees about problems and then do nothing with what they hear. Imagine telling a senior leader that the same system problem wastes an hour of your day, only to watch that leader write it down and disappear. Six weeks later, another leadership team arrives, asks the same question, records the same problem, and nothing changes again.

Eventually, employees stop talking.

Effective Gemba requires action and follow-up. Not every suggestion needs to be implemented, and some problems will take time or prove impractical to solve. Employees should still understand what happened and whether the issue is being addressed.

A simple follow-up process can include:

Record the observation
Determine whether deeper root-cause analysis is required
Assign ownership
Establish the next action
Communicate what will happen
Measure whether the change worked
Return to the Gemba and verify the result

Closing the loop tells people that speaking up matters. It also turns the Gemba Walk from an observation exercise into part of a real continuous improvement system.

Gemba Walks Build Better Leaders

There is another benefit that is harder to put into a spreadsheet. Leaders who regularly spend time where the work happens gradually become better decision-makers because they build a richer mental model of the operation.

They understand what a late supplier delivery actually does to production. They see what bad master data does to a planner, what poor packaging does to warehouse employees, and what an unnecessary approval does to purchase-order cycle time. That knowledge changes the quality of future conversations.

The leader is no longer discussing operations only through averages, charts, and PowerPoint slides. The numbers now connect to an actual process and to the people trying to make that process work. That connection can improve prioritization, investment decisions, and problem solving across the organization.

Gemba Walks Create a Continuous Improvement Culture

A single Gemba Walk can uncover problems, while regular Gemba Walks can help change a culture. When employees see leaders consistently asking how processes can improve, listening carefully, removing obstacles, and returning to see whether changes worked, improvement begins to feel like part of normal work rather than another corporate initiative.

That is where Gemba connects with Kaizen and continuous improvement. The organization develops a repeated cycle of seeing, learning, improving, checking, and learning again. Over time, problems become more visible and employees become more comfortable raising them.

The objective is not for senior leaders to personally solve every problem. It is to help create an organization where issues can surface early and the people closest to the work have the confidence and support to improve them.

Final Thoughts: Go See for Yourself

We live in an age of dashboards, analytics, automation, digital twins, control towers, and artificial intelligence. Those capabilities can give leaders extraordinary visibility, but they do not eliminate one of the oldest and most useful leadership practices in operations: going to the real place and seeing the work firsthand.

Talk to the people doing the work and watch what actually happens rather than relying only on what the procedure says should happen. Look for waiting, unnecessary movement, rework, workarounds, frustration, bottlenecks, and improvement ideas that have never made it into a management report.

Most importantly, do not walk into the Gemba looking for someone to blame. Walk in looking for something to learn and something you can help improve. A spreadsheet can tell you that something is wrong, a dashboard can tell you where performance changed, and AI may increasingly help predict what will happen next. The Gemba Walk helps connect all of that information to reality.

Sometimes the fastest path to understanding a problem is still remarkably simple: leave the conference room, go to the real place, observe the work, listen to the people doing it, and improve the process together.

Gemba and Continuous Improvement Quotes

“People who can’t understand numbers are useless. The gemba where numbers are not visible is also bad. However, people who only look at the numbers are the worst of all.” ~Taiichi Ohno, father of the Toyota Production System
“There are three kinds of leaders. Those that tell you what to do. Those that allow you to do what you want. And Lean leaders that come down to the work and help you figure it out.” ~John Shook
“If you aren’t improving you are going out of business.” ~Dave Waters
When you are out observing on the gemba, do something to help them. If you do, people will come to expect that you can help them and will look forward to seeing you again on the gemba. ~Taiichi Ohno
“The frequency of leadership going to the Gemba is inversely proportional to the number of walls separating them from the Gemba.” ~Jon Miller
“It’s pretty simple. If you have an environment where people aren’t afraid to speak up, and you listen to them things will get better.” ~Dave Waters