Understand Gemba and Gemba Walks in Engineering: how to observe real work in projects, construction, processes, and Owner’s Engineering before proposing improvements.
Check it out!
Gemba is the Lean principle of going to the place where work actually happens to understand the current condition through direct observation before proposing a solution. In Engineering, that place may be a construction site, an operating facility, a design office, a coordination meeting, a document-review process, or even a digital workflow in a GED/CDE environment. The goal is not simply to “visit the field,” but to confront management assumptions with facts and observe interfaces, constraints, waiting, rework, and abnormal conditions in the context where they arise.
A Gemba Walk also does not replace inspection, oversight, auditing, field surveying, or a Site Survey. These activities have their own scope, criteria, evidence, and responsibilities. Gemba is a practice for understanding work and managerial learning. Its value lies in enabling improvement decisions to be built on observed reality rather than only on aggregate indicators, presentations, or formal process descriptions.
What Is Gemba?
Gemba — also spelled genba — means, in Japanese, actual place or place where things happen. In Lean thinking, the term came to represent the place where value is actually created and where the process can be observed in operation.
In manufacturing, Gemba is commonly associated with the shop floor. In construction, it may be the jobsite. In a hospital, a treatment room. In Engineering Consulting, however, real work is not restricted to a single physical location.
Gemba can be:
- the desk where a designer consolidates input data;
- the review flow of a document;
- an interdisciplinary meeting where decisions are made;
- the jobsite where a solution is implemented;
- the electrical room where an existing condition needs to be verified;
- the operation where a system presents a recurring failure;
- the flow of submittals, RFIs, and approvals in a digital platform;
- the commissioning and punch-list closure process.
The essence is the same: directly observe the work, its conditions, interfaces, and problems.
What Is a Gemba Walk?
A Gemba Walk is a management practice for understanding the current state through direct observation and dialogue with the people who perform the work.
The Lean Enterprise Institute describes the practice as a way to “grasp the current situation”: understand the actual condition before acting. James Womack also organizes observation around three useful dimensions: purpose, process, and people.
In Engineering, this can be translated into questions such as:
- Purpose: what result does this process need to produce for the project or client?
- Process: how does work actually flow, including waiting, returns, decisions, and exceptions?
- People: who performs the work, who decides, who provides information, and what difficulties are encountered?
A Gemba Walk should not begin with a ready-made solution. It begins with disciplined curiosity.
Why Is Gemba Important for Engineering?
Complex projects generate a large amount of management information: schedules, dashboards, progress reports, punch lists, curves, meeting minutes, and KPIs.
These resources are necessary, but none fully replaces observing the actual process.
A dashboard may show that a review is late. Gemba may reveal that the document enters the queue without minimum required data and remains idle while waiting for a decision with no defined owner.
A report may show low field productivity. Observation may reveal that the team spends a significant portion of its time waiting for area release, materials, work fronts, or design information.
A spreadsheet may show many RFIs. Gemba may show that several are generated because the same interface between disciplines was not resolved at the source.
This distinction is central: data show what happened; observation helps explain how and why the system produces that result.
Taiichi Ohno’s “Plant-First” Principle
Taiichi Ohno argued that the plant was one of the most important sources of management information and emphasized the need to observe the actual place of production.
In the Toyota Production System, procedures and standards should not be defined only in the office. They needed to be tested and reviewed where the work actually occurred.
Applying this principle to Engineering requires care. Engineering is not a repetitive production line. Many decisions involve technical judgment, standards requirements, risk, and project-specific conditions.
Even so, the principle remains valid: a process improvement developed without observing the process tends to incorporate incorrect assumptions.
Gemba Is Not Unstructured “Management by Walking Around”
Visiting areas and speaking informally can be useful, but it does not necessarily constitute a good Gemba Walk.
Without purpose, the visit can become management tourism.
Without questions, the observer sees only what they expect to find.
Without evidence, individual impressions begin to be treated as facts.
Without respect for people, the practice may be perceived as personal policing.
An effective Gemba Walk needs to combine:
- a clear objective;
- flow observation;
- active listening;
- data and evidence;
- avoidance of premature judgment;
- recording of observed conditions;
- subsequent analysis;
- feedback on resulting actions.
Gemba Walk, Inspection, Oversight, Audit, and Site Survey: What Is the Difference?
These activities may occur in the same location, but they have different purposes.
| Activity | Main question | Typical output | Nature |
| Gemba Walk | How does the work actually happen and where are the difficulties? | understanding of the current state and improvement opportunities | managerial learning |
| Inspection | Does the condition meet the requirement or technical criterion? | record, checklist, evidence, nonconformity | technical verification |
| Oversight | Does the contracted execution comply with scope, design, and requirements? | oversight records, pending items, acceptance or rejection | contractual/technical control |
| Audit | Does the system/process meet predefined criteria? | findings, conformities, and nonconformities | systematic assessment |
| Site Survey | Which existing conditions need to be surveyed for a study or design? | survey, data, photos, measurements, inventory | technical information acquisition |
Mixing these purposes creates expectation and responsibility problems.
A Gemba Walk may reveal that an inspection workflow is inefficient. But the Gemba Walk itself does not replace the formal inspection required by the contract.
The name given to the visit does not define technical responsibility: purpose, criteria, evidence, and deliverables determine the nature of the work.
When the need involves independent verification, interfaces, and protection of the owner’s interests, the role of Owner’s Engineering should be structured with its own scope and responsibilities.
Observing the actual process creates more value when the team can compare what it sees with an explicitly visible state. Boards, indicators, pending items, and flows make abnormalities visible and help turn observation into management.
Gemba in Engineering Projects
It is common to think of Gemba only in construction. However, a large share of Engineering waste originates before mobilization.
Gemba in the Design Workflow
Observation can follow a deliverable from requirements input through approved issue.
The objective is to see:
- how information arrives;
- where it waits;
- how priorities are defined;
- how many times items return;
- who needs to decide;
- which interfaces create waiting;
- which systems are used;
- which parallel controls exist.
This approach connects directly to Value Stream Mapping in Engineering.
Gemba in Design Review
In design review, it can be useful to observe how comments are generated, consolidated, answered, and closed.
A company may believe it has a single review process but find, in practice, different spreadsheets, emails, PDF markups, and personal controls.
Gemba in Interface Management
Observing meetings and handoffs helps reveal where decisions remain without an owner, assumptions are transferred incompletely, or disciplines work at different maturity levels.
Gemba in Procurement
The flow can follow a requisition from specification through technical approval of the supplier.
Typical problems:
- late vendor data;
- incomplete submittals;
- reviews without defined criteria;
- scope questions;
- commercial decisions that return to Engineering;
- changes without traceability.
Gemba in Construction and Implementation
In the field, direct observation is especially powerful because it reveals constraints that reports do not fully capture.
Examples:
- team waiting for access;
- material available but not released;
- outdated drawing at the work front;
- incompatible construction sequence;
- interference between disciplines;
- equipment without an assembly area;
- safety issue preventing start;
- excessive movement;
- rework due to lack of definition.
In Lean Construction, this observation can complement Last Planner, constraint management, and plan-reliability analysis.
The Last Planner System in Engineering and Construction Projects provides a specific mechanism for turning constraints and commitments into production planning.
Gemba in Owner’s Engineering
Owner’s Engineering occupies a privileged position for observing the complete system from the owner’s perspective.
Gemba can help understand:
- how contractors interpret requirements;
- where interfaces between packages fail;
- how pending items affect sequence;
- whether documentation reflects the actual condition;
- where owner decisions block progress;
- how information flows among design, construction, and operations.
The role is not to “manage by field intuition.” Observation needs to feed governance, Project Controls, interface management, and formalized decisions.
Field observation without governance becomes anecdote; governance without contact with the field risks managing an abstract reality.
Integrating field evidence, pending items, schedule, and decisions is one of the core functions of Project Management / Project Controls.
How to Conduct a Gemba Walk in Engineering
The practice should be simple but disciplined.
1. Define the purpose
Choose a concrete question.
Examples:
- why is submittal approval taking so long?
- why does the electrical work front repeatedly start and stop?
- why do similar RFIs keep appearing?
- why is the punch list not shrinking?
- why does the review workflow have so many returns?
2. Define the process or flow to observe
A focused Gemba Walk tends to produce more learning than a generic visit.
3. Observe before intervening
Understand first. Analyze afterward.
The observer should avoid turning every abnormality into an immediate order, especially when causes and interfaces are not yet understood.
4. Ask the people who perform the work
Useful questions:
- what should happen here?
- what usually prevents it?
- how do you know what the priority is?
- what information is usually missing?
- what happens when an exception occurs?
- which step generates the most returns?
- where do you have to wait?
5. Separate fact from interpretation
“The document waited 11 days” is a fact.
“The reviewer is not productive” is an interpretation.
This discipline reduces premature conclusions.
6. Record evidence
Depending on the context:
- times;
- queues;
- quantities;
- authorized photos;
- system screenshots;
- flows;
- reported causes;
- observed deviations;
- interfaces.
7. Analyze after observation
A Gemba Walk generates inputs. Analysis may use VSM, Five Whys, A3 Thinking, Ishikawa, historical data, or other tools.
8. Return to the process
A healthy practice closes the loop: the people who participated need to know what was learned and which actions will be tested.
What Should Be Observed in an Engineering Gemba Walk?
Observation should follow the nature of the problem, but some elements appear frequently.
Flow
- where work starts;
- where it stops;
- where it returns;
- where there is waiting;
- where work accumulates.
Information
- what data are needed;
- where they come from;
- in what format;
- who validates them;
- how the version is controlled.
Decision
- who has authority;
- what evidence is required;
- how long it takes;
- what happens when no decision is made.
Interface
- who hands off to whom;
- what acceptance criterion exists;
- how conflicts are resolved.
Abnormality
- how the system indicates that something deviated from standard;
- how long it takes for someone to notice;
- what the response mechanism is.
People
- actual difficulties;
- manual rework;
- duplicate controls;
- informal dependencies;
- concentrated knowledge.
Gemba and Visual Management
Good visual management helps expand what is observed at the Gemba.
The objective is not to decorate walls or dashboards. It is to make abnormal conditions easy to identify.
Examples:
- RFI aging;
- WIP above the limit;
- blocked packages;
- unremoved constraints;
- documents awaiting approval;
- overdue punch items;
- interfaces without an owner.
The article on Visual Management in Engineering Projects examines this role in greater depth.
Gemba shows the actual condition; Kaizen organizes the response. This combination prevents a field visit from ending as a scattered list of observations and creates an improvement cycle with problem, cause, countermeasure, and verification.
Explore Kaizen and Continuous Improvement Applied to Engineering
Gemba and Kaizen
Gemba and Kaizen are complementary.
Gemba helps understand the actual state.
Kaizen provides the continuous-improvement logic for turning learning into tested and standardized countermeasures.
A common mistake is trying to “do Kaizen” without going to the process. The team discusses solutions in a meeting room without understanding the actual obstacles.
The reverse is also incomplete: continuous observation without turning learning into improvement produces only repetitive diagnosis.
Gemba and the Five Whys
Taiichi Ohno strongly associated fact-based observation with cause investigation. The Five Whys method seeks to prevent the organization from stopping at the superficial cause.
If a construction activity did not start:
- Why? The team did not receive release.
- Why? The previous inspection was not closed.
- Why? There was a documentation issue.
- Why? The document was submitted with conflicting information.
- Why? The interface between two disciplines had no defined criterion.
The number five is not a mathematical rule. The objective is to deepen the investigation until reaching a cause that can be addressed consistently.
Gemba and A3 Thinking
When observation reveals a relevant problem, A3 Thinking can organize the reasoning.
The typical sequence connects:
- context;
- current state;
- objective;
- cause analysis;
- countermeasures;
- plan;
- follow-up.
Gemba feeds A3 with facts. Without this basis, A3 risks becoming an office narrative.
What a Gemba Walk Should Not Do
It should not look for people to blame
The focus is understanding the system and process.
It should not become a surprise audit
If the purpose is an audit, it should be declared and conducted using its own criteria.
It should not generate improvised orders
Incomplete observation may lead to a countermeasure that improves one stage and harms another.
It should not ignore safety and authorization
In the field, access, photography, and interaction with teams must respect project rules.
It should not treat reports as the only evidence
People’s accounts are essential, but they should be combined with observation, data, and documents.
Example: Gemba in an RFI Workflow
Imagine a project with a large RFI backlog.
A dashboard-only analysis may show:
- 120 open RFIs;
- average aging of 18 days;
- 35 above the SLA.
A process Gemba can follow selected RFIs from opening through response.
Observation may reveal:
- incomplete questions;
- routing to the wrong people;
- need to consult multiple disciplines;
- lack of authority to respond;
- completed response waiting for formal approval;
- duplicate RFIs because the field cannot see previous responses.
The countermeasure changes completely depending on the cause.
The problem may not be “not enough engineers to respond.” It may be poor process design.
Example: Gemba at an Installation Work Front
An electrical team appears to have low productivity.
In the field, it is observed that:
- the work front is only partially released;
- materials are stored far away;
- civil supports have not been completed;
- drawings contain clashes;
- access requires daily authorization.
Demanding individual productivity will not solve the system.
Engineering needs to address constraints, interfaces, sequence, and logistics.
When the problem lies at the interface among design, supplier, and execution, field observation needs to be connected to requirements, scope, oversight, pending items, and acceptance criteria. This integration is a typical Owner’s Engineering function.
Which Business Problems Indicate a Need to Go to the Gemba?
Some symptoms show a gap between management and operational reality:
- reports say everything is under control, but deadlines continue to deteriorate;
- meetings discuss status without converging on a cause;
- problems reappear after corrections;
- departments blame one another;
- indicators do not explain why the flow is slow;
- construction and design have different versions of reality;
- decisions are made with incomplete data;
- formal procedures differ from actual work;
- digital automation has not eliminated parallel controls.
In these situations, more reporting may not be the answer. The actual process needs to be understood.
How to Turn Observation into Engineering Action
A Gemba Walk does not end with the visit.
Findings need to be transformed into a decision process:
- record the observed condition;
- define the problem;
- quantify impact;
- identify causes;
- prioritize countermeasures;
- test;
- verify effect;
- update the standard or process.
This sequence connects Gemba to Kaizen and continuous improvement when the content is published and, at the systemic level, to process management and governance.
How to Commission a Field- and Process-Based Diagnosis?
A company does not need to contract “a Gemba Walk” as an isolated product.
It is more useful to contract for the result that needs to be achieved.
Depending on the problem, the scope may combine:
- technical survey;
- interviews;
- direct observation;
- document analysis;
- AS-IS mapping;
- Value Stream Mapping;
- constraint analysis;
- interface analysis;
- authorized photographic records;
- TO-BE design;
- action plan;
- indicators;
- assisted implementation.
If the problem concerns physical condition, the work may take the form of a Site Survey, Due Diligence, or technical survey.
If the problem concerns work-system performance, observation needs to be integrated into a process diagnosis.
A good technical visit needs to end in better decisions — not merely more photographs, meeting minutes, or lists of observations.
When the need requires integrating field conditions, documentation, interfaces, and governance, A3A Engenharia’s Technical Engineering Consulting can turn scattered evidence into a structured diagnosis and action plan.
How Engineering Consulting Organizes This Type of Diagnosis
Engineering Consulting is especially useful when symptoms span multiple disciplines or contracts.
It can integrate:
- field conditions;
- documentation;
- requirements;
- contracts;
- planning;
- interfaces;
- risks;
- costs;
- governance.
This avoids an overly local interpretation. A constraint observed in construction may originate in procurement. A procurement delay may originate in design. A design error may originate in a poorly defined requirement.
The role of Engineering Consulting is to transform fragmented observations into a structured diagnosis and solution plan.
How A3A Engenharia Applies This Principle
A3A Engenharia A3A Engenharia uses direct observation in activities such as surveys, technical due diligence, Design Review, Owner’s Engineering, oversight, commissioning, and process diagnosis.
The objective is not to use the term Gemba as a commercial label, but to apply the right principle: technical decisions need to be connected to the actual condition of the project.
In Owner’s Engineering contracts, this may mean comparing reported progress against actual work fronts, pending items, documents, and constraints.
In process diagnosis, it may mean following a deliverable or decision through the entire flow and identifying where the system actually consumes time.
In a Site Survey, it means surveying the existing condition before defining a design solution.
The practice changes with the service; the principle remains.
Final Considerations
Gemba is a managerial-learning tool before it is a visit technique. Its contribution to Engineering lies in reducing the gap between the reality of work and the reality described by reports, procedures, and indicators.
A good Gemba Walk does not end with a list of impressions. It produces facts, better questions, and a more reliable basis for cause analysis and improvement.
When integrated with VSM, Kaizen, A3 Thinking, Project Controls, and Engineering Consulting, direct observation stops being episodic and begins to feed a decision system that is more closely aligned with what actually happens in design, construction, and operations.
Technical References
[1] OHNO, Taiichi. Toyota Production System: Beyond Large-Scale Production. Portland: Productivity Press, 1988.
[2] LEAN ENTERPRISE INSTITUTE. Gemba. Available at: https://www.lean.org/lexicon-terms/gemba/.
[3] LEAN ENTERPRISE INSTITUTE. Gemba Walk. Available at: https://www.lean.org/lexicon-terms/gemba-walk/.
[4] WOMACK, James P. Gemba Walks. Available at: https://www.lean.org/lexicon-terms/gemba-walk/.
[5] A3A ENGENHARIA. Value Stream Mapping in Engineering. Available at: https://a3aengenharia.com.br/conteudo/artigos-tecnicos/value-stream-mapping-engenharia-fluxo-valor/.
Frequently Asked Questions
Gemba means the actual place where work happens and value is created. In Engineering, it may be a jobsite, facility, design office, review workflow, or digital process.
It is a management practice for understanding the current state through direct observation and dialogue with those who perform the work before formulating a solution.
No. Inspection verifies compliance with requirements; Gemba seeks to understand how the process actually works and where difficulties, waste, and abnormal conditions arise.
Yes. It can be used in design workflows, document review, procurement, RFIs, commissioning, GED/CDE, and other Engineering processes.
No. A Site Survey is a technical survey of existing conditions. Gemba is a practice for understanding work. The two activities may occur in the same environment but have different objectives and deliverables.
It depends on the problem, but may include times, queues, WIP, rework, constraints, interfaces, authorized visual evidence, team accounts, and system information.
Gemba helps understand reality; Kaizen uses that understanding to test countermeasures, measure results, and consolidate improvements.
Complementary Technical Materials
Related Solutions
- Process, Workflow, and Technical Approval Management
- Management of Pending Items, RFIs, and Nonconformities
- Project, Program, and Portfolio Governance
