Log In

30–60 Minute Gemba Walk Playbook for Managers

Isometric illustration of direct process observation

A gemba walk is a structured visit to where work actually happens, done so a manager can observe the real process instead of trusting a status report. The payoff is direct: you spot waste, workarounds, and bottlenecks that never make it into a dashboard, and you do it by watching and asking questions rather than lecturing. Done right, it ends with a checklist, a debrief, and assigned follow-up, not just a walk-through.

Management and Strategy Institute
Build Stronger Process Improvement Skills
MSI offers online Six Sigma certification programs with training materials and exams included, allowing professionals to study at their own pace from home.

Explore Six Sigma certification

Table of Contents

What Is a Gemba Walk, and Where Does the Practice Come From?

“Gemba” is the Japanese term for “the real place,” and the practice traces back to Toyota’s production system, where supervisors learned that the factory floor told them more than any report ever could. The Lean Enterprise Institute defines a gemba walk as a management practice built on direct observation and inquiry, rooted in the idea of genchi genbutsu, or “go and see for yourself.”

It is easy to confuse this with generic “management by walking around,” but the two are not the same thing. A gemba walk has a theme, a set of questions, and a specific outcome in mind. An audit checks compliance against a standard; a gemba walk tries to understand how work actually flows, including the parts that do not match the standard. According to Wikipedia’s summary of the practice, a gemba walk is a scheduled visit with a clear goal, not a random stroll through the office or plant.

Three principles hold the whole method together:

  • Go see. Watch the actual work, not a summary of the work.
  • Ask why. Dig into root causes once you understand what is happening, not before.
  • Show respect. Treat the people doing the work as the experts on that work.

Why Gemba Walks Matter for Continuous Improvement

Reports lie by omission. A gemba walk closes that gap by putting a manager’s eyes directly on the process, where workarounds, delays, and confusion are visible in a way no spreadsheet captures.

The habit also builds something harder to quantify: trust. Employees notice when a manager shows up regularly to ask questions instead of assign blame, and that changes what they are willing to report. Research summarized by practitioner guides points to positive outcomes in efficiency, quality, cost, and satisfaction across several studies that used gemba walks as part of a broader improvement effort. That is not a guarantee of results from any single walk, but it is a strong signal that the discipline pays off when it is sustained.

Why Gemba Walks Matter for Continuous Improvement — overview diagram

How Do You Prepare for a Gemba Walk?

A gemba walk without a plan turns into a stroll, and a stroll gets you politeness instead of information. Preparation is what separates the two.

  1. Pick a theme. Choose one value stream, one process, or one recurring complaint. Trying to observe “everything” guarantees you notice nothing useful. Mapping the value stream ahead of time helps you decide exactly where to stand and what to watch.
  2. Decide who comes. A small group, typically two to four people, works better than a crowd. Include someone from the area being observed if possible.
  3. Set ground rules. No blame, no on-the-spot corrections, no interrupting the work in progress.
  4. Build a short checklist. List the specific things you want to observe: hand-offs, wait times, tool placement, information gaps.
  5. Draft eight to ten open questions. Keep them observational, not accusatory.
  6. Tell the team in advance. A surprise inspection breeds defensiveness; a scheduled visit with a stated purpose invites honesty.

Pro Tip: Write your checklist the day before, not the morning of. A rushed checklist tends to focus on what you already expect to find, which defeats the purpose of going to look.

What to Observe and How to Ask Questions During the Walk

Once you’re on the floor, in the clinic, or in the workflow, the goal shifts from planning to noticing. Four things deserve your attention before anything else: workarounds people have invented to cope with a broken step, wait times between hand-offs, information that gets lost or re-entered manually, and tools or materials placed somewhere inconvenient. These four categories catch more waste than almost anything else you could look for, because they are the friction points people stop noticing after a few weeks on the job.

Question order matters more than most managers realize. Lead with “what,” not “why.” Lean Enterprise Institute guidance on how to go to the gemba recommends asking open, factual questions first, such as “What happens when this order comes in?” or “What do you do when the system is down?” Asking “why” too early puts people on the defensive, because it implies judgment before you have even understood the situation. Save the diagnostic “why” for the debrief, once you have a fuller picture.

Practical mechanics during the walk:

  • Take notes or photos as observation artifacts, not as evidence for a write-up.
  • Do not fix anything on the spot, even when the fix looks obvious. Stopping to correct a process mid-walk undercuts the person doing the work and short-circuits the deeper root-cause conversation you want to have later.
  • Stick to the walk’s stated theme instead of chasing every side issue that catches your eye.
  • Keep your body language neutral. A raised eyebrow reads as criticism even when you meant nothing by it.

Timing follows a fairly consistent pattern across practitioner guidance: 30 to 60 minutes for the walk itself, with a similar block set aside afterward for debrief. Shorter walks tend to feel rushed and produce shallow notes; much longer than an hour and people start performing for you instead of working normally, which quietly undermines what you came to observe.

Closing the Loop: Debrief, Assign Actions, Follow Up

A gemba walk that ends with a notebook full of observations and no follow-up is worse than useless. It teaches employees that speaking honestly changes nothing.

  1. Debrief promptly within a few days. Waiting longer lets details go stale and lets the moment’s trust evaporate.
  2. Assign owners and deadlines. Run each finding through a Plan-Do-Check-Act cycle, or a similar structured method, so nothing stays a vague intention.
  3. Report back to the team. Even a short message that says “here’s what we changed based on last week’s walk” does more for engagement than the walk itself.

Adobe Business’s guidance on gemba walks makes closing the loop with a team debrief a core part of the method, not an optional add-on. Skipping it is the single most common reason gemba walks fade out after a few enthusiastic months.

Gemba Walk Variations: Virtual, Safety, and Sector-Specific Examples

The location of “the real place” shifts depending on the work, and the method adapts with it.

  • Virtual gemba. Screenshares, recorded calls, and shared dashboards replace physical presence. Adobe Business notes that virtual walks work well when they stay focused on one theme and capture recordings or screenshots as observation artifacts, a habit that became common during remote-work shifts.
  • Safety gemba. Focus narrows to hazard exposure, PPE use, and near-miss patterns rather than general efficiency.
  • Construction sites. Lean Construction resources apply gemba walks to observe material flow and safety conditions directly on-site.
  • Healthcare. The “gemba” becomes the ward or clinic workflow, watching hand-offs between shifts and how patients actually move through a unit; see how this plays out in continuous improvement in healthcare.
  • Knowledge work. For software or service teams, the gemba is a ticketing system or workflow tool, where the observation cues shift from physical movement to how information passes between people.

What Managers Consistently Get Wrong About Gemba Walks

The biggest mistake I see isn’t a scheduling problem, it’s a mindset problem: managers treat the gemba walk as an inspection with better branding. The moment employees sense they are being checked on rather than learned from, the walk stops producing honest information and starts producing performance. People show you the version of the process they think you want to see, and you leave with worse data than if you had just read the report.

Inspection versus learning gemba mindset comparison

The second mistake is skipping the debrief because “everyone’s busy.” That is exactly backward. The walk itself is the cheap part. The value lives in what happens in the 24 to 72 hours after, when observations either turn into an assigned owner and a deadline or quietly die in a notebook. A gemba program’s health is best measured by how many findings from three months ago actually got closed, not by how many walks got scheduled.

Formal training changes how a manager runs this whole cycle, mostly by tightening the “ask why” phase. Six Sigma root-cause tools give structure to a question that untrained managers tend to ask once and abandon. A Six Sigma certification builds the habit of following a symptom back to its actual source instead of settling for the first plausible explanation, which is where most gemba findings quietly go to die.

— David Lovell

Build the Skills Behind an Effective Gemba Walk

Watching the floor is only half the job. Turning what you see into a fix that sticks takes root-cause analysis, structured problem-solving, and a PDCA habit that most managers never learn on the job. Management and Strategy Institute’s Lean Six Sigma Black Belt certification covers exactly that: the analytical tools that turn a list of gemba observations into a prioritized, measurable action plan, at one flat price with no hidden exam fees.

Lean Six Sigma Black Belt Certification

The self-paced format matters here. You study on your own schedule, at home, and you’re not locked into a cohort calendar that assumes you have nothing else going on. If you want the full certification track, the Six Sigma certification package bundles the study materials and exam attempt together. Start with the course catalog at courses.msicertified.com and pick the level that matches where your team’s improvement work actually stands today.

Sources

FAQ

What Are the 7 Wastes Observed on a Gemba Walk?

The classic lean wastes are transport, inventory, motion, waiting, overproduction, over-processing, and defects. A gemba walk checklist typically maps observation points to these categories so notes translate directly into improvement priorities.

Is a Gemba Walk Part of Six Sigma?

A gemba walk originates from lean manufacturing, but it fits naturally into Six Sigma’s Define and Measure phases, where direct observation strengthens root-cause work later in the Analyze phase. Many practitioners trained through a Lean Six Sigma Black Belt certification use gemba walks as their primary data-gathering step.

What Are the Key Steps of a Gemba Walk?

Pick a theme, prepare a checklist and open questions, observe without fixing anything on the spot, ask “what” before “why,” capture notes or photos, then debrief and assign follow-up actions within a few days.

How Long Should a Gemba Walk Take?

Most practitioner guidance recommends 30 to 60 minutes for the walk itself, plus a similar block of time for the debrief that follows.

How Often Should Teams Run Gemba Walks?

Consistency matters more than frequency. A regular, predictable schedule, whether weekly or monthly, reduces the tendency for employees to change behavior just because a manager is watching.