TPS is the source of lean manufacturing. Researchers who studied Toyota in the 1980s used the word lean to describe it, and most lean tools, from kanban to andon, come from TPS.
Where it comes from
Toyota describes TPS as developed over many years, with Taiichi Ohno and Eiji Toyoda among the main figures. Its roots include Sakichi Toyoda's automatic loom, which stopped itself when a thread broke, and Kiichiro Toyoda's idea of just in time.
At a glance
The TPS house
Swipe sideways to see the whole diagram.
How to apply Toyota Production System
- 1
Start from customer demand
Set the pace of production by takt time, the rate at which customers buy, rather than by machine capacity.
- 2
Level the schedule
Use heijunka to smooth the volume and mix of production, so the process and suppliers see a steady load.
- 3
Build flow and pull
Link processes with continuous flow where possible and with kanban pull where not, so each step makes only what the next one has used.
- 4
Build in quality
Apply jidoka: machines and people stop when something is wrong, signal with andon and fix the problem before continuing.
- 5
Standardize the work
Write standard work for each task, so problems show up as deviations and improvements have a base to build on.
- 6
Improve continuously
Use kaizen, the five whys and A3 problem solving, led by people at every level, to raise the standard over time.
Worked example (illustrative)
A supplier of seat frames adopts TPS ideas one line at a time. It sets takt time from the customer's daily order, replaces a weekly batch schedule with a kanban loop to the welding cell, and adds an andon cord at each station. Before, about 4 days of welded frames sat between steps. After three months on the first line, that is down to about 1 day. In the first month the andon is pulled about 15 times a week, because problems that used to sit in stock now stop the line. Each one gets fixed, and by the third month pulls are down to about 5 a week.
Common mistakes
- Copying the tools, such as kanban cards or 5S boards, without the problem-solving culture that makes them work.
- Cutting inventory before processes are stable, so the line stops all day instead of exposing one problem at a time.
- Treating TPS as a cost-cutting program rather than a system for developing people and quality.
When Toyota Production System is not the right tool
TPS was built for repetitive, high-volume production with fairly steady demand. In high-mix or one-off work, takt time and supermarkets are hard to set, so teams there often borrow its principles, such as flow, built-in quality and kaizen, and adapt the tools.
TPS and lean manufacturing
John Krafcik, a researcher in MIT's International Motor Vehicle Program, used the word lean for Toyota's system in a 1988 article. The program's book The Machine That Changed the World (1990) brought the term to a wide audience.
Lean manufacturing is the general approach other companies adapted from TPS. Toyota itself still calls its system TPS.
TPS and The Toyota Way
TPS is how Toyota runs its plants and logistics: takt time, flow, pull, jidoka and standard work. Jeffrey Liker's The Toyota Way (2004) describes the management principles behind it, such as long-term thinking, developing people and going to see problems for yourself.
Companies that copy the tools without those principles tend to see the tools fade. The two belong together, and lean is the general name for both as other organizations adapted them.
Muda, mura and muri
TPS targets three kinds of loss. Muda is waste, work that adds no value, such as the eight wastes. Mura is unevenness, swings in volume or mix. Muri is overburden on people or machines.
They are linked. An uneven schedule (mura) pushes people and machines past their limits on busy days (muri), and both create waste (muda). That is why TPS levels the schedule with heijunka before it tries to cut inventory.
The TPS house
The TPS house is a diagram of how the parts support each other. Versions differ in their labels, but the logic is the same:
Roof
The customer gets the best quality, lowest cost and shortest lead time
Pillar: just in time
Make and move what is needed, when it is needed, in the amount needed
Pillar: jidoka
Detect abnormalities and stop defects moving on
Foundation
Standardized work, kaizen, heijunka and stable processes
Base: people
Everyone takes part in sustaining and improving the system
- Roof: Every improvement should link to an outcome the customer needs
- Pillar: just in time: Link production to actual use instead of letting stock build up
- Pillar: jidoka: Set clear signals and a response
- Foundation: Create repeatable conditions people can improve
- Base: people: Involve the people doing the work in problem solving
Use the house as a diagnostic. If a team wants faster delivery, ask whether its quality checks and working methods can support the pace. If problems stay hidden, a new visual board should prompt questions about escalation and response, not just tidy up the walls.
How the two pillars work together
Just in time coordinates flow; jidoka protects that flow from defects. Neither replaces the other: low inventory without jidoka spreads defects faster, and jidoka without flow leaves problems buried in stock.
To turn built-in quality into a process design, ask these questions at each station:
- What counts as abnormal? Define the condition clearly enough that two people would agree.
- How is it detected? By the operator, a sensor or a poka-yoke device.
- Who responds? An andon signal is only useful if someone comes.
- What stops affected work moving on? Containment comes before restart.
- What evidence is needed to restart? The condition is confirmed fixed, not just the alarm cleared.
Just in time also does not mean making every part from scratch after an order arrives. Toyota's own description includes small controlled stocks, replenished by kanban as downstream processes use them.
The practices that keep TPS running
The pillars set the direction. Day-to-day practices keep it going:
Standardized work
The work sequence, timing against takt and needed in-process stock, used as a baseline for improvement rather than a permanent rule. See standard work.
Heijunka
Leveling volume and mix so swings in orders do not ripple through the plant. A small finished-goods buffer can protect a steady schedule. See heijunka.
Kaizen
Daily improvement by the people doing the work, through plan, do, check and act, not only occasional events. See PDCA.
Respect for people
Toyota develops people alongside manufacturing capability. In practice: time to learn, help that arrives when called and changes that address real difficulties.
Repeated why questions help, but the aim is a cause supported by evidence, not reaching a fifth answer.
TPS, lean, just in time and kanban
These terms overlap but have different scopes:
TPS
Toyota's connected system of production, quality, working methods and improvement.
Lean manufacturing
The wider label for applying related principles in other companies. See lean manufacturing.
Just in time
One pillar of TPS, linking production and replenishment to need.
Kanban
A tool that carries production or replenishment signals, not the whole philosophy.
When a project is called lean or TPS-based, ask which operating problem it addresses and how its methods connect. A new kanban loop says little about quality response or people development.
TPS beyond vehicle assembly
Toyota applies TPS in offices too. Each setting needs its own definition of an abnormal condition, a complete input and a good handoff. These are illustrative applications:
Order processing
Check required information at entry so an incomplete order stops before downstream work starts, with a named person to resolve gaps.
Maintenance requests
A clear intake standard separates urgent safety issues from routine work, and missing approvals or parts are visible.
Document preparation
Agree what a complete handoff contains and test whether a shared template ends repeated clarification.
Warehouse replenishment
Defined signals for selected items, with owners, quantities and a plan for when the normal loop fails.
Start from one specific problem, such as one recurring handoff or one shortage, rather than the full vocabulary.
Why TPS implementations struggle
Problems usually come from copying the visible tools without the system around them:
- 1
Cutting inventory without checking reliability. Before removing a buffer, ask how long replenishment takes and which failure the buffer covers. Test the change at a small scale and treat a shortage as evidence, not a reason to push harder.
- 2
Adding signals with no response. At Toyota, an andon pull brings a leader to the station. Name the responder, expected action, containment and follow-up owner before launching any escalation board.
- 3
Counting improvement events. The Lean Enterprise Institute warns against measuring the number of kaizen events instead of results, and against gains that fade afterward. Ask what changed, what evidence supports it and who maintains the new method.
Learning TPS
Toyota stresses on-the-job training and sharing experience between plants. Classroom definitions need to be followed by observation and practice. Good training lets people:
- Observe: Watch a process and separate facts from assumptions.
- Explain the pillars: Say how jidoka and just in time meet different needs.
- See waste and burden: Spot waste without labeling necessary work or ignoring overburden.
- Read the work: Examine a work sequence and the conditions it depends on.
- Test a fix: Define a specific problem and try a small countermeasure.
- Review honestly: Report results and what is still unresolved.
For background, Toyota's official history site includes a timeline of how pull production, flow, small lots, leveling and jidoka developed.
Guides on this topic
- Muri: how to spot and reduce overburden in leanMuri explained: what overburden means, how it differs from muda and mura, the common causes, an observation checklist, six ways to reduce it, examples from factories to software, and how to measure progress without hiding overload.Read the guide
- Lean thinking: the 5 principles and the mindsetLean thinking is a way of creating value with less waste. Learn the five principles, the lean mindset, how it differs from lean tools and how managers apply it.Read the guide
- Lean construction: principles, techniques and how to startLean construction applies lean thinking to building projects. Learn the principles, the eight wastes on site, the Last Planner System and how to start.Read the guide
- Lean healthcare: principles, tools and how to startLean healthcare applies lean methodology to patient care. See the principles, hospital wastes, tools, patient flow and how to start in a clinic or ward.Read the guide
Sources
Books and papers show their publication year. Web pages show the month we last checked them.
- 1.Taiichi Ohno, Toyota Production System: Beyond Large-Scale Production (Productivity Press, 1988)
- 2.Yasuhiro Monden, Toyota Production System: Practical Approach to Production Management (Industrial Engineering and Management Press, 1983)
- 3.Toyota Motor Corporation, Toyota Production System (global.toyota, checked October 2026)
- 4.Steven Spear and H. Kent Bowen, Decoding the DNA of the Toyota Production System (Harvard Business Review, September-October 1999)
- 5.John F. Krafcik, Triumph of the Lean Production System (Sloan Management Review 30(1), Fall 1988)
- 6.James P. Womack, Daniel T. Jones and Daniel Roos, The Machine That Changed the World (Rawson Associates, 1990)
- 7.Jeffrey K. Liker, The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer (McGraw-Hill, 2004)