Going to the Gemba
The Gemba is the real place — where work actually happens, where patients are actually waiting, where the constraint actually manifests. Going to the Gemba means going there to see what is actually occurring, not what is reported. It is not a management technique. It is a visibility intervention — and the most direct response to the most universal visibility failure: the structural separation between where decisions are made and where the constraint lives.
The Gemba walk only produces structural change when the person going has the authority to act on what they see AND the staff have the psychological safety to show them what is actually happening. Without both conditions, the walk is observational theatre rather than a visibility intervention.
A management walkround without authority produces a report. A Gemba walk with authority and psychological safety produces a change point. Bootstrap CUSUM on the outcome metric tells you which one you had.
☰ Contents
What the Gemba is
The word Gemba comes from Japanese and means “the real place” — the actual location where value is created, where work happens, where problems manifest. In manufacturing it is the factory floor. In healthcare it is the ward, the corridor, the discharge lounge. In a software company it is the support desk, the implementation site, the customer’s office where the system is being used.
Taiichi Ohno, who developed the Toyota Production System, made Going to the Gemba a core discipline precisely because he recognised that the information needed to improve a system almost never travels accurately from where the work happens to where the decisions are made. Every step the information travels upward, it gets filtered, summarised, reframed, and delayed. By the time it reaches a management meeting, the constraint is invisible — not because it doesn’t exist but because the information system that should have made it visible has made it abstract instead.
Going to the Gemba is the direct response: instead of waiting for the information to travel to you, go to where the information lives. See the constraint directly. Hear from the people closest to it. Observe the system as it actually operates rather than as it is reported to operate.
Why it is a visibility intervention
Most descriptions of Going to the Gemba frame it as a leadership behaviour — a way of showing respect for front-line workers, demonstrating commitment to improvement, staying in touch with operational reality. These are real benefits. But they miss the structural point.
Going to the Gemba is a visibility intervention because it addresses the most fundamental visibility failure in hierarchical organisations: the structural separation between where decisions are made and where the constraint manifests.
In a hospital, the constraint manifests in the corridor. The decisions are made in the boardroom. Between those two places, the information travels through a hierarchy that systematically reduces its precision, urgency, and actionability. By the time corridor care appears on a board report, it is a number — percentage of patients boarded, average wait time — that describes the symptom without conveying the structure that produces it.
The person who walks the corridor at 7am, talks to the nurse who has been managing three boarded patients since midnight, watches the discharge coordinator chase a social care placement for the fourth time that week — that person sees something the board report cannot contain. The constraint is visible in the Gemba. It is invisible in the boardroom.
Don Norman showed that use errors are almost always design errors — the correct action was invisible so the user made the only choice the design made obvious. The same principle applies to organisational hierarchy. The constraint is visible at the front line. The correct action — addressing the constraint — is invisible to the decision-makers because the design of the organisation keeps them away from where the constraint lives. Going to the Gemba is the design fix: it makes the constraint visible to the person with the authority to act on it.
The two pre-conditions
Going to the Gemba produces structural change only when two pre-conditions are simultaneously met. Without either one, the walk is observational rather than transformational.
The person going to the Gemba must have the authority to act on what they see — immediately, without escalation, without committee approval. Going to the Gemba without authority produces frustration rather than improvement. The observer sees the constraint. They cannot change the consultant’s priorities, override the bed allocation system, or accelerate the social care decision. The visit makes the problem visible to the observer. It changes nothing in the system.
At Watford, the senior manager on the floor had cross-departmental authority. That is what made the Gemba walk structural rather than observational.
Going to the Gemba in a culture of fear produces a performance rather than reality. Staff show the senior visitor what they think the visitor wants to see. The real constraint remains invisible — not because it isn’t there but because the people who can see it have learned that pointing it out is dangerous.
Deming’s Point 8 (drive out fear) is not a consequence of good leadership — it is a pre-condition for the Gemba walk to work. Without it, the walk reveals the performance of the system rather than the reality of the system.
Gemba walk vs management walkround
| Dimension | Management walkround | Gemba walk |
|---|---|---|
| Purpose | Visibility (being seen), morale, symbolic leadership | Constraint identification, system observation, immediate action |
| Authority | Present but not exercised at the point of observation | Exercised immediately when the constraint is visible |
| Information flow | Front line performs for the visitor; real constraint remains invisible | Front line shows the real constraint; psychological safety makes honesty safe |
| Output | A report, a note, an action item for a future meeting | A decision made at the point of the constraint, immediately |
| Bootstrap CUSUM result | Flat line — activity without structural change | Change point — if the right constraint was addressed with the right authority |
Watford and Gloucestershire — the Gemba institutionalised
Both Bright Spot trusts demonstrate Going to the Gemba operating at different levels of institutionalisation.
Watford General put a senior manager on the floor 24 hours a day, seven days a week — with cross-departmental authority. This is the Gemba walk as a permanent structural feature rather than a periodic visit. The senior person is always at the point of the constraint, always with the authority to act, always available to hear what the front line can see. The visibility mechanism is continuous rather than scheduled.
Gloucestershire Hospitals built a control centre providing real-time data on patient flow, bed state, and discharge status — visible to the whole executive simultaneously. This is the Gemba institutionalised into infrastructure: making the Gemba visible without requiring physical presence at the point of work. The control centre is what happens when Going to the Gemba is taken seriously enough to be designed into the system rather than performed periodically.
Most NHS trusts have some form of bed management system, some form of escalation process, and some form of senior presence at peak times. What made Watford and Gloucestershire different was not the technology or the presence — it was the authority and the psychological safety. The senior person could act on what they saw immediately. The front-line staff showed them what was actually happening rather than what they hoped the senior person wanted to see. Both conditions were present. That is why the Bootstrap CUSUM change points appeared.
A practical Gemba walk protocol
Bootstrap CUSUM — the test of whether the Gemba worked
The Gemba walk is the visibility instrument. Bootstrap CUSUM is the confirmation instrument. The walk makes the constraint visible and enables the intervention. Bootstrap CUSUM tests whether the intervention produced structural change or activity.
Without Bootstrap CUSUM, the Gemba walk produces the same attribution problem as every other improvement intervention: the walk happened, something improved, the walk gets the credit. With Bootstrap CUSUM, the pre-committed prediction — made before the walk, specifying what metric should change and when — determines whether the credit is deserved.
Test whether your Gemba walk produced structural change
Upload your outcome metric data to the StepChange Analyzer. Bootstrap CUSUM will tell you whether a structural change point appeared after your intervention — or whether the constraint was not reached.
▶ Open the StepChange Analyzer