Just-in-Time Isn’t Just for Manufacturing
Just-in-Time is one of the most recognized ideas associated with Toyota, and also one of the most narrowly understood.
For decades, JIT has been described primarily as an inventory strategy: keep fewer parts on hand, have suppliers deliver materials closer to when they are needed, reduce storage costs, and avoid tying up capital in excess stock. That description is not necessarily wrong, but it is incomplete.
When I worked at Toyota, Just-in-Time was part of a much larger way of thinking about how work should move. The principle wasn’t simply to have less inventory. It was to create a system in which what was needed could move to where it was needed, when it was needed, in the amount needed.
That distinction matters because once you understand JIT as a principle of flow rather than simply inventory reduction, its relevance extends far beyond manufacturing.
Service businesses have inventory, too. You just can’t always see it sitting on a shelf.
What Just-in-Time Actually Means
Within the Toyota Production System, Just-in-Time is one of two foundational pillars, alongside Jidoka. As I explain in The Real Lesson Most Companies Miss About the Toyota Production System, Toyota JIT focuses on delivering the right item at the right time and in the right quantity.
That sounds simple. In practice, it requires an organization to understand demand, timing, capacity, handoffs, and the movement of work through the entire system.
This is why reducing JIT to “keeping less inventory” misses so much of its value.
The more useful questions are: What does the customer need? When do they need it? What needs to happen immediately before that? Where is work accumulating faster than it can move? What information is required for the next step? And what is preventing the work from flowing as expected?
Inventory matters because excess inventory is often evidence that something in that flow is out of balance. But the principle behind JIT is much larger than the inventory itself.
Why Inventory Became the Focus
In manufacturing, inventory is easy to see. Walk through a facility and you can see materials waiting to be processed, components stacked between production stages, and finished products waiting to be shipped.
That visibility makes inventory relatively easy to measure. It also explains why conversations about JIT often become conversations about reducing physical stock.
But inventory can serve another function: it can hide problems.
If one part of a process produces faster than the next part can handle, inventory accumulates between them. If a process is unreliable, organizations may compensate with additional stock. If production happens long before actual demand exists, finished goods have to sit somewhere.
The inventory is visible. The operational conditions that created it may not be.
The same dynamic exists in service companies, except the accumulation is much harder to see.
Service Businesses Have Inventory Too
Consider a consulting firm with 30 active client projects, even though the team only has the capacity to move 15 of them forward effectively. Or a company where proposals regularly wait several days for executive approval. A new client signs a contract on Monday but cannot begin onboarding until the following week. A customer support request moves from one department to another and waits in each person’s queue.
None of these organizations has a warehouse full of parts. They still have work sitting in the system.
In a service business, inventory can take the form of unfinished projects, open requests, pending approvals, unanswered emails, unprocessed applications, clients waiting for onboarding, reports waiting for review, or decisions waiting for a leader.
This is one reason understanding the flow of both work and information is so important. In Process Mapping: Why Systems Don’t Fail — Your Workflow Does, I explain how every operational process contains both a goods flow and an information flow. In service organizations especially, information often determines whether the work can move forward at all.
The cost of this invisible inventory can be substantial. Asana’s Anatomy of Work Global Index found that knowledge workers spent 58% of their day on “work about work”, meaning activities such as coordinating work rather than completing skilled or strategic work. Respondents estimated that better processes could save them 4.9 hours every week.
For service businesses, this is where the principles behind JIT become particularly useful. The question is no longer how many physical items are sitting in storage. It becomes: How much work have we started that isn’t actually moving?
Starting More Work Doesn’t Mean Completing More Work
One of the easiest mistakes to make in a growing company is to confuse activity with flow.
Demand increases, so more projects get started. A new initiative appears, so it gets added to the existing priorities. A client makes a request, so someone immediately begins working on it. Every department tries to keep its people fully occupied.
Individually, each decision can seem productive. Across the entire system, the result can be the opposite.
More work in progress means more competing priorities, more handoffs to manage, more context switching, and more opportunities for work to wait between steps. People stay busy while the time required to deliver something from beginning to end gets longer.
Atlassian’s State of Teams research illustrates the problem. Sixty-four percent of knowledge workers said their teams were constantly being pulled in too many directions, and 70% said it would be easier to make progress if they had fewer, more specific goals.
This is where JIT challenges a common assumption about efficiency. The goal isn’t necessarily to make every person or department as busy as possible. The goal is to help value move through the entire system in response to actual demand.
A company can have every employee working at full capacity and still have terrible flow.
What JIT Looks Like in a Service Business
Applying Just-in-Time to services does not mean copying a Toyota production line. The application has to change because the work is different. The principle, however, remains useful.
Take client onboarding. A company may collect every possible piece of information from a new customer immediately, distribute it to multiple departments, and launch a long list of tasks simultaneously. But if several of those tasks cannot begin for another two weeks, starting them early may simply create more work to track.
A JIT mindset asks what information and activity are required for the next step to happen successfully.
The same principle applies to approvals. If dozens of routine decisions continually accumulate in a senior leader’s inbox, the problem isn’t simply that the executive needs to approve things faster. Decision rights may need to move closer to where the work happens so information and decisions are available when the process requires them.
Project portfolios offer another example. Starting ten initiatives does not create ten times the progress. If the organization has the capacity to execute three well, limiting work in progress may allow those three to reach completion faster before capacity is released for the next priorities.
The objective in each case is not speed for its own sake. It is flow.
Find Where the Work Is Waiting
One of the most useful ways to apply JIT thinking to a service organization is to stop looking only at where people are working and start looking at where work is waiting.
Waiting may happen between sales and operations, between an employee and a manager, between a customer request and a response, or between one department completing its work and another beginning theirs.
These delays are often difficult to detect because no single step looks particularly broken. The problem becomes visible only when you look at the process from end to end.
As I explain in How to Identify Bottlenecks in a Process, service bottlenecks frequently come from delayed decisions, missing information, and unclear ownership between roles. Mapping the process makes those constraints visible instead of relying on assumptions about where the problem is occurring.
That visibility is critical because adding capacity to the wrong part of a process does not necessarily improve flow. It may simply allow more work to reach the bottleneck faster.
JIT Does Not Mean Eliminating Every Buffer
There is another misconception worth addressing. Just-in-Time does not mean stripping every buffer, every bit of spare capacity, or every form of redundancy out of a business.
That can make an operation fragile rather than efficient.
Variation exists. Demand changes. Employees get sick. Technology fails. Suppliers encounter problems. Customers behave unpredictably. A well-designed operation has to account for reality.
The better question is why a particular buffer exists.
If additional capacity protects the organization from a meaningful and understood source of variation, it may be appropriate. But if the buffer exists because nobody trusts the process, because handoffs are unreliable, or because teams cannot predict when work will arrive, then it may be compensating for a deeper operational problem.
JIT isn’t a race toward zero. It is a discipline of understanding what the system actually needs.
JIT Is Really a Lesson About Flow
The enduring value of Just-in-Time isn’t that Toyota found a clever way to keep fewer parts in a warehouse. It is that JIT forces an organization to pay attention to demand, timing, capacity, and the movement of value through a system.
Those questions matter whether your company manufactures vehicles, manages client accounts, develops software, processes insurance claims, runs a professional services firm, or onboards customers.
Every organization has flow. Every organization has demand. And every organization has some form of work sitting somewhere waiting to move.
For leaders in service businesses, that may be the most useful way to rethink JIT. Don’t begin by asking how you can copy a manufacturing practice. Begin by looking at your own operation and asking:
Where is work accumulating, why is it waiting, and what would need to change for it to move when the customer actually needs it?
That is where Just-in-Time becomes much more than an inventory strategy.
Want to Work With Us?
What if you could see exactly where work is getting stuck?
In our 1-day virtual FlowState Workshop, we help your team map how work and information move across departments, uncover bottlenecks, and identify opportunities to improve flow.
Stop guessing where the delays are. Start seeing the entire system.
