The Walk Is Not the System

There’s a story going around about a construction project where a vice president of continuous improvement noticed something simple during a routine site visit.

The workers’ parking lot was a four minute walk from the jobsite. He had it moved closer. Four minutes became one. Which sounds trivial until you do the math. Multiply three saved minutes by a hundred workers over 160 workdays, and the change returned more than a thousand labor hours to the project. No new technology. No consulting engagement. No major investment.

Someone walked the site, paid attention, and noticed something that had probably been sitting in plain view for months. It’s a great example of why leaders need to spend time where work actually happens.

It’s also where many organizations stop thinking.

Whether you call it Management by Walking Around or a gemba walk, the underlying idea is the same: the people closest to the work know things decision makers don’t, and the only way to close that gap is to show up.

The problem is that showing up is only the beginning.

Walking the floor is a way of collecting information, and perhaps building relationships, but what happens to that information afterward is a separate question.

A leader learns that a process change created a workaround everyone now uses. A supervisor explains why targets are being missed. A technician points out a piece of equipment that has been unreliable for weeks.

Useful information. Then what?

Does it become part of how the organization evaluates and prioritizes improvements? Does it get routed to someone who can act on it? Does anyone follow up thirty days later to see whether anything changed or does it sit in a notebook until the next walk, the next priority, or the next quarter?

The parking lot story works because the solution was immediate and within the observer’s authority. Most problems aren’t.

Most require coordination, resources, and decisions that cannot be made on the spot. Finding the problem is only the first step.

Many organizations operate as though once a senior leader knows something, the organization knows it.

Those are not the same thing.

Information held by one person is personal knowledge. Organizational knowledge exists when information has been captured, shared, routed, and incorporated into decisions.

A supervisor tells you a safety procedure works on paper but routinely fails in practice. Now you know, but unless there is a mechanism that carries that information beyond the conversation, the organization hasn’t learned anything.

One person became more informed, the system didn’t.

This is also why people eventually stop raising issues.

If concerns disappear into notebooks, people notice. If the same problems are raised repeatedly and nothing changes, people notice. People are usually willing to share what they know. They’re simply making a judgment about whether sharing it will matter.

Trust is built when people see that the information goes somewhere. That trust builds stronger relationships and engagement.

Many organizations focus on improving the walk itself. Better questions. Better observation forms. Better schedules.

These are all useful, but none address the central issue.

The walk is only the information-gathering part of the process. What matters is everything around it. How is information captured? Who sees it? How is it prioritized? What determines whether it gets acted on? Can employees see what was fixed, what was deferred, and why?

Without answers to those questions, floor walks remain individual learning experiences rather than organizational learning systems.

A floor walk can reveal the truth about how work actually gets done.

Whether that truth becomes action depends on what happens after the walk is over.

The organizations that improve fastest aren’t necessarily the ones that see the most problems. They’re the ones with a reliable way to turn observations into organizational knowledge, and organizational knowledge into action.