Just-in-Time

Just-in-time is the lean principle that says you should make exactly what is needed, exactly when it is needed, in exactly the amount needed. It is the operational heart of Toyota's pull-based production system and the practice most people associate with the word "lean." JIT is also the practice most likely to be implemented badly, because it surfaces every form of upstream unreliability the moment buffers shrink.

"When you make to forecast, you make extra. When you make to signal, you make right."

How just-in-time works

The mechanics of JIT are simpler than they look. Each station in the shop holds a small buffer of parts ready to go. When the downstream station consumes one of those parts, it sends a signal upstream, usually a kanban card, that says "make one more like this." The upstream station only produces in response to that signal. Multiply this across every station, from raw material in the back of the shop to finished goods at the loading dock, and you get a system where the entire shop only produces what the customer actually pulls.

The signal can be physical or digital. The original Toyota system used cards in metal holders that travelled with bins of parts. Modern shops sometimes use electronic kanban systems that trigger reorders based on barcode scans or RFID. The technology does not matter. The discipline does. JIT works because every station respects the signal, neither making more nor making less than the signal asks for. Stations that overproduce because "they had time" or underproduce because "they thought they could catch up later" destroy the rhythm.

What JIT requires under the hood is stability. The upstream process has to be reliable enough that the small buffer downstream is enough. That means short setup times (SMED for changeovers), high quality (jidoka for stopping defects before they propagate), and standardized work (standard work so each operator does the task the same reliable way). Without these, JIT does not work; the buffers are too small to absorb the variation.

Where JIT fits on a small shop floor

Imagine a 25-person electronics assembly shop building three control boards on a steady weekly cycle. The shop currently runs an MRP system that schedules production five weeks out based on the order book. Each station produces to schedule, which means at any given time there are 8 to 12 boards stacked between solder paste and reflow, another 15 between reflow and test, and 20 in a finished-goods area waiting for shipment paperwork. Lead time from order to ship is around four weeks.

A JIT pilot would not replace the MRP entirely. The MRP would still set the weekly volume plan. But within each week, the shop would put a two-bin kanban between each of the four assembly stations. Each bin holds enough boards for about half a day of downstream work. When the downstream station empties a bin, the empty bin goes back upstream as the "make more" signal. Within a month, WIP between stations drops by half. Within a quarter, lead time drops from four weeks to ten days, because the work is no longer queueing in piles.

The hard part is the day the upstream supplier has a quality issue and the small buffer runs dry. Without JIT, the issue would have been hidden by the four-week inventory cushion. With JIT, it stops the line in the afternoon. That is JIT working as designed: the problem is surfaced immediately, and the team can fix the supplier issue while the shop is still small enough to do so. Without the signal, the shop would have shipped 200 defective boards before anyone noticed.

Common mistakes with just-in-time

• Interpreting JIT as zero inventory. Right-inventory is the goal: small enough to surface problems quickly, large enough to absorb normal variation. Zero is brittle.
• Implementing JIT before upstream is stable. If suppliers are unreliable or setup times are long, JIT will create constant stockouts. Stabilize upstream first, then shrink buffers.
• Mixing JIT with hot-order expediting. A shop that says "we run JIT, except when the order is hot" does not run JIT. The whole point is the signal is the only trigger.
• Skipping standard work. Without standardized tasks, station output varies too much for small buffers to absorb. JIT depends on predictable output at every station.
• Outsourcing the discipline to software. Electronic kanban can replace cards but cannot replace the operator habit of respecting the signal. The discipline is human.

Just-in-Time and related Lean tools

JIT is one of the two pillars of the Toyota Production System, paired with jidoka (stop the line when something goes wrong). It is the operational heart of lean manufacturing. The most common signalling mechanism for JIT is kanban, Toyota's pull-trigger system, which in turn requires supermarket stocking between operations to work reliably.