methodatlas
Operations

Gemba Walk

Turns workflows, data, causes, and improvements into a tangible result by selecting a process, going to the place of work, and recording improvements.

Core question
Which gaps between standard work and real work become visible on site but do not appear in reports or dashboards?
LowWorkshop30-120 min
Open runsheetEstablish practiceStart comparison
Purpose

The method helps clarify workflows, data, causes, and improvements concretely. It identifies patterns, causes, bottlenecks, or constraints and derives actions. The outcome is captured as observation notes and improvement ideas.

How it works

The team follows the steps: select a process, go to the place of work, observe without disruption, ask clarifying questions, and record improvements. Each step is captured visibly. At the end, observation notes and improvement ideas are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

Gemba Walk · Understand Work On SiteObserve the real process, ask respectfully, and derive improvements from concrete conditions
Gemba WalkThe visual shows observation at the real workplace, clarifying questions, and concrete improvement notes.Understand work where it happensOn-site observations replace assumptions and make concrete improvements easier to connect to.seeclarifyderivelearn respectfullyPlace of workreal process instead of reportObserveflow, wait time, aidsAskWhat makes the work harder?Improvementsmall experiments with ownerWaiting for approvalDuplicate entryStandard unclear

Flow

  1. 1Select a process
  2. 2Go to the place of work
  3. 3Observe without disruption
  4. 4Ask clarifying questions
  5. 5Record improvements

The runsheet guides execution with 4 phases, timeboxes, 6 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Ops Leadership
  • Process Improvement
  • Service Teams

Not good for

  • Desk-only theory
  • Status meetings

Deep dive

In detail

Gemba Walk follows a clear working logic: select a process, go to the place of work, observe without disruption, ask clarifying questions, and record improvements. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, observation notes and improvement ideas are produced and ready to support decisions, learning, or further planning.

Facilitation

Prepare a clear guiding question, the right information, and a visible workspace. Plan about 30-120 min with 2-6 people and use the format in a facilitated workshop. The facilitation stays lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions help.

Output artifacts
Observation NotesImprovement Ideas
Tags
leanobservationprocessoperations

Sources

Gemba - What Does It Mean? | Lean Enterprise Institutelean.orgWhat is Gemba: Meaning and Best Practicesblog.proactioninternational.com
Artifact templates
Gemba Walk Working TemplateCompact working template for Gemba Walk with context, input, output artifacts, and next step.
markdown

gemba-walk-working-template.md

Compact working template for Gemba Walk with context, input, output artifacts, and next step.

Gemba Walk Working Template

Goal

Go to where the work actually happens and observe the real process.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Observation Notes:
  • Improvement Ideas:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

Value Stream Mapping

Statt Gemba Walk, wenn du einen End-to-End-Fluss mit Wartezeiten und Verschwendung vermessen willst.

Similar methods

All methods
Operations
A3 Problem Solving

Turns workflows, data, causes, and improvements into a tangible result by defining the problem, capturing the current state, and defining follow-up actions.

Operations
Process Mapping

Turns workflows, data, causes, and improvements into a tangible result by setting process boundaries, collecting steps, and deriving a target process.

Operations
Fishbone Diagram

Turns workflows, data, causes, and improvements into a tangible result by defining the problem, choosing cause categories, and prioritizing likely causes.

Operations
Waste Analysis

Turns workflows, data, causes, and improvements into a tangible result by clarifying the process and value definition, observing or mapping the flow, and deriving improvements.

Operations
Kaizen Event

Turns workflows, data, causes, and improvements into a tangible result by clarifying scope and goal, observing the current process, and setting the new standard and follow-up.

Operations
Standard Work Analysis

Turns workflows, data, causes, and improvements into a tangible result by collecting the current standard, observing actual work, and updating and training the standard.