It started with a problem.
Toyota engineers in postwar Japan faced resource constraints that made large inventories impossible to maintain. Taiichi Ohno, an engineer who became a key figure in Toyota's production system, developed a method that organized manufacturing around demand rather than capacity. The principle was to make only what was needed, when it was needed, in the amount needed. This required each production stage to signal the previous stage when it used materials — a system called kanban, using physical cards or signals. Toyota's own description of the Toyota Production System identifies just-in-time as one of its two foundational pillars, developed with strong backing from Eiji Toyoda.
Historical sources below ↓Then something changed.
Just-in-time changed what counted as waste in a factory. Under earlier mass-production models, large buffers of parts between stages were considered prudent. Under just-in-time, a buffer indicated a problem: a stage was producing faster than the next could use, or quality was inconsistent enough that spares were needed as insurance. Surfacing those problems — rather than covering them with inventory — was the point. The system made every inefficiency visible. This required reliable suppliers and consistent quality; just-in-time is fragile in ways that buffer-based production is not.
What a builder can learn.
Our interpretation: just-in-time is often described as an efficiency technique, but it is also a diagnostic tool. Carrying inventory hides process problems; removing inventory exposes them. This principle applies beyond factories. A service business that maintains large backlogs of unanswered requests is cushioning itself from a capacity or quality problem it has not yet addressed. Reducing the backlog — or at least measuring where it grows — reveals which steps cannot keep pace.
A door still open.
A hypothesis worth testing: if a small service business reduced its work-in-progress limit for one category of task — say, limiting how many open repair jobs, proposals, or design reviews could be active at once — would constraints reveal the real bottleneck within one or two weeks?
Where does your business keep a buffer that makes operations feel smooth — and what problem would become visible if that buffer were smaller?
Follow the evidence.
History is sourced below. Business lessons are editorial interpretations; future possibilities are questions to test, not predictions.
Prepared from primary-source histories. First edition: 25 Sept 2026.