TPS Relationships #4 - TOC and TPS Do Not Compete. They Ask Different Questions.
One perspective identifies where to focus improvement. The other helps us understand what must change.
TPS FUNDAMENTALSPROBLEM SOLVING
TOC and TPS Do Not Compete. They Ask Different Questions.
In many organizations, improvement methodologies are presented as alternatives from which one must choose.
Lean or Six Sigma.
Kaizen or innovation.
The Toyota Production System or the Theory of Constraints.
As if adopting one perspective required rejecting the others.
But real systems can rarely be understood through a single question.
The Theory of Constraints—TOC—and the Toyota Production System—TPS—observe the flow of work from different angles. TOC directs attention toward the point currently limiting overall performance. TPS seeks to understand the conditions within the system that allow that limitation to emerge, remain, or return.
One asks:
Where is the constraint?
The other asks:
Why does it exist?
These are not incompatible questions.
They are complementary ones.
The Constraint Determines the Performance of the System
Every system has a limited capacity to generate results.
In a production process, the constraint may be a machine. In a service operation, it may be an approval stage. In a supply chain, it may be material availability. In an organization, it may even be the speed at which decisions are made.
TOC reminds us of something fundamental: improving a part of the process that does not limit the system may generate more activity, but not necessarily better results.
A machine may run faster.
A department may reduce its lead time.
A team may exceed its targets.
But if the constraint remains unchanged, overall performance is unlikely to improve.
From this perspective, the organization’s first responsibility is to identify the point regulating the flow and protect it from interruptions, variability, and unnecessary work.
It is a powerful way to avoid dispersion.
Instead of trying to improve everything at once, TOC forces us to ask where an improvement made today would have the greatest effect.
TPS Observes More Than the Slowest Point
TPS is also deeply concerned with flow.
However, it does not stop at identifying the operation with the lowest capacity.
When work begins to accumulate at one station, TPS does not ask only how to make that station produce more. It also examines the conditions surrounding the problem:
Is standardized work in place?
Has the workload been leveled?
Does the operator receive complete materials on time?
Is quality built into the process?
Are there unnecessary motions?
Does the equipment suffer from recurring minor interruptions?
Does the design of the work depend on the experience of one person?
Is demand being released irregularly?
The visible constraint may be only the manifestation of a deeper problem.
An operation may appear slow because it receives defective parts. A machine may appear insufficient because it produces in batches that create lengthy changeovers. An operator may appear overloaded because they perform tasks that should have been eliminated or separated. An area may become a bottleneck because the previous process releases work without regard for the pace of the system.
In such cases, adding capacity may relieve the symptom without transforming the conditions that produced it.
TPS asks why the system needs that additional capacity in the first place.
Exploiting a Constraint Does Not Mean Overloading It
When a constraint is identified, a common reaction is to demand more from it.
More speed.
More hours.
Fewer pauses.
Greater pressure.
But a constraint is not used more effectively by exhausting people or running equipment without stopping.
It is used more effectively by eliminating whatever wastes its capacity.
If a critical operation loses time waiting for materials, searching for tools, correcting defects, resolving doubts, or processing work that was never necessary, the problem is not that it should work harder.
The problem is that the system is consuming its most limited resource on activities that do not create value.
This is where TOC and TPS meet clearly.
TOC helps us recognize that this time has special value because it belongs to the constraint. TPS provides a way to observe the work, distinguish value from waste, and redesign the conditions so that available capacity is used properly.
The constraint establishes the priority.
Direct observation helps us understand what must change.
Subordination Does Not Mean Keeping Everyone Busy
One of the most difficult ideas for many organizations to accept is that local efficiency can damage overall performance.
When every area attempts to maximize its own utilization, the system produces more work than the constraint can process. The result is inventory, growing backlogs, longer lead times, and an increasing inability to distinguish what is urgent from what is important.
People appear busy.
The system does not necessarily move forward.
TOC proposes subordinating all other activities to the needs of the constraint. TPS expresses a similar logic through the pull system: the previous process should not produce simply because it has available capacity, but in response to a real need from the next process.
Both perspectives challenge the same belief:
That keeping every resource operating at maximum capacity is the same as optimizing the system.
It is not.
A balanced process is not one in which nobody ever stops. It is one in which work moves with the fewest possible interruptions, accumulations, and delays.
At times, protecting the flow requires a non-constraint resource to wait.
That waiting may appear inefficient when viewed only through a local indicator. But it may be a rational decision when it prevents overproduction and keeps the true condition of the system visible.
The Bottleneck Can Move
A constraint is not necessarily permanent.
When a source of loss is eliminated, a changeover is improved, tasks are redistributed, or capacity is increased, the limiting point may shift elsewhere in the process.
That does not mean the previous improvement failed.
It means the system changed.
TOC helps us recognize this dynamic nature. Once a constraint no longer limits performance, the organization must observe the system again and identify the next one.
TPS adds an important warning: it is not enough to chase bottlenecks as they appear. The organization must also learn from the conditions that create them.
Otherwise, it may enter an endless cycle:
Identify an overloaded area.
Add people.
Buy equipment.
Move work.
Find a new overloaded area.
Add capacity again.
The system changes shape, but not necessarily the way it thinks.
The purpose should not be to live in permanent reaction to visible constraints. It should be to develop the ability to understand how work design, variability, quality, sequence, and decision-making create those constraints.
Not Every Constraint Is Found in Production
Sometimes the resource limiting the system is not located on the shop floor.
It may be found in engineering, purchasing, maintenance, planning, IT, sales, or management.
A line may have available capacity and still stop because a specification has not been released. A team may understand the problem but lack the authority to modify the standard. A plant may have space and personnel but still be waiting for an investment decision. A project may accumulate delays because every approval depends on one person.
In these cases, the constraint is not always physical.
It may be a policy, a rule, an authorization structure, or a way of measuring performance.
TOC allows us to broaden the observation beyond machines. TPS encourages us to go to the actual place, study the real situation, and avoid explanations built only from reports or conference rooms.
An administrative constraint must also be made visible.
And, like any other problem, it must be understood before it is corrected.
Focus and Learning
TOC provides focus.
It prevents continuous improvement from becoming a collection of disconnected projects. It reminds us that not every opportunity has the same impact and that system performance depends especially on a small number of critical points.
TPS provides depth.
It does not settle for increasing the capacity of one operation. It seeks to understand the work, reveal waste, reduce variability, develop standards, and strengthen people’s ability to solve problems.
One perspective helps decide where to look first.
The other helps us learn how to look.
Together, they help avoid two common mistakes.
The first is improving many things without changing overall performance.
The second is increasing the capacity of a constraint without understanding why it became a constraint.
The Complete Question
When a process fails to meet demand, the conversation should not end when the bottleneck is found.
That discovery is only the beginning of learning.
We should ask:
Where is the flow currently being limited?
What losses are consuming the capacity of that point?
Which parts of the system are producing more work than it can process?
What conditions caused that operation to become the constraint?
What standard, design, or decision needs to change?
What will we learn when the constraint moves?
TOC and TPS do not need to compete for the role of the definitive explanation.
A mature organization does not select methodologies as if choosing sides. It uses different perspectives to observe the system more clearly.
TOC asks where attention should be focused.
TPS asks what we must learn from what we find.
One identifies the point limiting present performance.
The other helps build a system in which problems become visible, can be understood, and become opportunities to develop people.
Because locating the constraint matters.
But understanding why it exists is what allows the system to be truly transformed.