Gemba: definition, Gemba Walk and industrial application

The word Gemba (現場) literally means 'the real place' in Japanese. In lean management, the Gemba is the place where real value is created : the production shop floor, the assembly line, the warehouse. It is on the Gemba that real problems appear, that waste becomes visible, that improvement opportunities reveal themselves. The Gemba Walk is a fundamental lean practice: going into the field, observing without preconceptions, engaging the teams and identifying the improvement levers. For an industrial SME, the Gemba Walk changes everything: instead of deciding from the office, you decide with real data from the field.

What is Gemba? Definition and origin

The Gemba is the heart of lean management. It is the place where production happens, where customers are served, where value is created. For a plant, it is the shop floor. For a warehouse, it is the picking area. For an office, it is the workstation. The Gemba is not an abstract concept — it is a real physical place where you can observe, measure and improve.

The concept of Gemba comes from Toyota, in the 1950s. Taiichi Ohno, the engineer who created the Toyota Production System (TPS), established a simple rule: 'Go and see the Gemba'. Before taking a decision, before launching an improvement, before changing a process, you must go and see the field. No meeting, no report, no statistics — just direct observation.

Why this approach? Becausea large share of the real problems is not visible in the reports. The data reported from the field is often filtered, smoothed or misinterpreted. By going to the Gemba, you see the real problems: wasted time, quality defects, poorly organised stock, frustrated teams.

The Gemba Walk in 5 steps has become the standard practice for putting this philosophy to work. It is a structured visit to the field, with a clear objective, a rigorous method and measurable follow-up.

The Gemba Walk in 5 steps: the complete method

An Gemba Walk is not just a walk around the plant. It is a structured approach, with precise steps, a defined timing and measurable results.

Step 1: Prepare the visit (1-2 days beforehand)

Before going out into the field, you must prepare your visit : define a clear objective — what are you going to observe? Which process? Which problem? Which waste?

• 'Observe the assembly process to identify unplanned stoppages'
• 'Analyse the material flow in the warehouse to reduce picking times'
• 'Understand why quality is falling on line 3'

You must also prepare your team : production manager, operators, team leaders. Ideally, you include the people who actually work on the process — they are the ones who know the real problems. Finally, prepare your tools : observation sheet, camera, stopwatch, checklist. You are going to note what you see, not what you think you see.

Step 2: Observe without judging (1-2 hours in the field)

This is the most important step: observe without preconceptions. You go down to the Gemba and you watch. You do not criticise, you do not judge, you do not interrupt the work. During this observation, you note:

• Flows : how does material circulate? Are there waiting times? Any backtracking?
• Times : how long does each operation take? Is there any idle time?
• Waste : unnecessary stock, unnecessary movement, waiting, defects?
• Teams : how do the operators work? Are they focused? Frustrated? Engaged?
• Problems : what obstacles do the teams encounter?

The observation must be neutral and factual. You do not say 'This is badly organised'. You say 'I observed 3 stoppages of 15 minutes each, caused by waiting for raw material'.

Step 3: Identify the waste and the opportunities

Once your observation is complete, you analyse what you have seen. You identify the waste (muda in Japanese): the activities that create no value for the customer. The 7 classic lean wastes:

• Overproduction : producing more than necessary
• Waiting : downtime, queues
• Unnecessary transport : moving material more than necessary
• Unnecessary processing : steps that create no value
• Inventory : poorly managed raw material, work in progress and finished goods
• Unnecessary motion : inefficient movements, searching for tools
• Defects : rework, scrap, touch-ups

For each waste identified, you ask the question 'Why?' 5 times in a row (see the 5 Why method) to trace back to the root cause, not just the symptom. Example: 'Why is there a 15-minute wait?' → 'Because the material is not delivered on time.' → 'Why?' → 'Because the warehouse does not know when it is needed.' → 'Why?' → 'Because there is no communication system between production and the warehouse.'

Step 4: Engage the teams and co-create the solutions

This is a crucial step: you do not decide alone. You involve the teams on the ground. They are the ones who know the process, the constraints and the possible solutions best. You organise a feedback meeting with the operators, the team leaders and the managers. You present your observations, your analyses and your questions. You listen to them.

Teams will often propose simple and effective solutions — because they live with the problem every day. Example: "We observed a 15-minute wait. The operators told us: 'If the warehouse prepared the material for us 30 minutes earlier, we would no longer be waiting.' Simple solution: change the preparation schedule in the warehouse." This joint development also createsengagement : the teams feel heard, involved and responsible for the improvement.

Step 5: Formalise an action plan and ensure follow-up

At the end of the Gemba Walk, you must formalise a clear action plan : What? (which improvement), Who? (person responsible), When? (deadline), How? (steps), Measure? (how to measure the result).

Improvement	Owner	Deadline	Steps	Measure
Reduce material waiting time	Warehouse manager	15 July	1. Analyse current schedules 2. Propose a new schedule 3. Trial for 1 week 4. Validate	Waiting time: 15 min → 0 min

Then you follow up regularly : every week you check whether the action plan is progressing, you measure the results and you adjust if necessary. Without follow-up, improvements are forgotten and nothing changes. With regular follow-up, results accumulate and a culture ofcontinuous improvement takes hold.

Measurable benefits of the Gemba Walk

A well-conducted Gemba Walk generates concrete, measurable results. Here are the typical benefits observed in industrial SMEs:

• Productivity : regular Gemba Walks reduce waste and significantly increase productivity .
• Quality : by identifying the root causes of defects, you appreciably improve quality.
• Costs : reducing waste appreciably lowers costs.
• Safety : the Gemba Walk reveals hidden risks; by correcting them, you significantly reduce accidents.
• Team engagement : absenteeism and turnover down, satisfaction up.

Illustrative example: a mechanical engineering SME with 80 employees that introduces monthly Gemba Walks typically sees, after a few months, higher productivity, fewer defects, lower stock and stronger safety.

Gemba Walk implementation checklist

Preparation (before the first Gemba Walk)

• Define the objective of the Gemba Walk (which process? which problem?)
• Identify the participants (production manager, operators, team leaders)
• Prepare the tools (observation sheet, camera, stopwatch)
• Communicate to the teams (explain the objective, reassure them about the intent)
• Schedule the visit (date, time, duration 1-2 hours)

During the Gemba Walk

• Observe without judging (note facts, not opinions)
• Ask open questions ('Why?', 'How?', 'Since when?')
• Listen to the teams (they are the ones who know best)
• Take photos/videos (document the waste)
• Time the operations (measure the actual times)

After the Gemba Walk

• Analyse the observations (waste, root causes)
• Feedback meeting (present to the teams, co-create the solutions)
• Formalise the action plan (what, who, when, how, measure)
• Assign responsibilities and schedule the weekly follow-up
• Measure the results (productivity, quality, costs, safety)

Regularity

• Schedule regular Gemba Walks (weekly or monthly)
• Involve every level (management, supervisors, operators)
• Document the improvements (Gemba Walk database)
• Communicate the results (KPI boards, team meetings)

Common mistakes to avoid

Mistake 1: the flying visit. 15 minutes in the field are not enough — you see nothing. A Gemba Walk must last at least 1-2 hours.

Mistake 2: criticising the teams. 'Why are you doing it that way?' shuts down the dialogue. The Gemba Walk is a collaborative approach, not an inspection: you observe, you listen, you learn.

Mistake 3: no follow-up. Without follow-up or measurement, nothing changes and the improvements are forgotten. Follow-up is crucial.

Mistake 4: no regularity. A Gemba Walk every 6 months does not build a culture. Gemba Walks must be regular : weekly or monthly.

Mistake 5: top-down decisions. Deciding alone without consulting the teams makes improvement something endured rather than adopted. The Gemba Walk must be co-creative.

Frequently asked questions

Who should carry out the Gemba Walks?

Gemba Walks should be carried out by production managers, team leaders and ideally senior management. But it is not a top-down inspection. It is a collaborative approach. Operators should take part too — they know the shop floor best. Ideally, you create mixed teams: management + supervisors + operators. Everyone learns, everyone contributes.

How often should Gemba Walks be carried out?

It depends on your context. For an SME starting out, we recommend once a week (1-2 hours). It creates a habit, it shows that this is a priority and it generates quick results. Once the culture takes hold, you can move to once a month (in greater depth). But never go below once a month — otherwise you lose the momentum.

How can the teams be involved in the Gemba Walks?

The teams must be informed in advance (no surprises). You explain the objective to them: 'We want to understand how to improve the assembly process. We are going to observe and ask you questions.' During the Gemba Walk, you listen to them, you ask open questions and you note their ideas. Afterwards, you involve them in co-creating the solutions. They must feel that their opinion counts and that you are genuinely listening.

What is the ROI of a Gemba Walk?

The ROI is generally very fast. The improvements identified during a Gemba Walk often generate gains within 2-4 weeks: fewer stoppages, better quality, lower stock. Over 6 months, you generally see a significant improvement in productivity. The cost of a Gemba Walk is close to nil (just time). The ROI is therefore very high.

How can the impact of a Gemba Walk be measured?

You must define clear KPIs before the Gemba Walk: productivity (parts per hour), quality (defect rate), costs (cost per part), safety (number of accidents), lead times (cycle time). You measure these KPIs before the Gemba Walk, then measure them again after 2 weeks, 1 month and 3 months. You see the improvement. You communicate the results to the teams — that motivates them to keep going.