A lunch, a hand gesture, and the question most Lean implementations are answering backwards.
The gesture is the whole thing.
The late Hajime Ohba held his hands out in front of him, palms down, one higher than the other. “All the other consultants and managers implement solutions down on the people doing the work. What they don't understand is the work always changes in unpredictable, even unknowable ways underneath them.”
Then he repositioned. Palms up. Fingers spread. Supporting from below.
“Toyota is different. First, we develop the people. And everything flows from that.”
That story comes from Dr. John Kenagy, who was sitting across the lunch table when Ohba said it. Kenagy was at Harvard Business School at the time, doing research on how high-velocity organizations actually work. Ohba was head of the Toyota Production System Support Center — a legendary figure in TPS's North American history. The lunch was mostly Ohba asking Kenagy questions about his work, the way Toyota people do when they want to find out what you actually know.
Then, midway through, came the question that's stayed with Kenagy ever since:
“Would you like to know the secret of the Toyota Production System?”
Kenagy gulped. He started looking around for a pen and paper.
He didn't need one.
The Two Hands
Most of what gets called Lean implementation is the first gesture wearing the vocabulary of the second.
Leaders say they're developing their people. Their behavior, observed honestly, is closer to “we push solutions down on them and then ask why they're not engaged.” Ohba wasn't sharing a methodology that day. He was correcting a misunderstanding about which direction support flows.
What Kenagy Had Been Studying
Kenagy didn't arrive at HBS as a Lean person. He's a vascular surgeon who broke his neck falling out of a tree in 1982 and spent six months as a totally disabled patient, watching the healthcare system from within. What stuck with him was that most of the good care he received came from individuals going around the system, not from the system itself. He kept asking what it would take for the system to make it easier for people to do what patients needed.
That question led him eventually to Harvard, where he studied with Steve Spear, Kent Bowen, and the late Clayton Christensen. Spear and Bowen's 1999 HBR paper, “Decoding the DNA of the Toyota Production System,” is the article Kenagy still points to first. It lays out the four “rules in use” — how Toyota actually designs work activities, connections, pathways, and improvement. If you haven't read it, get it. It's free, and short enough to read tonight.
What the rules describe, when you read them carefully, is the palms-up gesture. Toyota designs the system so that problems become visible immediately, at the point and time of the work, by the person doing it. The system is built to support that person, not to be defended from them.
People feel psychologically safe enough, in other words, to speak up and point out problems.
The Nurse and the 103 Steps
Kenagy's “Adaptive Design” work in healthcare took the Ohba lesson and made it operational. The way you start, in his approach, is by going to the front line and asking a nurse if you can simply watch her for an hour.
He shared the data from one of those hours during a KaiNexus webinar I hosted with him. In one hour, the nurse — her name was Jess — was responsible for the medication needs and other care of five patients. To do that, she worked in three or four locations and changed location 103 times. She talked with seventeen different people about more than one hundred subjects. She spent 23 minutes of that hour on direct patient care and 21% on administrative work. The rest, in Kenagy's framing, was a workaround or a small system failure.
She wasn't underperforming. She was extraordinary. She had to be, to do that hour at all.
The point isn't to fix the nurse. The point is to redesign the system around her so the next hour requires fewer workarounds. That's the difference between pressing down and supporting up, made concrete enough to count.
It's also where Goodhart's Law shows up. When a metric becomes a target, it stops being a useful metric. Kenagy's data from the operating room of a large northeastern teaching hospital showed surgical volume increased 14 percent and staff overtime decreased 12 percent over six months — not because anyone was targeting volume or overtime, but because they were running 59 small “A3” experiments centered on patients. The numbers moved because the system moved. The system moved because the people running it had been developed enough to move it.
The Same Conversation, Twenty Years Later
Kenagy said something in the webinar that I keep returning to. He shows audiences the difference between his two kinds of “kata” — pressing-down kata and developing-people kata. Almost everyone in the audience picks the second one. Then they walk out the door and run the first one.
Paul Batalden's line covers this: every system is perfectly designed to get the results it gets. If your improvement system keeps producing the palms-down gesture even while your slides say palms-up, that's worth noticing. Not as a moral failing. As information about how the system you've built is actually structured.
There's a corollary Kenagy uses that's stuck with me: We don't think our way to a new way of acting. We act our way to a new way of thinking.
Reading about palms-up doesn't change your hands. The work changes your hands. And the work is harder than reading.
A Smaller Question
Ohba didn't give Kenagy a methodology that day. He gave him a gesture and let him figure out the rest. The gesture is doing two things at once. It's describing what Toyota does. It's also demonstrating what Toyota expects from a coach — that you'd rather show something simple than explain something complicated.
If you wanted to test where your own organization sits, you wouldn't need a survey. You'd watch what people do with their hands in the next problem-solving meeting.
Which way are they pressing?
