Operations

Lean Thinking and the Eight Wastes – An Operator’s Field Read

Lee Sammartino 5 min read

Case Study: What Toyota knew, and what your P&L is paying for.

Lean is the discipline of refusing to pay for activity that the customer would not pay for. The instinct sits in finance, and the lineage runs through a Toyota machine shop in 1948.

Taiichi Ohno joined Toyota in 1932 and moved into the engine plant in 1943. Working under the constraints of a post-war Japanese economy that had no capital cushion to carry inventory and no domestic market large enough to justify Detroit-style mass production, Ohno reverse-engineered an operating system designed around customer pull rather than factory push (Ohno 4-7). He named the eight forms of waste he found in any process. He used the word muda.

The seven wastes, then eight

Ohno’s original list ran seven items long. Later practitioners added an eighth, the underused skill and intelligence of the workforce, after observing that the most expensive waste in any system is a capable person spending their day on activity the customer does not value (ISM 1).

The Toyota Production System inverted the assumptions of mid-century mass production. Smaller batches, faster changeover, defects surfaced at the source, inventory treated as a liability rather than a buffer, capacity managed against takt time rather than utilization (Liker 23).

What Womack and Jones translated

James Womack and Daniel Jones spent five years inside the auto industry on the IMVP study and put the framework into English in The Machine That Changed the World in 1990 and Lean Thinking in 1996. They distilled the operating philosophy into five principles that every lean engagement still runs against (Womack and Jones 16-26).

Ries took it to the venture portfolio

Eric Ries published The Lean Startup in 2011. He carried two of the Toyota ideas into product development. Build a minimum viable version of the thing. Run a Build-Measure-Learn cycle against falsifiable hypotheses. Pivot when the data says the thesis is wrong (Ries 75-103). The translation worked because the underlying problem is the same. A startup with too much capital and a manufacturing line with too much inventory both pay the same kind of tax. They produce something the customer has not asked for.

The principle scales up and down. A 5,000-person enterprise that runs an annual planning cycle on activity-based budgeting is paying the same tax. The work is to move budget toward activity the customer values and to find and remove the rest.

Womack & Jones · 1996

The five principles, in order.

  1. Specify valueDefine value from the customer’s view, not the operation’s.
  2. Map the value streamIdentify every step from input to delivery and label each as value-adding, necessary non-value-adding, or pure waste.
  3. Create flowMake the value-adding steps move continuously, without queues, batches, or interruptions.
  4. Establish pullProduce only what the next step or the customer is asking for, when they are asking for it.
  5. Pursue perfectionRepeat the cycle. The waste removed reveals the next layer of waste underneath.

Source · Womack and Jones, Lean Thinking, 1996, pp. 16-26.

Figure 02 · The Eight Wastes
Score the operation against Ohno’s eight wastes. Most companies have one or two that drown out the other six.
HORIZONTAL BAR · ILLUSTRATIVE
Source · Adapted from Ohno (1988), Liker (2004), and the Womack and Jones lean canon. Estimated impact distribution from a working diagnostic.
95%
Cycle time as waste

Estimated share of total cycle time in a typical process spent on non-value-added activity at the start of a lean engagement (Womack and Jones).

8
Forms of muda

Ohno’s seven wastes plus the eighth added later: the underused skill of the workforce.

1948
First TPS practice

Year Toyota piloted the practices that became the Toyota Production System under Taiichi Ohno’s direction.

The eight wastes, with examples a CFO can find on a P&L.

WasteWhat it looks like in operationsWhere it shows on the P&L
DefectsRework, scrap, customer escalations, support tickets that loop back.COGS variance, support cost per ticket, contract penalties.
OverproductionBuilding features and inventory ahead of demand signal.Inventory carrying cost, write-downs, sunk product spend.
WaitingQueues between handoffs, approvals, system locks, pipeline stalls.Working capital tied up, missed quarter-end recognition.
Non-utilized talentSenior people on low-impact activity, capability mapped to the wrong work.Comp expense to output ratio, recruiting churn cost.
TransportationDocuments, parts, or data moving for no customer reason.Logistics line, integration cost, IT bus charges.
InventoryWIP, finished goods, marketing stock, unused licenses.Working capital, depreciation, license waste.
MotionPeople stepping through unnecessary tools, screens, meetings.Productivity gap, T&E, software cost.
Extra processingSteps that exist because the workflow once required them.SG&A creep, vendor cost, finance close cycle time.
The Call
Share
LinkedIn WhatsApp

If this
lines up,
let's connect.

Start the conversation. Tell me where you are and what's at stake. We'll take it from there.

Direct Contact
⌄

No sales process. Direct conversation.