Resources/Glossary/
Toyota Production System
TPS Foundations

Toyota Production System

The operating system Toyota built to make only what was ordered.

Updated
·
4
min read
Definition

What is Toyota Production System?

The Toyota Production System is the integrated manufacturing approach Toyota developed in the decades after World War II to produce exactly the right parts at the right time at the lowest cost. Its two pillars are just-in-time, producing only what is needed when it is needed, and jidoka, stopping production at the moment a problem appears. Lean manufacturing is the Western generalization of TPS.

The Toyota Production System is the most studied, most copied, and most poorly imitated manufacturing approach in industrial history. Built inside Toyota by Taiichi Ohno and others in the 1950s and 1960s, TPS turned a small post-war Japanese carmaker into the world's largest auto manufacturer. The system is not a technology or a software platform. It is a way of running a shop floor that treats every minute of every shift as an opportunity to remove waste from the work.

"The pillars are simple. The discipline to actually stop the line when something is wrong is not."

How the Toyota Production System works

TPS rests on two pillars. The first is just-in-time, the practice of producing only what is needed, when it is needed, in the amount needed. JIT replaces forecast-driven production with actual customer demand, signalled through kanban cards or other pull triggers. The second pillar is jidoka, the practice of stopping production at the moment a defect or abnormality appears. Jidoka gives any worker the authority to pull the andon cord and halt the line so the problem can be fixed at its source.

The pillars sit on a foundation of standard work (the current best-known way to do each task), heijunka (leveling production so demand swings do not whiplash the shop), and continuous improvement (the daily habit of finding and removing small wastes). The center of the diagram, in every textbook drawing of the TPS house, is the customer: the shortest possible lead time, the lowest cost, the highest quality.

What makes TPS work is not the diagram. It is the daily discipline of using it. Every worker is trained to see the gap between standard work and what is actually happening, and to flag it the moment it appears. Every supervisor is expected to come to the shop floor, see the problem, and help solve it. Every manager is judged not by whether the line ran today but by how many problems the team surfaced and fixed.

Where TPS fits on the shop floor of a small manufacturer

Imagine a 30-person fabrication shop running steel parts for two HVAC OEMs. Production is fairly steady but lead time from order to ship is around three weeks, and the shop carries about $300,000 in WIP between operations. The owner has heard about TPS and assumes it requires a six-figure consulting engagement.

A small-shop TPS rollout would start with three things, in order. First, install two-bin kanban signals between the two operations that produce the most WIP. The bins are physical, the rule is simple: when bin one is empty, the supplier process makes another. Second, set up a 10-minute morning standup at a whiteboard where the shift discusses what went wrong yesterday and what they will do about it. Third, give every operator authority to stop their machine and ask for help the moment they see a defect, without management approval.

That is TPS at small scale. Three changes, none of which cost more than a few hundred dollars in materials, all of which the team can run themselves. Within three months the shop will see lead times come down and WIP shrink. The harder work, building the kaizen habit so improvements keep coming after the initial wave, takes years.

Common mistakes when adopting TPS

  • Copying the tools, skipping the authority. Andon cords are physical; the authority to pull them is cultural. Without the authority, the cord is decoration.
  • Treating it as a software rollout. TPS lives on the shop floor, not in an ERP. Adding a dashboard does not add TPS.
  • Implementing in one wave. TPS is built incrementally over years. Trying to install it in 90 days produces a shop that looks lean briefly and then reverts.
  • Skipping daily problem-solving. Without the morning standup, the kaizen habit never forms. The tools then have nothing keeping them in tune.
  • Ignoring respect for people. TPS engages workers as problem-solvers. A shop that uses TPS to monitor and squeeze workers will be sabotaged within a year.

The Toyota Production System and related Lean tools

TPS is the source. Lean manufacturing is its Western generalization. The two pillars of TPS, just-in-time and jidoka, are the most distinctive Toyota contributions. The supporting philosophy is captured in the Toyota Way, Jeffrey Liker's framing of Toyota's 14 management principles. The daily engine that keeps it all running is kaizen, the continuous improvement habit that turns one-time wins into a permanent operating rhythm.

Common questions

The questions we hear most about this term.

How is Toyota Production System different from Lean Manufacturing?
TPS is Toyota's specific operating system, developed inside Toyota over decades. Lean manufacturing is the generalized version, distilled by Western researchers in the 1990s so non-Toyota organizations could apply the ideas. If you read about lean in a book, you are reading about a translation of TPS. If you walk a Toyota plant, you are seeing TPS. Most of the principles are the same; the difference is whether you are studying it from inside the company that invented it or from outside.
How is TPS different from the Toyota Way?
TPS is what Toyota does on the shop floor: the pull signals, the andon cords, the standard work, the takt time. The Toyota Way is the management philosophy that explains why Toyota does it that way: 14 principles organized into four pillars, framed by Jeffrey Liker in 2003. You can implement TPS tools without the Toyota Way and end up with a shop floor that looks lean for six months before it decays. The Toyota Way is the supporting culture.
Why do so many companies fail when copying TPS?
Because they copy the tools without the discipline. The visible parts of TPS, kanban cards in racks, andon lights, color-coded floor markings, are easy to install and look impressive in a tour. The invisible parts, the authority any worker has to stop the line, the daily problem-solving meetings, the long-term investment in developing people, take years to build. A shop that copies the cards but not the authority ends up with decorated workplaces that do not actually run on pull.
What are common mistakes when implementing TPS?
The biggest one is starting with the tools instead of the problems. A shop that buys kanban racks without first understanding where parts are sitting will end up with kanban racks full of the wrong parts. The second is treating TPS as a project with a finish line. TPS is a habit that runs every shift. The third is skipping respect for people, which means engaging workers as problem-solvers, not just operators. Without it, the tools decay within a year.
What does TPS look like on the shop floor of a small manufacturer?
Smaller and quieter than people expect. A 30-person machine shop running TPS might have a few bins between operations, each with two cards. When the second card frees up, that is the signal to make more. There is a daily 10-minute standup at a whiteboard with three columns: what we made yesterday, what we will make today, what is in our way. There is no software dashboard. The information is on the floor where the work is.

Ditch the whiteboards and spreadsheets.

Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.