The First Thing a Leader Should Do at the Genba

What is the first thing you do when you go to the Genba?

Look at the performance boards? Ask for a project update? Talk to the supervisor?

No. Before doing any of those things, simply observe for a while.

See Before You Listen

A leader visited the Genba and immediately asked for an update on a troubled project. The team explained, “The machine manufacturer supplied us with a bad machine.”

The conversation quickly turned toward the supplier: What should the supplier fix? Who should contact them? How could the team hold them accountable?

While everyone discussed the supplier, I quietly observed the machine.

Eventually, the leader noticed that I was not participating in the conversation. He turned to me and asked, “What do you see?”

I pointed toward the fixture and asked, “Why is that pin moving?”

The pin was not supposed to move. The fixture was broken.

Once the fixture was repaired, the problem disappeared. The machine itself had not been the real issue.

Instead of asking why the fixture had broken, however, the team initially tried to convince me that the machine should still work properly with a broken fixture. They had become so committed to their explanation—that the supplier had delivered a bad machine—that contradictory evidence was difficult to accept.

The leader shook his head and said, “Why didn’t I see the problem before listening?”

His question revealed an important lesson: Once we hear someone else’s explanation, it becomes difficult to see the situation with fresh eyes.

Fifteen Minutes of Silence

On another occasion, I arrived at the Genba before my coach. By the time he arrived, I had already observed the operation and formed several impressions.

As soon as he approached, I asked, “Would you like to hear what I observed?”

He responded, “Thanks, but no thank you.”

He then stood beside the production line and silently observed it. He did not ask for an update. He did not read the reports. He did not request anyone’s opinion.

For fifteen minutes, he simply watched.

Then he turned to me and said, “I’m ready to discuss.”

At first, his response had surprised me. Later, I understood what he was protecting: his ability to form an independent first impression.

He wanted to see the actual condition before hearing my interpretation of it.

Information Is Never Completely Neutral

How do you know whether the information given to you is biased?

The honest answer is that you often do not.

Bias may be intentional, but frequently it is not. People naturally organize information around the explanation they currently believe. They emphasize facts that support their conclusions and overlook facts that challenge them.

In the machine example, the team was not necessarily trying to mislead the leader. They genuinely believed the supplier was responsible. Their report reflected that belief, so the conversation began with the machine manufacturer rather than the condition of the fixture.

By the time the leader looked at the equipment, the team’s explanation had already shaped what everyone expected to see.

This is why observation must come before explanation.

Reports Explain the Current Direction

Reports are useful. Performance boards are useful. Updates from team members are useful.

But they are not the same as direct observation.

Reports usually contain information that explains or justifies the current condition, conclusion, or direction. They tell us what people believe is happening and why they believe it is happening. That information is important, but it may conflict with what a leader would notice independently.

A report can direct your attention before you have had a chance to decide where your attention belongs.

The explanation becomes a lens—and every lens makes some things clearer while making other things harder to see.

The Value of a Leader’s Fresh Eyes

A leader brings something valuable to the Genba: fresh eyes.

That value disappears when the leader immediately asks for opinions, explanations, or updates. Once the leader hears the accepted story, their observation is no longer completely independent.

This does not mean leaders should ignore the team or distrust reports. It means they should establish a sequence:

First, observe the actual condition.

Then, listen to the people closest to the work.

Finally, compare what you observed with what you were told.

The differences between those three perspectives often reveal the most important learning opportunities.

A leader’s first impression is not always correct. But it is valuable precisely because it has not yet been shaped by the organization’s assumptions. It offers a different starting point from the explanations that have already become familiar to the team.

If the leader’s fresh perspective turns out to be incorrect, how clearly is the Genba being visualized? If the leader is confused, many others are likely confused as well.

Go, See, and Think

When you arrive at the Genba, resist the urge to demonstrate leadership by immediately asking questions or offering solutions.

Do not begin with the board.

Do not begin with the report.

Do not begin with someone else’s explanation.

Stand quietly and observe.

Watch how the work actually moves. Notice what changes, what stops, what repeats, and what appears abnormal. Look for small details that others may have learned to accept as normal.

Give yourself enough time to form a fresh impression.

Then you can say, as my coach did:

“I’m ready to discuss.”

The first responsibility of a leader at the Genba is not to speak. It is to see.