Episode Details

Back to Episodes
Ohno and Malone Were Asking the Same Question

Ohno and Malone Were Asking the Same Question

Published 4 months, 3 weeks ago
Description

A maintenance supervisor retired four years ago. Thirty years at a plant in Alabama. He had started as an operator on the molding line, worked his way up, and over three decades had installed every piece of major equipment in the building. He knew the sound a gearbox made forty-eight hours before it seized. He knew which electrical panels had been wired by which contractor and where each one had buried its shortcuts. Thirty years of institutional knowledge in his hands, none of it in a manual.

When he retired, the HR file recorded a benefits payout, a final paycheck, and a thank-you card signed by the shift. The general ledger recorded nothing else. No write-down. No impairment. No depreciation schedule closing out. As far as the accounting system was concerned, nothing of value had left the building.

Two quarters later, the machines began to crash in ways no one on the floor could explain. Throughput dropped. The new maintenance lead blamed the supplier, the heat, the schedule. He did not blame the ledger, because the ledger never told him there was anything to blame. The asset that walked out the door was never on the books in the first place. An asset stranded at birth — recorded nowhere, consumed continuously, replaced almost never.

Two disciplines have brushed against this and walked away. Oana Labes posted a sharp note this week listing seven limitations of EBITDA. Her list is correct as far as it goes, and it stops where the financial accounting tradition has always stopped: just shy of naming the asset that EBITDA was designed to hide. The operational accounting tradition stopped at the same place, fifty years earlier, in a different language. Lean called it the eighth waste, named it as a placeholder, and never built the system to address it.

That’s the argument. Finance has seven EBITDA limitations and a missing eighth. Lean has seven wastes and a bolted-on eighth that no one operationalized. The convergence is not coincidence. It is the same asset — the formed capability of the frontline worker — going unrecognized in two different accounting languages. You can only manage what you measure. Both traditions abandoned the metric for the asset that mattered most. Until that asset is on the books, neither discipline can finish what it started.

What Ohno Built, and What the West Could Not Carry

Taiichi Ohno codified seven wastes in the Toyota Production System: transportation, inventory, motion, waiting, overproduction, overprocessing, defects. TIMWOOD. Each waste came paired with a method to eliminate it — kanban for overproduction, jidoka for defects, one-piece flow for waiting. They named what happened to the work, not what happened to the worker’s capability — because at Toyota, capability was not a separate category. The plant was, in Ohno’s framing, a Thinking People System. Workers stopped the line. Workers proposed kaizen. Respect for the human was not a waste category. It was the substrate the whole system rested on.

Then TPS crossed the Pacific. American practitioners in the 1990s — Jeffrey Liker, Norman Bodek, the academic translators of The Toyota Way — added an eighth: non-utilized talent. Unused human potential. The waste of skills. It went on the posters. It went into DOWNTIME, the American acronym that displaced TIMWOOD.

The eighth was added because something visible at Toyota was not transferring. The Western adopters could see the seven process wastes did not account for the human substrate. So they named it. But they could not carry what they were naming. Ohno did not need an eighth waste — the seven, applied through autonomation and continuous improvement, were already the operational expression of respect for the worker. Strip the substrate out, paste the wastes onto an American assembly line that still treats labor as a substitutable input, and the seven can be eliminated while the eighth grows. The poster goes up. The capabi

Listen Now

Love PodBriefly?

If you like Podbriefly.com, please consider donating to support the ongoing development.

Support Us