The hidden forces in organisations and Gemba
Gemba (現場) and the Unconscious
Gemba is a Japanese term meaning 'the real place' or where value-creating work actually happens. A production report can tell you output dropped on Tuesday. A dashboard can show a growing queue. A customer complaint can describe what went wrong. Gemba asks a different question: what is actually happening where the work is done?
That is why the Japanese management philosophy of Gemba has stayed relevant far beyond its roots in manufacturing. It gives leaders, managers, and teams a simple discipline: leave assumptions behind, go to the real place, observe the real work, and learn from the people closest to it.
Gemba is one of the key takeaways from my guest appearance on the SAP SuccessFactors 'The Human Factors' podcast with Michael Esau and Simon Humphreys.
A Gemba Walk is a great way to uncover 'hidden forces' impeding business success and especially in high investment, value-driven, large-scale improvement or change initiatives because 'hidden forces' or the unconscious tends to naturally coalesce around workplace change because of the anxiety potential changes brings and creating significant impediments to transformation which are unseen to the untrained eye.
Common management techniques and tools such as programme management, project management and change management are essential to successfully deliver an initiative, however, the methodology used often detaches or distances programme board leaders from what is actually happening on the ground including changes to working practices, emotions, reactions, working relationships and personalities. Highlight reports are useful and can tell a good story but if you are a leader facing a potentially unsuccessful initiative or keen to ensure a successful one, a Gemba Walk - literally going from the board room to the desktop or shop floor - is one of the practical things you can do to get a different perspective on risks and issues, and to drive or enable value.
Go to Gemba enables leaders to encounter and proactively counteract 'hidden forces' at the desktop rather than board level, and can help to turnaround initiatives that are heading in the wrong direction.
Why do organisations invest so much in change, yet still struggle with resistance, engagement and turning strategy into sustained behaviour?
Perhaps part of the answer lies in something we don't spend enough time talking about: what sits beneath the surface. We explore the conscious and unconscious forces that influence how people respond to change, why compliance is very different from genuine commitment, the role leaders play in creating the conditions for people to move forward, and why getting closer to where work actually happens can tell us far more than another programme report.
Listen to the podcast by clicking on the icons below.
Apple Podcasts
Spotify
Amazon Podcasts
Pocket Casts
(現場) About Gemba
Gemba is often translated as 'the real place'. In management, it means the place where value is created. That might be a factory line, an open plan office, a desktop area, a hospital ward, a warehouse aisle, a shop floor, a hotel laundry room, a call centre queue, or a maintenance bay. The point is not the location itself. The point is seeing work as it happens, not as it is imagined from a report.
What Gemba really means
Gemba is a core idea in lean management and is closely linked with Toyota’s production system. The Japanese phrase 'genchi genbutsu', often translated as 'go and see for yourself', captures the same spirit.
At its best, Gemba is a response to a common management problem: decisions made too far from reality.
When people rely only on summaries, they miss the small details that shape performance. A process map may look tidy, but the person doing the job may be walking across the site twenty times a shift. A quality rule may sound clear, but the label on the shelf may be hard to read under poor lighting. A delivery target may appear reasonable, but the tools needed to meet it may be shared, missing, or placed in the wrong area.
Gemba makes those problems visible.
It also changes the relationship between managers and employees. Instead of treating workers as a source of labour only, it treats them as a source of knowledge. The person who handles the process every day often sees waste, risk, and friction long before anyone else does.
That is why Gemba is not just a productivity method. It is also a way to build trust.
The core principles of Gemba
Gemba looks simple from the outside, but it works because it rests on a few strong principles.
Go to the real place
The first principle is physical or direct presence. The manager goes where the work happens. If the work is digital, this might mean sitting with a support agent, joining a live incident review, or watching how a user request moves through a system.
The goal is to see the work, not to perform a ceremonial walkabout.
Good Gemba practice means observing the flow, the tools, the steps, and the conditions. It means noticing what helps the work and what gets in the way.
Observe before judging
A useful Gemba visit starts with curiosity. Leaders watch before they comment. They ask what is happening and why. They avoid jumping to fixes too early.
This matters because the visible problem is often not the real problem. A missed target might look like slow work. After observation, it may turn out that the team is waiting for approvals, re-entering data, searching for missing items, or stopping to correct defects from an earlier step.
Observation gives the team a better starting point.
Respect the people who do the work
Respect is one of the most important parts of Gemba. It means listening without blame. It means asking employees to explain the process in their own words. It means treating front-line experience as evidence.
A manager who asks, 'Why did you do it this way?' can sound accusatory. A manager who asks, 'Can you show me what happens next?' invites learning.
That difference matters. If people feel inspected, they hide problems. If they feel respected, they share them.
Focus on the process, not the person
Gemba does not exist to catch people out. It exists to improve the system of work.
When something goes wrong, the question is not, 'Who failed?' The better question is, 'What in the process allowed this to happen?'
That shift protects morale and leads to better fixes. Training may help in some cases, but many problems come from unclear instructions, poor layout, bad handovers, unreliable equipment, or conflicting targets.
Improve in small, steady steps
Gemba is closely tied to kaizen, the practice of continuous improvement. The aim is not always a large transformation. Often, the best gains come from practical changes that remove daily friction.
That could mean moving equipment closer to where it is used, changing the order of tasks, improving signs, simplifying a form, or making stock levels easier to see.
Small changes can compound quickly when they are based on real work.
What going to the Gemba looks like in practice
'Going to the Gemba' means visiting the real place of work with a clear purpose. It is sometimes called a Gemba walk, but the phrase can be misleading. A casual walk is not enough. The value comes from careful observation and honest conversation.
A simple Gemba visit might follow this pattern:
Choose a specific process to observe.
Stand where the work happens.
Watch the steps from start to finish.
Ask open questions.
Listen to the people doing the work.
Look for delays, rework, excess movement, confusion, and safety risks.
Agree on next steps with the team.
The best questions are plain and practical:
What should happen at this step?
What makes the task harder than it needs to be?
Where do delays usually occur?
What information do you need but do not always have?
What would you change first if you could?
How do you know if the work has been done correctly?
The tone of those questions matters. Gemba is not a performance review. It is not a surprise inspection. It is a way to understand reality.
A good leader also resists the urge to solve everything during the visit. Some changes are obvious and safe to make quickly. Others need testing. The team should leave the discussion knowing what will happen next, who will act, and when they will hear back.
When managers ask for input and then disappear, Gemba loses credibility. Follow-through turns observation into trust.
Real-world examples of Gemba in action
Gemba began in manufacturing, but the principle applies anywhere work flows from one person, place, or system to another.
Toyota and the factory floor
Toyota is the best-known example of Gemba thinking. Leaders and engineers are expected to understand the production line by seeing it directly. Problems are treated as chances to learn, not as irritations to hide.
One widely known lean practice is stopping or slowing production when a defect appears, so the cause can be understood. That only works in a culture where people are trusted to raise problems. Gemba supports that culture because leaders can see the conditions that created the issue.
For example, if a repeated assembly fault appears, the answer may not be 'work more carefully'. A Gemba visit might reveal that parts are presented in a confusing order, a tool is awkward to reach, or a visual guide is unclear. Fixing the work environment prevents the defect more reliably than reminding people to try harder.
Hospitals and patient care
In healthcare, the Gemba is often the ward, theatre, pharmacy, or reception area. Leaders who observe patient flow can see delays that would be hidden in a spreadsheet.
A hospital team might study why patients wait too long for discharge medicine. From a report, the issue may look like a pharmacy delay. At the Gemba, the team may discover that discharge decisions are made in batches, prescriptions arrive with missing details, and ward staff spend time chasing updates by phone.
Seeing the full flow helps leaders make better choices. They can improve handovers, clarify information requirements, or test earlier communication between ward and pharmacy teams.
This does not only help efficiency. It can reduce stress for staff who are tired of working around the same avoidable problems.
Warehouses and fulfilment
In a warehouse, Gemba can show how layout affects productivity. A manager might see that frequently picked items sit far apart, forcing workers to walk long distances. They might notice that packaging sizes are stored away from the packing station, or that damaged barcodes create repeated scanning issues.
Those details rarely appear in high-level performance numbers. The numbers show the result. Gemba shows the cause.
A practical improvement might involve placing fast-moving items closer together, changing shelf labels, or adjusting replenishment timing. None of those improvements requires a grand strategy. They require attention to the real work.
Restaurants and service teams
In a restaurant, the Gemba could be the kitchen pass, prep area, or dishwashing station. If orders are late, a manager might first blame staffing levels. A Gemba visit may tell a different story.
Perhaps ingredients are stored in several places. Perhaps the ticket printer sits where cooks cannot see it easily. Perhaps one station becomes overloaded while another waits. By watching the dinner service, the manager can see the actual flow of work and make changes that help the whole team.
This is where Gemba improves employee engagement. People feel the difference when leaders remove real obstacles instead of simply asking for more effort.
How Gemba improves decision-making
Gemba improves decisions because it closes the gap between reported performance and lived experience.
Reports are useful, but they compress reality. They show trends, totals, averages, and exceptions. Gemba adds context. It answers questions that data alone cannot answer.
Decision based only on reports | Decision improved by Gemba |
Output is low, so ask the team to work faster. | Output is low because materials arrive late, so fix the supply point. |
Error rates are up, so add more checks. | Errors come from unclear labels, so improve visual guidance. |
Customer response time is slow, so set a tougher target. | Response time is slow because cases are routed badly, so change the routing rules. |
Staff seem disengaged, so run a survey. | Staff are frustrated by repeated blockers, so remove the blockers and involve them in fixes. |
The impact is practical. Leaders make fewer assumptions. Teams spend less time arguing about what is happening. Improvement work starts from shared evidence.
Gemba also improves the quality of questions. A leader who has seen the process can ask about specific handovers, tools, timings, and constraints. That makes discussions sharper and more useful.
It can also stop costly mistakes. Without Gemba, organisations may buy new software, hire extra staff, or redesign targets when the real issue is simpler. A missing part, confusing form, poor layout, or unclear instruction may be the true cause.
How Gemba boosts productivity and employee engagement
Productivity improves when people spend less time fighting the process. Gemba helps reveal the forms of waste that slow teams down:
Waiting for materials, approvals, decisions, or information
Rework caused by errors or unclear instructions
Unnecessary movement between tools, stations, or systems
Overprocessing, where a task has more steps than needed
Searching for items, files, or answers
Bottlenecks that shift pressure onto one person or team
By removing those barriers, organisations increase productive time without demanding constant extra effort.
Employee engagement improves for a related reason. People are more likely to care about improvement when their experience shapes the answer. Gemba shows that leadership is willing to learn from the front line.
That does not mean every suggestion should be accepted. It means every serious concern should be heard, tested, and answered.
There is also a safety benefit. Hazards often appear first as small workarounds. A cable taped down, a missing guard, an awkward lift, or a rushed handover can become normal if nobody looks closely. Gemba brings those signals into view before they become larger problems.
Common mistakes to avoid
Gemba can fail when leaders treat it as a ritual instead of a learning practice.
One common mistake is arriving with a fixed answer. If the purpose is only to prove a theory, people notice. Observation becomes theatre.
Another mistake is focusing on individual behaviour while ignoring the system. If every visit ends with someone being corrected, employees will stop sharing the truth.
A third mistake is failing to act. Teams will usually tolerate slow progress if they receive honest updates. What damages trust is repeated listening with no visible response.
Good Gemba habits are simple:
Visit regularly, not only during a crisis.
Explain why you are there.
Ask open questions.
Thank people for showing the real process.
Record what you learn.
Test changes with the team.
Return to see whether the change worked.
Making Gemba part of everyday management
Gemba works best when it becomes a normal habit, not a special event. Leaders do not need to spend hours observing every process. They do need to build a routine of seeing work directly and responding respectfully.
Start small. Choose one process that causes delay, frustration, defects, or customer complaints. Visit the real place. Watch. Ask. Listen. Then work with the people involved to test one improvement.
After that, return.
That return visit is powerful. It shows that Gemba is not a passing interest. It shows that employee knowledge led to action. It also checks whether the change helped in real conditions.
Gemba Explained How Going to the Workplace Boosts Productivity and Employee Engagement is more than a management idea with a Japanese name. It is a practical reminder that the best decisions often start with direct observation. Go to the place where value is created, respect the people who create it, and improve the work with them.
The shortest route to better performance may be leaving the report behind for an hour and seeing the work for yourself.
Comments