Gemba means the place where real work happens:
- construction site,
- workshop,
- operational office,
- control room,
- maintenance center,
- administrative department.
A Gemba diagnosis consists in directly observing:
- flows,
- interactions,
- problems,
- interruptions,
- and real working conditions,
in order to understand how the system really works.
Lean considers that:
- operational reality cannot be understood only through reports or indicators.
- To improve an organization sustainably, you have to go and see real work.
Simple definition
The Japanese term Gemba means:
"the real place".
In a Lean approach, Gemba represents:
- the place where value is created,
- and where problems appear concretely.
A Gemba diagnosis consists in:
- observing operations on the ground,
- listening to teams,
- understanding flows,
- identifying losses,
- and analyzing the real causes of dysfunctions.
Unlike a conventional audit focused mainly on:
- procedures,
- documents,
or indicators,
a Gemba diagnosis seeks to understand:
- how work is actually performed,
- and why certain gaps appear.
Why it matters
In many organizations:
decisions are made far from the field,
based on:
- reports,
- indicators,
- or partial perceptions.
- But real work is often very different from "theoretical" work.
Field teams regularly have to:
- work around problems,
- improvise,
- manage interruptions,
- compensate for organizational defects,
- or arbitrate contradictory constraints.
Very often:
major losses remain invisible in dashboards.
Lean therefore considers that:
the best improvement opportunities appear directly in the field.
A Gemba diagnosis makes it possible in particular to:
- reveal hidden waste,
- understand operational difficulties,
- improve flows,
- and reconnect decisions with the reality of the system.
Concrete example
Example in construction
On a complex construction site:
the schedule shows an activity as "in progress".
But by observing the field:
- teams are waiting for approvals,
- some areas are not ready,
- materials are not available,
- and companies obstruct one another.
The real problem does not appear in reporting.
The Gemba diagnosis then makes it possible to:
- visualize interruptions,
- understand the causes of productivity losses,
- and improve the real coordination of the site.
Example in services
In an administrative department:
indicators show a high level of activity.
But the Gemba reveals:
- multiple approvals,
- constant follow-ups,
- searches for information,
- and a high cognitive load.
Improvement will therefore not focus only on:
- people,
but on: - flows,
- interfaces,
- and work organization.
Common mistakes
Using Gemba as field control
Gemba is not a disciplinary audit.
Observing only results
Lean seeks to understand:
- mechanisms,
- flows,
- and real causes.
Limiting yourself to indicators
Major losses are sometimes invisible in dashboards.
Looking for someone to blame
A Gemba diagnosis aims at:
- learning,
- and improving the system.
Doing Gemba only occasionally
Field observation should become a regular practice.
Indicators to track
A Gemba diagnosis can rely on several indicators:
- Waiting time
- Number of interruptions
- Real cycle time
- Number of rework loops
- Unnecessary movements
- Flow variability
- Number of open constraints
- Commitment reliability
- Level of overload
- Time spent coordinating
- Problem resolution rate
- Team satisfaction
The objective is to measure:
- how the system really works,
- not only its theoretical results.
Frequently asked questions
Why go to the field if indicators already exist?
Because indicators often show:
- consequences,
but rarely: - the real causes of problems.
Who participates in Gemba?
Managers,
operational teams,
Lean managers,
project leadership,
or continuous improvement teams.
Does Gemba concern only industry?
No. It also applies to:
- services,
- design offices,
- projects,
- support functions,
- and administrative organizations.
Is Gemba used to control teams?
No. It is mainly used to:
- understand,
- learn,
- and improve the system.
How often should Gemba be done?
Lean encourages regular practice in order to:
- stay connected to real work,
- and detect gaps quickly.
Leanfinity offer link
Gemba maturity diagnosis
Leanfinity supports organizations in:
- field analysis of flows,
- identifying performance losses,
- making dysfunctions visible,
- and building improvement plans adapted to operational reality.
Our approach aims to reconnect:
- strategy,
- management,
- and the real field.
How it works
Define
Clarify what must be observed and why.
See
Go to the field and observe real flows, gaps, and interfaces.
Listen
Capture the knowledge of the people closest to the work.
Improve
Act on causes so the system improves sustainably.
A Gemba diagnosis is based on several key principles.
Go and see in the field
Managers and improvement teams directly observe:
Observe without judging
Lean seeks to understand:
The objective is:
Listen to teams
Field employees often know:
The Gemba diagnosis values that knowledge.
Make problems visible
Lean seeks to visualize:
Understand root causes
The objective is not only to observe symptoms.
A Gemba diagnosis seeks to understand: