Your TPS Implementation Is Failing Because You Have Made Problem Solving Optional

Let me say something uncomfortable about Toyota Production System (TPS):

Most companies do not fail at TPS because their people cannot solve problems.

They fail because the organization has made it possible to survive without solving them.

You can train people in A3.

You can teach 5 Why.

You can introduce standardized work.

You can install Andon.

You can put visual management boards all over the factory.

And still fail.

Why?

Because none of these tools matter if the organization can continue operating while problems remain unsolved.

Stop Blaming the Workers

When TPS implementation stalls, management often says:

> "Our people don't have enough problem-solving skills."

This is often the wrong diagnosis.

The real problem may be much higher up.

Ask yourself:

What happens when someone does not solve a recurring problem?

Does production stop?

Does management go to the Genba to understand?

Does someone have to investigate the cause?

Does the problem appear on the management agenda?

Does anyone follow up?

Or does everyone simply work around it?

If nothing happens, you have already answered the question.

Problem solving is optional in your organization.

And people are behaving rationally.

Your Buffers Are Hiding Your Problems

Consider what happens when a process is unstable.

Instead of fixing it, you add inventory.

When production falls behind, you add more people.

When a machine repeatedly breaks down, you keep a spare machine.

When defects occur, you add inspectors.

When materials are late, someone expedites them.

When standardized work is ignored, the supervisor simply tells the operator to "be careful."

Congratulations.

You have solved the problem.

Except you haven't.

You have paid money to hide it.

This is one of the most dangerous forms of management in manufacturing.

The problem disappears from the manager's view while remaining inside the process.

A Factory Without Problems Is Probably Hiding Them

This is where many companies misunderstand TPS.

They think the goal is to create a factory with fewer problems.

Not exactly.

The first goal is to create a factory where problems cannot hide.

A factory that appears to run smoothly may actually be full of hidden abnormalities.

Excess inventory hides material problems.

Large production batches hide quality problems.

Inspection hides process problems.

Overtime hides capacity problems.

Expediting hides planning problems.

Extra people hide productivity problems.

And management reports hide all of them behind numbers.

TPS removes these cushions.

Why?

Because when the cushions disappear, problems become impossible to ignore.

And once problems become visible, people are forced to think.

That is when improvement begins.

Don't Create a Culture That Rewards Firefighting

Many organizations unintentionally reward firefighters.

Someone stays late to rework defect.

Someone works Saturday to recover production.

Someone personally calls a supplier and gets an emergency shipment.

Everyone applauds.

"Great job!"

But what happens next?

The same problem occurs again.

And the same person saves the day again.

This is not excellence.

This is a system designed to reproduce problems.

If you reward people for heroically recovering from problems but do not demand elimination of the causes, you are institutionalizing firefighting.

The hero becomes necessary because the system is broken.

And management becomes comfortable with the hero.

That is the trap.

The Worst Problem Is a Problem That Has Become Normal

The most dangerous problems in a factory are not necessarily the biggest ones.

They are the problems everyone has stopped seeing.

"That's normal."

"That machine always does that."

"We always need overtime at the end of the month."

"That supplier is always late."

"Those parts always need rework."

"That's just how this process works."

These statements should terrify management.

Because once an abnormality becomes "normal," nobody feels responsible for solving it.

The organization has stopped seeing the problem as a problem.

Management Must Make Problems Expensive

Not necessarily financially expensive.

Management-attention expensive.

A recurring defect should create management attention.

A deviation from the standard should trigger investigation.

A missed target should require understanding the reason.

A machine breakdown should lead to more than simply getting the machine running again.

A repeated abnormality should be unacceptable.

Not because people should be punished.

But because the organization must refuse to normalize abnormal conditions.

If management tolerates recurring problems, employees learn a very simple lesson:

> "Don't solve it. Just keep production moving."

That lesson will defeat every Lean training program you purchase.

Standards Are Not Documentation

This is also why standardized work is so important.

A standard gives you a reference point.

Without a standard, you can say:

"Something went wrong."

With a standard, you can ask:

"Where did reality deviate from the standard?"

That difference is the starting point for problem solving.

And when the standard itself is no longer adequate, improvement should change the standard.

Standard and improvement are not separate activities.

The standard exposes the gap.

The gap creates the problem.

The problem drives investigation.

The investigation produces improvement.

The improvement creates a new standard.

That is the cycle.

Stop Asking, "Who Made the Mistake?"

Ask:

"Why was this mistake allowed to happen?"

This is the fundamental difference between blaming people and improving the system.

If an operator makes the same mistake repeatedly, simply telling the operator to "pay more attention" is not problem solving.

If a mistake can produce a defect, the process should be designed so that the mistake is difficult—or impossible—to make.

If a machine can produce an abnormal condition, the abnormality should be detected immediately.

If a defect can escape to the next process, the process should stop or signal the problem.

We need a management-led system that shifts the culture from blaming people to involving them in controlling and improving processes.

The leader Has to Decide What Is Unacceptable

TPS implementation ultimately comes down to management behavior.

If the leader says:

"Keep production running at all costs,"

employees will hide problems.

If the leader says:

"Do not stop the line,"

Andon becomes decoration.

If the leader says:

"Hit the monthly number,"

overtime and inventory will become the solution.

If the leader says:

"Do not allow the same problem to happen twice,"

the organization starts behaving differently.

The system follows management's reaction to problems.

Not its slogans.

Not its a department.

Not its training program.

Its reaction.

The Ultimate TPS Question

So forget the question:

"How mature is our improvement program?"

Ask this instead:

"Can our factory continue operating indefinitely without solving its recurring problems?"

If the answer is yes, your TPS implementation is in serious trouble.

Because you have created a system where problem solving is optional.

And when problem solving is optional, people will choose the path of least resistance.

They will contain.

They will rework.

They will expedite.

They will add inventory.

They will work overtime.

They will apologize.

They will firefight.

And tomorrow, they will face the same problem again.

That is not TPS.

That is a system for managing failure.

TPS is different.

TPS deliberately creates an environment where abnormalities become visible, where problems cannot be comfortably ignored, and where management expects causes—not symptoms—to be eliminated.

So perhaps the first question in your TPS transformation should not be:

"How do we teach our people to solve problems?"

It should be:

"What have we done as management to make problem solving unavoidable?"

If you cannot answer that question, don't start another training program.

Fix the environment first.