Taiichi Ohno built the Toyota Production System — the operating framework that transformed manufacturing and became the foundation for lean thinking, Six Sigma, and virtually every process improvement methodology that followed. He was also, by all accounts, a brutal teacher.
When a promising young engineer joined Toyota, Ohno’s standard welcome was to draw a chalk circle on the factory floor and say: “Stand there and look for waste until I come back.”
Hours later Ohno would return, ask what the engineer had seen, and reply: “You’re a complete blockhead. How did we ever hire you?”
This would repeat — sometimes for days — until the engineer finally saw what Ohno had been looking at all along. Not because the problems were hidden. Because the engineer had been looking at a factory floor through the eyes of someone who expected it to make sense. Ohno’s method was to force the observer to stay in one place long enough that what they had decided was normal became visible as waste.
You are standing in your own chalk circle every shift. The question is whether you are actually seeing what is in it.
The Problem With Normal
The operator who has been in their building every day has made thousands of micro-decisions about what is normal in their operation. How the stage looks at 6pm. How the kitchen sounds during a rush. How the cast moves through their sections. Those decisions are efficient — they allow the operator to process a massive amount of information without consciously evaluating all of it.
They are also the reason the operator has stopped seeing what a first-time Guest sees when they walk in for the first time.
The waste Ohno was training his engineers to see was not dramatic or obvious. It was the pause between one station and the next that everyone had accepted as part of the process. The movement that required three steps when one would do. The redundancy so deeply embedded in the routine that nobody questioned whether it needed to be there at all.
In your restaurant, that waste is the table that sits ungreeted for ninety seconds while the cast member finishes a task they have decided is more urgent. The handoff between the kitchen and the floor that adds two minutes to every ticket because the sequence was never examined. The service sequence that made sense when the concept opened and has never been revisited even though the Guest flow changed three years ago.
None of these feel like problems from inside the operation. All of them are visible the moment someone stands in the chalk circle and actually looks. OnsiteReview™ is built on exactly this premise — one visit, fresh eyes, the diagnostic that the operator cannot run on themselves.
Processes That Average People Can Use To Get Brilliant Results
Fujio Cho, the president of Toyota’s North American subsidiary, once said something that stopped Womack and Jones cold: other companies hired brilliant people to run broken, disconnected processes. Toyota designed processes that average people could use to get brilliant results.
In the end, Cho said, Toyota would win.
This is the most important idea in lean thinking for a restaurant operator — and it has nothing to do with manufacturing.
The operator who builds an operation that only works when they are in the building has not built a system. They have built a dependency. Every shift that requires the operator’s personal presence to hold the standard is a shift that confirms the operation cannot scale, cannot be replicated, and cannot survive the inevitable moment when the operator is not there.
The operator who builds processes clear enough, consistent enough, and well-taught enough that a well-developed cast can execute them without supervision — that operator has built something. The standard holds because it is embedded in the system, not because the operator is watching.
This is the Performance fundamental and the People fundamental working together. Performance is about building systems that produce consistent results. People is about developing the cast who can execute those systems without being managed through every step. Neither one works without the other. Together they produce what Cho was describing — an operation where the process produces the outcome, not the personality of whoever happens to be on shift. Leadership Coaching and MIT Development are built around exactly this transition — from the operation that runs on the operator’s presence to the operation that runs on its own systems.
What Ohno Was Actually Teaching
The chalk circle was not a hazing ritual. It was a training method for teaching observation — the discipline of seeing what is actually there rather than what you expect to be there.
The engineers who survived it did not become better at following procedures. They became better at seeing problems before they became expensive. They developed the pattern recognition that made them able to walk into any part of the operation and read it accurately — not because they were brilliant, but because they had been trained to observe without the filter of assumption.
That is what 44 years on the stage produces. Not a checklist. Not a methodology. A pattern library built from standing in enough chalk circles, in enough operations, long enough to see what normal is hiding.
Stand in your chalk circle. Stay there until what you have decided is normal starts to look like what it actually is.

