← Back to Field Notes

January 28, 2025 · The Bloomfield Team

What Toyota Gets Right That Your ERP Does Not

Toyota City, Aichi Prefecture, 1953. Taiichi Ohno stands on the production floor watching an American-style batch production system create exactly the problems he predicted: mountains of work-in-progress inventory between stations, long lead times caused by large batch sizes, and quality defects that traveled through half the factory before anyone noticed them. Over the next two decades, Ohno built the Toyota Production System around a principle that most manufacturing ERP systems still violate in 2025: information should flow with the work, not ahead of it.

The Toyota Production System uses pull-based signals. A downstream station consumes a part and sends a kanban signal upstream to produce the next one. The signal is immediate, visual, and connected to actual demand. No part is produced until the next station needs it. Work-in-progress stays minimal. Problems surface instantly because there is no inventory buffer to hide them.

Your ERP uses push-based logic. An MRP run calculates demand from sales orders and forecasts, explodes bills of material, generates planned production orders, and releases them to the floor as a batch. The floor receives a stack of work orders with due dates. The foreman sequences them based on a combination of the dates, machine availability, and judgment. The schedule is a snapshot that was accurate when it was created and begins decaying the moment the first setup takes longer than planned.

Where Push Logic Breaks

The ERP's scheduling module treats the shop floor as a deterministic system. It assumes that setup times match the routing, that cycle times are consistent, that machines do not break down, that material arrives on time, and that operators are interchangeable. None of these assumptions hold in a high-mix environment. The result is a schedule that looks precise on screen and bears little resemblance to what happens on the floor by midweek.

Toyota understood this problem from the beginning. Ohno described traditional production scheduling as "a schedule that looks good at the desk and fails at the machine." The Toyota Production System eliminated the gap between the plan and reality by making the plan respond to reality in real time through visual signals at the point of production.

Most job shops experience this gap daily. The ERP says Job 4412 should be on Machine 7 right now. Machine 7 is still running Job 4408 because the setup took an extra 45 minutes and the material for 4412 has not arrived from receiving. The scheduler adjusts manually, moving jobs around on the whiteboard that exists alongside the ERP schedule because the whiteboard updates in real time and the ERP does not.

What Toyota Built Instead

The Toyota Production System replaced centralized scheduling with distributed decision-making at the point of work. Three principles drove the design.

Visual management. Every workstation displayed its current status through physical signals visible from across the floor. Andon lights indicated whether the station was running, waiting, or stopped. Kanban cards showed exactly what needed to be produced next and in what quantity. A manager walking the floor could assess the entire operation's state in minutes without opening a single software application.

Pull-based flow. Production was triggered by actual consumption downstream, not by a forecast-driven plan generated days or weeks in advance. This eliminated the fundamental scheduling problem: the gap between what the plan assumed and what actually happened. When reality changed, the pull signals changed with it automatically.

Immediate problem visibility. When a quality issue or a machine problem occurred, the andon cord stopped the line. The problem was addressed immediately rather than being buried in a batch of work-in-progress inventory. Toyota's famous "stop and fix" culture was not a philosophy about quality. It was a systems design choice that made problems visible the moment they occurred, when the cost of fixing them was lowest.

The ERP Was Never Designed for This

ERP systems were designed to manage transactions: purchase orders, work orders, inventory movements, customer invoices. They perform that function well. The scheduling and production management modules that were bolted on over the years operate on the same transactional logic: create a plan, release it, and track progress against it. The plan is a document. The floor is a dynamic system. The two are fundamentally different, and the ERP bridges them poorly.

This is why the foreman's whiteboard exists. The whiteboard is a primitive pull-based system. It reflects current reality. It updates instantly when priorities change. It is visible to everyone on the floor. It does everything the ERP's scheduling module fails to do, at the cost of having no memory, no analytics, and no connection to the rest of the operation's data.

The answer is not to replace the ERP. The answer is to build a visibility layer that does what the whiteboard does with the data depth that the ERP provides. Real-time machine state. Actual job progress versus plan. Queue visibility for each work center. Automatic re-sequencing based on current floor conditions rather than last Tuesday's MRP run.

Closing the Gap

Toyota's production system worked because information flowed with the work. The kanban card traveled with the part. The andon signal was generated at the machine. The scheduling intelligence was distributed across the floor, not concentrated in a planning office running batch calculations on day-old data.

Building that same information flow in a modern job shop means connecting the ERP's data, which is comprehensive but static, to a real-time layer that reflects what is actually happening on the floor right now. When Machine 7 finishes Job 4408, the system should immediately identify the next highest-priority job that has material staged and tooling ready, without waiting for a human to check the schedule, walk to the whiteboard, and make a decision. The integration between your ERP and your floor is where Toyota's principles meet modern manufacturing reality.

Your ERP is a planning tool. Your floor needs a flow tool. The shops that build the bridge between the two will run their operations with the same efficiency that made Toyota the benchmark for an entire industry.