In many organizations, operational performance is still steered from the offices, through dashboards, reports and steering meetings. Decisions rely on consolidated data and on the reported word of intermediate managers. The distance between those who decide and those who execute often remains considerable.

Yet this distance creates a blind spot. Indicators inform about what is measured, but they say little about how the work actually unfolds, about informal workarounds, about the daily frictions that weigh on productivity and quality.

The gemba walk proposes to close this gap. Going on site, observing the work where it is done, listening to those who do it: the approach seems obvious, but it proves more demanding than it appears. Conducted well, it transforms management’s understanding of its own organization.

Understanding what the gemba walk covers

The term gemba, in the Lean tradition, designates the place where value is created: the workshop, the production line, the engineering office, the counter, the care unit. Everything that happens elsewhere is considered secondary to what plays out on that ground.

The gemba walk therefore consists in deliberately moving to that place to observe the actual work. It is neither a protocol visit nor an audit. The objective is not to check compliance, nor to greet the teams, nor to collect material for a report.

It is to learn. To learn what the figures do not show and what the reports do not say.

The gap between prescribed work and actual work

One of the most persistent findings of continuous improvement initiatives is the existence of a gap between what is prescribed and what is effectively done. Procedures describe an ideal way of operating, but teams continually adapt their practices to the constraints of the moment.

These adjustments are sometimes beneficial, sometimes compensatory, sometimes risk-bearing. They generally remain invisible from the offices. Only direct observation allows identifying them and understanding why they emerged.

A gemba walk reveals these gaps not to sanction them, but to question their origin. A bypassed procedure is often the symptom of a poorly designed procedure.

What to look for on the field

A useful gemba walk does not boil down to attentive wandering. It is organized around a few precise observation points:

  • the physical and informational flows and their disruptions
  • waiting times, reworks and useless movements
  • the material conditions of the workstation
  • the gaps between the described standard and the observed practice
  • the weak signals expressed by operators
  • the interfaces between teams or between processes

This grid is not a form to fill in. It structures the gaze and prevents dispersion. The observer keeps an open mind to what fits into no box.

A posture of questioning rather than of inspection

The value of a gemba walk rests almost entirely on the posture adopted. A manager arriving with answers already formed will only see what they thought they would see. A manager arriving with open questions will see what they did not suspect.

The favored questioning is the one that invites explanation rather than the one that demands justification. “How does it actually happen” opens an exchange. “Why is this not compliant” closes it.

This difference seems minor. It is actually decisive. It conditions the quantity and quality of the information that surfaces. It also conditions the trust that teams will grant to subsequent gemba walks.

The drifts that empty the exercise of its meaning

Poorly understood, the gemba walk can quickly slide into two drifts that make it counterproductive. The first is the gemba walk-inspection: a passage on the field used to verify the application of procedures and to flush out gaps to sanction. Teams prepare for it, hide problems and present a reconstituted reality.

The second drift is the gemba walk-theater. The manager shows up, exchanges a few words, takes a photo for internal communication, then leaves without having observed anything precise. The exercise loses all learning value and becomes a cosmetic ritual.

In both cases, what is supposed to bring management closer to the field ends up reinforcing the distance.

The role of management in conducting the gemba walk

The gemba walk is by construction a managerial practice. Its effectiveness depends on the way management carries it and on the coherence between what is observed and the decisions that follow.

When the gemba walk is used as a control tool, teams learn to dread it. They prepare the ground, smooth over anomalies and limit exchanges to the strict minimum. The information degrades and the practice exhausts itself.

Conversely, when it is conducted as a tool of learning and support, it frees speech. Difficulties are expressed more freely, improvement ideas surface and cooperation between hierarchical levels strengthens.

Managerial posture conditions the value of the gemba walk.

The necessity of a structured follow-up

An observation without follow-up produces disenchantment. If teams notice that the difficulties raised during a gemba walk are never addressed, they stop investing in the exchange. The exercise becomes formal.

Follow-up does not mean that every problem must be resolved immediately. It means that each observation is tracked, prioritized, and that a clear response is given, even to explain why a request cannot be satisfied in the short term.

This discipline transforms the gemba walk into a learning loop. Without it, observation remains without effect.

From one-off observation to a lasting practice

The gemba walk takes its full value when it takes place over time. An isolated visit gives a snapshot; a regular practice builds a fine understanding of the organization.

Regularity also installs a different relationship to the field. Management’s presence is no longer perceived as exceptional. Exchanges become more direct, weak signals surface earlier, adjustments happen before problems worsen.

This sustained practice contributes to grounding decisions on observed facts rather than on perceptions filtered by several hierarchical levels.

The gemba walk then becomes a full-fledged steering instrument.

Key takeaways

  • The gemba walk consists in observing the work where it is done
  • It reveals the gap between prescribed work and actual work
  • It does not replace indicators but puts them in perspective
  • A posture of questioning is worth more than a posture of inspection
  • The gemba walk-theater and the gemba walk-inspection ruin the exercise
  • The voice of operators is the raw material of the analysis
  • Without structured follow-up, observation loses all its value
  • Regularity turns the gemba walk into a lasting steering tool