I remember watching leaders visit the floor at Toyota for the first time. From a distance, it didn’t look particularly remarkable. They weren’t giving speeches. They weren’t carrying checklists. They weren’t walking around pointing out mistakes.
If you’re working to improve the way work flows in your organization, start with my free Implement Scalable Processes in 5 Simple Steps guide. It will help you identify where to focus before you start making changes.
Most of the time, they were simply observing. They watched how work moved. They asked questions. They listened far more than they spoke.
Years later, I realized why those moments stood out. They weren’t taking a tour. They were practicing Gemba.
Today, Gemba has become one of the most misunderstood concepts in operational excellence. Many organizations treat it as a leadership walk-through, a chance to check on employees, or another management routine to add to the calendar.
That was never its purpose.
What Is The Purpose of the Gemba Walk
Gemba isn’t about looking busy as a leader. It’s about learning how work actually happens before trying to improve it. So, what is Gemba?
Gemba means “the actual place.” In Lean thinking, it refers to the place where value is created. According to the Lean Enterprise Institute, Gemba is where the real work happens, and a Gemba Walk is the practice of going to that place to observe, understand, and improve the work.
That sounds simple, but most leaders do not struggle with the walking part. They struggle with the seeing part.
A leader walks into a department, asks a few questions, notices what looks broken, and immediately starts solving. A handoff is missed, so the answer becomes “better communication.” A deadline slips, so the answer becomes “more accountability.” A spreadsheet is out of date, so the answer becomes “a better tool.”
Sometimes those things are true. But very often, they are only symptoms.
Gemba is not about collecting evidence for the solution you already had in mind. It is about slowing down long enough to understand the real process. Not what the SOP says should happen. Not what the dashboard says is happening. Not what leadership hopes is happening. What is actually happening.
That distinction matters because companies do not scale based on good intentions. They scale based on what their systems can reliably produce.
And this is where many companies get into trouble. In the first half of 2026, Gallup reported that only 49% of employees strongly agreed they know what is expected of them at work.
That is not a people problem. That is a clarity problem.
How Did Toyota Use Gemba Differently Than Most Companies Today?
At Toyota, Gemba was not treated as a performance. It was not a leader walking around to appear involved. It was not a surprise inspection. It was not a chance to jump in and prove who had the answer fastest.
It was a discipline.
Leaders went to the place where the work happened because they understood something many companies forget: you cannot improve what you do not understand.
Toyota used Gemba to study the flow of work, identify where problems occurred, understand why they existed, and support people in improving the process. The point was not to blame the person closest to the problem. The point was to understand the system creating the problem.
Many companies today use Gemba very differently. They turn it into a scheduled walk-through. A leader visits a team, asks what is going on, makes a few observations, and leaves with a list of action items.
That may look like operational leadership, but it often misses the point.
Real Gemba requires humility. It requires leaders to enter the work with curiosity instead of judgment. It requires them to see the difference between a person failing and a process failing.
When a team misses a deadline, the easy assumption is that someone dropped the ball. The better question is, what made the ball so easy to drop?
Was ownership unclear? Was the handoff invisible? Was the process dependent on one person remembering something? Was the team using three different sources of truth? Was the “standard process” actually just tribal knowledge with a nicer name?
These are very different problems. They require very different solutions. If you skip the observation, you will usually solve the wrong one.
What Does a Good Gemba Walk Actually Look Like?
A good Gemba walk is quiet before it is useful.
That may sound strange, but it matters. The leader’s first job is not to talk. It is to watch how work actually moves.
A good Gemba walk starts with observing the process, not interrogating the person. You look at where the work begins, where it waits, where it gets handed off, where it gets reworked, where decisions slow down, and where the team has created workarounds to keep things moving.
Then you ask better questions.
Not: “Why didn’t this get done?”
Instead, ask:
“What happened right before the delay?”
“Where does this handoff usually break down?”
“What information do you need but do not consistently have?”
“What part of this process depends on memory?”
“Where do you have to create a workaround to serve the customer well?”
“What would make this easier to do correctly every time?”
These questions change the conversation. They move the team away from blame and toward process understanding. They help leaders see root causes instead of reacting to symptoms.
They also show the team that operational improvement is not something being done to them. It is something being built with them.
That matters because people support what they help improve.
Can Service Businesses Use Gemba, Or Is It Only For Manufacturing?
Gemba is often associated with manufacturing because of its roots in Lean and Toyota. But Gemba is not only for manufacturing.
Every business has a place where value is created.
In a service business, Gemba may not be a factory floor. It may be a client onboarding call. A sales-to-operations handoff. A project management board. A support ticket queue. A fulfillment workflow. A leadership meeting where decisions get made and remade because ownership is unclear.
The principle is the same: go where the work happens and learn from the real process.
In growing service companies, leaders often have a polished idea of how work gets done. Then they go to the actual place and discover the truth.
The client onboarding process is not really the clean five-step workflow in the document. It is a 17-step workaround managed by the most experienced person on the team.
The sales-to-operations handoff is not really happening inside the CRM. It is happening in Slack, email, memory, and one recurring meeting everyone secretly depends on.
The approval process is not really “simple.” It requires three people, two reminders, and a founder who still gets pulled in because no one is fully sure who has final authority.
This is why Gemba matters in service businesses. It reveals the gap between the designed process and the lived process.
That gap is where inefficiency grows. It is where accountability gets blurry. It is where your best people carry too much invisible weight. It is where leaders get dragged back into tactical firefighting even though everyone agrees they should be focused on strategy.
And here is the uncomfortable part: if you do not go see it, you may be rewarding the workaround while blaming the process.
What Mistakes Do Leaders Make During Gemba Walks?
The first mistake leaders make during Gemba walks is turning observation into surveillance.
A leader walks around, checks whether people are doing things correctly, points out what is wrong, and leaves with a list of fixes.
That is not Gemba. That is management by drive-by.
Real Gemba requires respect. The point is not to catch people making mistakes. The point is to understand the conditions people are working inside.
The second mistake is solving too quickly. Leaders are often rewarded for speed, decisiveness, and answers. But during Gemba, moving too quickly can create the wrong solution.
If the process is unclear, more effort just creates more strain. If the handoff is broken, more meetings just create more conversation about the same problem. If accountability is undefined, more reminders just create more dependency on the leader.
The third mistake is assuming the problem is the person instead of the system.
Most leaders do not have lazy teams. They have teams spending too much time trying to make unclear systems work.
Asana’s Anatomy of Work research found that 60% of a person’s time at work is spent on “work about work”, including communicating about tasks, hunting down documents, and managing shifting priorities.
That is a lot of time spent around the work instead of inside the work.
The fourth mistake is letting knowledge live in one person’s head.
The company may look like it has a process, but the real process lives in one person’s memory. The team may look cross-functional, but only one person knows how to move the work forward when something gets complicated. The system may look documented, but everyone still has to ask Sarah, Mike, or the founder what to do next.
That is not scalable.
Panopto’s Workplace Knowledge and Productivity research found that employees spend 5.3 hours per week waiting for information from colleagues. That is not just wasted time. It is delayed decisions, slower execution, duplicated effort, and unnecessary frustration.
And again, the issue is usually not the people. It is the system.
The fifth mistake is failing to turn observation into improvement.
This is where many companies get stuck. They learn the language. They schedule the walks. They ask a few questions. Everyone nods. Then nothing changes.
The same issues come back next month because there is no system for turning what was observed into better standards, clearer ownership, improved workflows, or stronger accountability.
Gemba is powerful, but it is not magic.
Observation has to become action. Action has to become process improvement. Process improvement has to become a standard. And that standard has to be owned by the team, not carried forever by the leader.
Otherwise, Gemba becomes another meeting in motion. A good intention. A nice ritual. A leadership activity that looks operationally mature but does not actually change the way the company runs.
The goal is not to “do Gemba.” The goal is to build a company that can see problems clearly, solve them at the root, and improve the way work gets done.
Your Next Stage of Growth Doesn’t Need Another Tool
Operational maturity does not start with a new tool. It does not start with a bigger org chart. It does not start with another all-hands reminder that people need to communicate better.
It starts with seeing the work clearly. Then building the systems, ownership, and accountability that allow the work to improve.
That is the real spirit of Gemba.
It is not a walk. It is a leadership discipline.
It is the discipline of staying close enough to the work to understand it, humble enough to question your assumptions, and structured enough to turn what you learn into better operations.
If your company is growing but still depending on leadership heroics to keep things moving, that is a sign your systems need attention.
If your team is talented but constantly working around unclear processes, that is a sign your operations need attention.
If your growth is creating more firefighting instead of more freedom, that is a sign your next stage will require a different operating rhythm.
That is exactly what we work on inside The Ops Edge Academy.
Cohort 3 is designed for founders, COOs, and operators who want to step out of reactive problem-solving and build a company that runs with clearer processes, stronger accountability, and less dependence on daily leadership rescue.
If you are ready to stop guessing where the real operational issues are and start building the systems to solve them:
👉 Apply now for The Ops Edge Academy Fall Cohort.
Only 7 spots left. Apply by August 31 to be considered for this cohort.
