Toyota Production System (TPS): The Two Pillars & Why It Works

What is the Toyota Production System (TPS)?

The Toyota Production System is the production philosophy Toyota developed between the 1940s and the 1970s, codified mainly by Taiichi Ohno and Eiji Toyoda. Its purpose is simple to state and hard to execute: produce exactly what the customer wants, in exactly the required quantity, at exactly the right time, with the absolute minimum of waste. Everything else in TPS — Just-in-Time, Jidoka, Kanban, Heijunka, Kaizen — is a method in service of that goal.

TPS is the origin of what the Western world later renamed Lean Production. The two are often used as synonyms, but they are not identical. Lean is the distilled, exported version; TPS is the original, culturally anchored system as it runs inside Toyota. Understanding the difference matters because most failed "Lean transformations" outside Toyota fail for the same reason: they copy the tools and miss the system.

In manufacturing reality, TPS is usually visualised as a house with two load-bearing pillars — Just-in-Time and Jidoka — built on a foundation of Heijunka (levelled production), Standardised Work and continuous Kaizen. The roof is the goal: highest quality, lowest cost, shortest lead time, best safety and highest morale. Remove one element and the house collapses.

The two pillars of TPS

Most of the public confusion about TPS comes from reducing it to a single slogan — usually "Just-in-Time". In reality, JIT only works because Jidoka stops it when something goes wrong. Both pillars are load-bearing; neither is optional.

Jidoka is often mistranslated as "automation". It is not. Toyota's founder Sakichi Toyoda built the principle into his automatic looms in 1924: when a thread broke, the loom stopped itself. One operator could supervise many machines because the machines knew when to stop. Defects were never produced, never passed downstream, and always visible. That is Jidoka — "automation with a human mind", sometimes called autonomation.

The 7 wastes (Muda) — and the ones Ohno added later

Taiichi Ohno's single most exported idea is the list of seven wastes. They define what TPS is trying to eliminate. An eighth waste — "unused employee creativity" — was added later in the Lean adaptation but was already implicit in Toyota's Kaizen culture.

TPS targets three Japanese concepts together: Muda (waste, the seven above), Mura (unevenness, volatility in volume or mix) and Muri (overburden of people and equipment). Western Lean programmes tend to focus on Muda and miss the other two, which is why they stabilise then stall.

The TPS house: what sits under the pillars

The two pillars only work because of what is below them. Most Lean implementations fail because they install Kanban and Andon on an unstable foundation — and the system collapses within 18 months.

The "Respect for People" element is often reduced to HR platitudes in Western adaptations. At Toyota, it is operational: any operator can stop the line, problems are never blamed on individuals, and every suggestion gets a response. Strip that out and Kaizen dies inside 12 months.

TPS vs. Lean: the honest comparison

Everything you do as Lean is a subset of TPS. The reverse is not true.

What TPS means for a modern MES

TPS was designed before ERPs, MES and cloud platforms existed. The Kanban card was literally a piece of paper. Yet every serious MES implementation today is either supporting TPS principles or undermining them. The connection is direct, not metaphorical.

The risk runs the other way too. An MES that just backflushes ERP orders in big batches is actively hostile to TPS — it encourages overproduction, hides micro-stops and makes real pull impossible. The architecture decision matters.

FAQ

Is TPS only for automotive?
No, but automotive is where it hardens. Toyota, Honda, Porsche, BMW and most tier-1 suppliers run TPS-derived systems because automotive combines high volume, high variant complexity and unforgiving quality standards. The principles transfer well to food, pharma packaging, consumer goods and metal forming. They transfer poorly to pure project business, construction sites and R&D — because those lack the repeating flow that TPS is built around.

Is TPS the same as Lean Manufacturing?
Not quite. Lean is the Western distillation of TPS, published in "The Machine That Changed the World" in 1990. Lean adopted the tools (Kanban, Andon, SMED, 5S, Kaizen events) and the vocabulary (value, value stream, flow, pull, perfection). What it mostly failed to import is the cultural foundation: decades-long commitment, "Respect for People" as an operational principle and the insistence that every process improvement has an equal people element. TPS without the culture is a toolbox. Lean with the culture is TPS.

Can a mid-sized manufacturer really apply TPS?
Yes, and some of the cleanest implementations in Europe are not at big OEMs but at SMEs with 200–800 employees. The constraints are different: shorter runs, more variants, smaller change budgets. But the basics — levelled production where possible, visible WIP limits, standardised work, Andon on critical stations, daily Kaizen — work at any scale. The honest warning: TPS is a commitment, not a project. If the leadership team won't still be on the shopfloor in year five, do something simpler.

What is the single biggest reason TPS roll-outs fail outside Toyota?
Pressure to hit the monthly number overrides the line-stop principle. The moment a plant manager tells an operator "don't stop the line, we can't afford it this quarter", Jidoka dies. Once Jidoka is dead, defects pass downstream, inventory rises to hide the problem, pull loops collapse into push, and within 18 months the plant is back to where it started — with expensive Andon lights decorating the walls. The second-biggest reason is turnover at leadership level: new COO arrives, declares "our own system", and restarts the clock.

How does TPS relate to Industry 4.0 and cloud MES?
They are complementary, despite being from different eras. TPS defines what you should optimise for — flow, pull, built-in quality, waste elimination. Industry 4.0 and cloud MES define what you can now measure and automate in support of those goals: every cycle time, every micro-stop, every deviation, across every plant. The danger is the same as with classical Lean tools: companies install the technology without the principles, get a data dashboard, and call it transformation. A real TPS-plus-MES setup uses the data to expose problems faster, not to paper over them.

Related: Lean Production · Just-in-Time · Kanban · Pull Control · Kaizen · Takt Time · SMED · TPM

About the author

Christian Fieg

Head of Sales at SYMESTIC. Six Sigma Black Belt with 25+ years in automotive. Built and ran TPS-derived JIT/JIS lines for Johnson Controls across plants in China, Mexico, the US, France, Tunisia and Russia. Author of "OEE: One Number, Many Lies". · LinkedIn