Build a system where making bad products results in a loss

Build a system where making bad products results in a loss.

Inspired by the management philosophy of Taiichi Ohno.

One of the most important principles in manufacturing can be expressed in a simple but provocative statement:

Make a bad product, and you should lose.

At first, this may sound harsh. It might even appear to promote punishment. But that is not the point. The principle is really about accountability, feedback, and the thoughtful design of management systems.

In many companies, the true cost of producing a defective product is absorbed somewhere else in the organization. The product is sent for rework. A technician fixes it. A quality inspector catches the problem. The production schedule is adjusted, overtime is approved, and additional resources are assigned.

Eventually, the defect disappears from the daily performance numbers.

Meanwhile, the manager, department, or process that created the problem may never experience its consequences. Production still reaches its output target. The line continues running. The customer may never know what happened.

The organization appears to have solved the problem, but in reality, it has only hidden it.

That is dangerous because a system that absorbs failure without exposing its source has little reason to improve.

When Poor Quality Is Free, It Will Continue

Imagine a production process in which an operator can produce a defective part without stopping the line.

The defect is discovered later during inspection. It is removed from the normal flow and sent to another department for correction.

The operator does not lose anything.

The supervisor does not lose anything.

The production department still achieves its output target.

The defect simply becomes someone else’s responsibility.

What kind of behavior does this system encourage?

Nobody needs to intentionally produce bad products for quality to deteriorate. The design of the system has already communicated an implicit message:

“It is acceptable to create defects because someone else will take care of them.”

Over time, this assumption becomes embedded in the organization. Rework becomes normal. Extra inspection becomes necessary. Buffers grow. More inventory is added to protect downstream operations, and overtime is used to recover from recurring problems.

People become highly skilled at managing defects without ever eliminating their causes.

This is how quality problems become institutionalized. The organization does not formally approve poor quality, but its management system quietly tolerates and even protects it.

Make the Process Feel the Consequence

The principle of “make a bad product and lose” does not mean punishing employees whenever something goes wrong.

Punishment often creates the opposite of the desired result. When people fear blame, they hide defects, manipulate numbers, delay reporting, and avoid taking responsibility. The problem remains in the process, but management loses the ability to see it.

I visited a plant where employees were punished for reporting defects. Predictably, the number of recorded defects fell—but the defects themselves did not disappear. Customer complaints increased, costs skyrocketed, and quality deteriorated. Punishing people did not solve the problem; it merely encouraged them to hide it.

A healthy production system must make it safe to expose problems while making it difficult to ignore them.

When a defect occurs:

The process should stop when appropriate.

The abnormality should become immediately visible.

The responsible team should respond quickly.

The cause should be investigated.

The current standard should be reviewed.

The process should be improved to prevent recurrence.

The consequence should be experienced where the problem occurs, not transferred to an inspector, a rework team, or the next process.

This is one of the most powerful ideas behind the Toyota Production System. Problems should not be allowed to travel silently through the organization. They should create an immediate signal that something in the process requires attention.

Build Quality Into the Process

End-of-line inspection can tell you that a defect has already been produced. It may protect the customer from receiving the defective product, but it does not prevent the organization from creating another one.

Inspection detects failure. It does not necessarily build capability.

A stronger management system asks a different question:

“How can we make it difficult, or even impossible, for this defect to occur?”

That question leads to practices such as jidouka, poka-yoke, standardized work, and management with your own eyes.

Jidouka gives a process the ability to detect abnormalities and stop rather than continuing to produce defects. Poka-yoke uses mistake-proofing techniques to prevent errors or make them immediately obvious. Standardized work establishes the current best-known method for performing a task. Visual controls allow people to recognize normal and abnormal conditions at a glance.

Together, these mechanisms help build quality directly into the production process.

When something abnormal occurs, the process responds immediately. The problem cannot quietly move to the next workstation, where it becomes more expensive and difficult to correct.

The result is a powerful learning relationship:

Bad product → Immediate consequence → Problem solving → Kaizen

Every defect becomes an opportunity to strengthen the process. Over time, the organization becomes increasingly capable of producing quality at the source rather than inspecting quality into the product afterward.

The Same Principle Applies to Management

This idea extends far beyond product quality.

Consider production planning. If a plan is consistently unrealistic but nothing happens when it is missed, the planning process will never improve. Managers will simply create another plan based on the same assumptions.

Consider inventory. If excessive inventory creates no visible consequence, inventory will continue to grow. It will hide equipment problems, unstable processes, unreliable suppliers, and poor coordination between departments.

Consider equipment maintenance. If machines repeatedly break down but production always recovers through overtime, emergency repairs, and heroic effort, the organization may never address the underlying maintenance problem.

Consider standardized work: when process variations are repeatedly accepted by management, the standard gradually loses its significance and eventually becomes meaningless.

In each situation, leaders should ask:

What happens when the system produces the wrong result?

If the honest answer is “nothing,” the management system may be reinforcing the very behavior the organization claims it wants to eliminate.

A system cannot improve when failure is consistently hidden, transferred, or absorbed.

Good Systems Create Natural Feedback

Weak management systems depend heavily on reminders and pressure.

Managers repeatedly tell employees:

“Be careful.”

“Do better.”

“Pay more attention.”

“Don’t make mistakes.”

These instructions may create temporary awareness, but they rarely produce lasting improvement. People do not usually fail because they have forgotten that quality matters. They fail because the process makes errors possible, difficult to detect, or easy to pass downstream.

A good management system does not rely on constant warnings. The system itself provides feedback.

When something goes wrong, it becomes visible.

When it becomes visible, someone responds.

When someone responds, the cause is investigated.

When the cause is understood, a countermeasure is developed.

When the countermeasure proves effective, it becomes part of the new standard.

This creates a continuous cycle of organizational learning:

Problem → Response → Cause → Countermeasure → New standard → Better process

Through this cycle, the organization develops more than improved products. It develops people who can recognize abnormalities, investigate causes, test countermeasures, and strengthen standards.

That capability is one of the most valuable outcomes of a well-designed production system.

The Goal Is Not to Punish Failure

There is an essential distinction between exposing a problem and punishing the person who reports it.

A company should never create a culture in which employees hide problems because they are afraid of blame. Such a culture does not eliminate failure. It only eliminates visibility.

People should feel safe to stop the process, report an abnormality, question a standard, and ask for help.

But psychological safety should not become organizational passivity. Once a problem is exposed, the organization must respond. It cannot simply acknowledge the defect, repair the product, and return to business as usual.

The appropriate message is:

“Thank you for exposing the problem. Now let’s understand why it happened and make sure it does not happen again.”

That is a healthier and more effective form of accountability.

It separates the person from the problem while still demanding improvement from the process.

Stop Rewarding Heroic Recovery

Many organizations unintentionally reward the people who rescue them from recurring problems.

Someone works late to repair defective products. A supervisor rearranges the production schedule. A maintenance technician brings a broken machine back online. A manager persuades a customer to accept a delayed delivery.

These efforts may be necessary in the moment, and the people involved may deserve recognition. However, a dangerous pattern develops when recovery receives more attention than prevention.

The organization begins celebrating heroes while tolerating the conditions that repeatedly require heroism.

The better question is not merely, “Who saved us this time?”

It is:

“Why did the system require a ‘hero’ again?”

A mature organization appreciates immediate recovery but places greater value on eliminating the need for the same recovery in the future.

Ask Yourself One Question

When you examine your factory or management system, ask:

“If we make a bad product today, who actually loses?”

If the answers sound like these, you may have discovered a fundamental weakness:

“Production does not lose.”

“Quality does not lose.”

“The process does not stop.”

“The output numbers still look good.”

“The customer has not complained yet.”

“Someone in rework will fix it.”

When no one feels the consequence, the organization receives no meaningful signal to change.

The defect becomes an accepted cost rather than a reason to improve.

Do not simply tell people to produce better products.

Build a system in which producing a bad product creates an immediate and visible need for investigation, learning, and improvement.

When poor quality has no consequence, the organization learns that poor quality is acceptable.

When poor quality creates clear feedback, the organization learns how to prevent it.

Do not manage quality primarily through inspection. Build a system in which the process itself demands quality.

Reference.

日刊工業新聞社編. (2005). トヨタ強さの原点 大野耐一の改善魂. 日刊工業新聞社.