Definition
Just-in-Time is one of the two pillars of the Toyota Production System, alongside jidoka. It is the principle of making only what is needed, when it is needed, in the amount needed. In Japanese, Toyota often explains it as: 「必要なものを、必要なときに、必要なだけ」— “what is needed, when it is needed, only in the amount needed.”
JIT is not simply delivering parts on time. It is an integrated production philosophy that synchronizes every process in the value stream to the rate of actual customer demand, using takt time, continuous flow, pull systems, and leveled production to eliminate the waste of overproduction.
Japanese Origin
Just-in-Time is a borrowed English phrase written in katakana (ジャストインタイム). Toyota uses the English-derived term, not a native Japanese word. This is notable — the label has Western linguistic roots even though the system was developed entirely in Japan.
Kiichiro Toyoda used the phrase in his original writings when establishing Toyota Motor Corporation. The fact that he chose an English term may reflect the strong influence of American manufacturing (Ford, Taylor) on early Japanese industrialization.
History at Toyota
Kiichiro Toyoda’s founding vision, 1937 — When Toyota Motor Corporation was formally established in 1937, Kiichiro Toyoda envisioned a production system where parts would flow without large stockpiles. Toyota’s 75-year history records that Kiichiro laid out factory design and process flow in a document later called “The Roots of TPS” by Eiji Toyoda, and decreed that internal production should be done “Just-in-Time” to avoid waste.
The Koromo Plant, 1938 — When Toyota’s new Koromo plant (now Honsha Plant) opened, Kiichiro pushed to implement his JIT ideas. However, wartime disruptions and the chaos of the immediate postwar period prevented full realization.
Taiichi Ohno’s development, 1950s-1970s — After the war and Toyota’s severe financial crisis in 1950, Taiichi Ohno took Kiichiro’s JIT concept and built the operational system to make it real. This is where kanban, leveled production, quick changeovers, and continuous flow were developed as the practical mechanisms of JIT. Ohno worked for roughly two decades, starting in his own machine shop and gradually expanding across all of Toyota’s operations.
The two pillars formalized — Toyota formally describes TPS as standing on two pillars: Just-in-Time (flow) and Jidoka (quality). This framing became standard Toyota language, appearing in official publications and the Toyota Way 2001 document. Both pillars are necessary — flowing defective parts quickly is worse than not flowing at all.
How It Actually Works
JIT is an integrated system with several essential sub-elements that must work together:
Takt time — The rate of customer demand. If customers buy 480 cars per day and the plant operates 480 minutes, takt time is 1 minute per vehicle. Every process in the plant is synchronized to takt time. This is the heartbeat of JIT.
Continuous flow (一個流し / ikko nagashi, one-piece flow) — Where possible, parts move one at a time through sequential processes without waiting in queues. This is the ideal state. Where true one-piece flow is not possible (between processes with different cycle times or between buildings), controlled buffers with kanban are used.
Pull system — Downstream processes pull parts from upstream only when needed. This is the opposite of push (MRP-driven, forecast-based batch production). Kanban is the signal that implements pull.
Heijunka (平準化, production leveling) — Perhaps the most underappreciated element. Toyota does NOT build to the raw sequence of customer orders. Instead, they level the production schedule, mixing different models and variants throughout the day in a repeating pattern. Instead of building all white Camrys in the morning and all red ones in the afternoon, they interleave them. This leveling smooths demand on every upstream process and supplier. Without heijunka, pull systems oscillate wildly.
Small lot sizes and quick changeover — To enable mixed-model production and flow, Toyota drove changeover times down dramatically. Stamping presses that took hours to change in Western plants were changed in minutes at Toyota.
Implementation Guidance
JIT cannot be implemented piecemeal. The sub-elements form an integrated system — remove any one and the system degrades.
The implementation sequence matters:
- Stabilize first — reliable equipment, consistent quality, standardized work
- Level production (heijunka) — this creates the stable demand pattern everything else requires
- Establish flow where possible — connect sequential processes, reduce batch sizes
- Implement pull (kanban) between processes where flow is not yet possible
- Synchronize to takt time — balance work content across stations
- Continuously reduce buffers to expose and solve the next problem
Do not skip heijunka. Most Western JIT failures can be traced to attempting pull and flow without leveled production. The result is amplified demand variation that makes the system less stable, not more.
Start in a contained area. Pick one product family and one value stream. Get it working end-to-end before expanding.
Common Mistakes
Thinking JIT means zero inventory. JIT means minimum necessary inventory. Toyota maintains strategic buffers — supermarkets between processes, safety stock for shipping variation. The goal is to continuously reduce inventory (which exposes problems), but zero is an asymptotic ideal, not an operational reality.
Shifting inventory to suppliers. Simply making suppliers deliver more frequently without helping them implement their own flow and pull is not JIT — it is cost-shifting. Toyota invests heavily in supplier development precisely because JIT requires the entire value stream to be capable.
Confusing JIT with “deliver on time.” On-time delivery is a consequence of JIT, not its definition. JIT is a production system design philosophy centered on eliminating overproduction — the waste Ohno called the worst of all wastes because it causes every other waste.
Implementing kanban without the prerequisites. Kanban is the tool that implements pull, but it requires heijunka, stable processes, and standardized work to function. Kanban without these prerequisites produces chaos.
Blaming JIT for supply chain fragility. Toyota actually weathered supply disruptions (including the 2021 semiconductor shortage) better than most competitors because JIT provides better supply chain visibility and faster response capability. Companies that suffered most often had the least supply chain discipline, not the most.