Challenge the Thinking, Not Just the Rules: The Spirit of Constructive Defiance

Taiichi Ohno’s rebellious spirit offers a useful lens for understanding improvement. It was not simply a matter of refusing instructions or rejecting established practices. The more important distinction is between opposing a rule and questioning the thinking that makes the rule necessary.

These behaviors can look similar from a distance. Both may involve disagreement. Both may make people uncomfortable. Both may challenge authority.

But they move in different directions.

Resistance rejects what exists. Constructive defiance takes responsibility for creating something better.

For business leaders, that distinction matters. An organization that treats every challenge as disobedience can discourage improvement. An organization that treats every act of disobedience as innovation can lose the discipline required to operate reliably.

The challenge is to encourage people to question established thinking without making coordination, standards, and accountability optional.

Resistance Rejects. Constructive Defiance Improves.

Resistance says:

“I do not want to follow this instruction.”

Constructive defiance asks:

“What problem is this instruction meant to solve, and is there a better way to solve it?”

The difference is not politeness. A challenge can be expressed respectfully and still lack substance. Conversely, a difficult question can expose a genuine weakness in the current system.

The deeper distinction is whether the person challenging the practice accepts responsibility for improvement.

That responsibility includes understanding why the current method exists, observing its actual effects, proposing an alternative, testing it appropriately, and considering the consequences for others.

Simply refusing to follow a method does not demonstrate that another method is better.

Constructive defiance must go beyond disagreement. It must connect a challenge to a problem, a proposed change, and evidence of the result.

Standards: A Baseline to Improve, Not a Boundary on Thinking

Consider the difference between ignoring a standard and improving one.

A person who disregards a standard because it is inconvenient may introduce variation that others cannot anticipate. Even if the individual believes their method is faster, the change may affect quality, safety, timing, or the next process.

That is not automatically improvement. It may simply be an uncoordinated departure from the agreed method.

Constructive defiance begins with a different question:

“What is this standard intended to achieve, and where does it fall short?”

Perhaps the sequence requires unnecessary movement. Perhaps the standard assumes material location which is not defined. Perhaps the documented method no longer reflects actual operating conditions.

These are reasons to investigate—not reasons to pretend the standard does not exist.

The disciplined response is to observe the work, understand the gap, test an alternative under appropriate conditions, and revise the standard if the alternative proves better.

A standard therefore serves two purposes: it supports consistent work today, and it provides a reference point for improvement tomorrow.

Without a baseline, it becomes difficult to distinguish a meaningful improvement from a temporary or local variation.

The principle is not “obey and stop thinking.” It is “work from a shared method, and improve that method deliberately.”

When a Standard Cannot Be Followed

Respecting standards does not mean requiring people to continue work under unsafe conditions or conceal a problem to preserve the appearance of compliance.

If a standard cannot be followed safely, or if following it creates a quality risk, the problem must be surfaced and handled through the appropriate escalation process.

This is different from quietly choosing a personal method.

The important distinction is visibility and responsibility. Stopping to expose an abnormal condition helps the organization respond. Silently working around it can hide the condition and make the process appear more reliable than it is.

Constructive defiance does not demand blind obedience. It demands an honest relationship with reality.

Batch Production: Change the Conditions Behind the Rule

The distinction becomes especially clear in batch production.

Suppose a production rule calls for a large batch. An operator or manager decides that smaller batches are better and simply reduces the quantity.

The intention may be reasonable. But if changeovers remain lengthy, materials are not replenished appropriately, or downstream processes are unprepared, the result may be disruption rather than better flow.

Breaking the batch rule is not the same as removing the reasons for large batches.

Constructive defiance investigates those reasons.

Is the batch size driven by customer demand? By setup time? By equipment constraints? By transport arrangements? By a scheduling convention that has not been reconsidered?

Each explanation points toward different work.

If long changeovers make smaller batches impractical, reducing setup time may be necessary. If replenishment depends on infrequent deliveries, material movement may need to change. If performance measures reward long production runs, management may need to reconsider what those measures encourage.

The objective is not merely to announce a smaller batch size. It is to make smaller batches workable within the production system.

That is a more demanding challenge—and a more meaningful one.

Resistance breaks the existing rule. Constructive defiance changes the conditions that gave rise to it.

Production Planning: Redesign the System, Don’t Ignore It

Production plans present a similar challenge.

A supervisor may see that the schedule creates uneven workloads or unnecessary inventory. They may decide to change the sequence without consulting anyone else.

The local result might look better. But the change may also disrupt material preparation, another production area, or a customer commitment.

The problem is not that the supervisor questioned the plan. The problem is that unilateral action can transfer difficulty elsewhere without resolving its source.

Constructive defiance examines the planning logic itself.

Why does the plan create unevenness? Why is work released in large quantities? Why are processes producing ahead of actual need? What prevents work from moving more smoothly between operations?

Production leveling and one-piece flow represent ways to challenge that logic where operating conditions support them.

However, neither is simply a scheduling instruction.

Leveling requires attention to demand, capacity, production mix, and the ability to replenish. One-piece flow requires connected work, dependable quality, and suitable process conditions. Where direct flow is not feasible, the connection between processes still needs deliberate design.

The objective is not to abandon planning. It is to develop a planning and production system that supports more reliable flow.

Changing the schedule is an action. Improving the system that generates the schedule is a different level of work.

Local Freedom Is Not the Same as System Improvement

A useful test for any proposed change is to ask where the benefit appears—and where the burden goes.

Does one process become faster by building inventory for the next? Does one team simplify its work by increasing another team’s handling? Does one department meet its target by making the overall production sequence less stable?

A local improvement is not necessarily a system improvement.

This is why constructive defiance requires a broader view than personal preference or departmental convenience. The question is not simply, “Is my way easier?” It is, “Does this change improve the performance of the connected work?”

That may require conversations across functions, observation beyond one workstation, or a trial that measures more than the result in one area.

The willingness to challenge is important. The willingness to follow the consequences of that challenge is equally important.

What Leaders Should Encourage

Leaders need to hold two expectations together:

“We expect you to follow the current standard.”

“We also expect you to help us identify where it should improve.”

These expectations are not contradictory. They become contradictory only when the organization provides no practical way to connect them.

If employees are told to follow standards but their concerns are dismissed, compliance can become silence.

If employees are encouraged to innovate but no discipline governs changes, experimentation can become uncontrolled variation.

Leaders therefore need to make improvement both legitimate and concrete.

When someone questions a practice, a productive response is:

“What problem do you see? What have you observed? What change do you propose? How will we test it?”

These questions do not guarantee that every idea will be adopted. They establish that disagreement can lead somewhere useful.

They also place responsibility on both sides. Employees must bring more than dissatisfaction. Leaders must bring more than authority.

Separate a Failed Experiment From an Undisciplined Change

Not every well-designed improvement trial will succeed.

A smaller batch may reveal a replenishment weakness. A revised work sequence may create an unexpected quality concern. A proposed flow arrangement may prove unsuitable under actual demand conditions.

An unsuccessful result does not automatically mean the challenge was wrong to raise.

The relevant questions are whether the trial addressed a real problem, respected necessary safeguards, made its assumptions clear, and generated useful learning.

An undisciplined change is different. It bypasses coordination, obscures what was changed, or declares success without considering the consequences.

Leaders should avoid treating these two situations as equivalent.

If a responsible experiment is punished simply because it did not produce the expected result, people may stop exposing weaknesses. If an uncontrolled change is celebrated because it happened to work once, the organization may reward risk without learning.

Constructive defiance needs room to test ideas—and discipline in how those tests are conducted.

Turn a Challenge Into a Better Standard

The work is not complete when an experiment produces a promising result.

The organization still needs to determine whether the improvement is repeatable, whether it creates problems elsewhere, and what must change to sustain it.

If the method proves better, the standard should be updated. People affected by the change need to understand the new method and its purpose. Supporting arrangements may also need revision.

Otherwise, the improvement can remain dependent on one person’s attention or become an unofficial exception.

This is where constructive defiance comes full circle.

It begins by questioning a standard. It ends by establishing a better one.

The purpose is not to maintain permanent opposition to the organization. It is to strengthen the organization’s ability to work, learn, and improve.

The Real Meaning of a Rebellious Spirit

The distinction between resistance and constructive defiance is ultimately a distinction in responsibility.

Ignoring a standard is not the same as improving it.

Breaking a batch-production rule is not the same as making smaller batches practical.

Disregarding a production plan is not the same as building a better system for leveling work and supporting flow.

The visible act of disagreement is only the beginning. The real value lies in the observation, experimentation, coordination, and follow-through that come afterward.

Resistance says, “I will not do it your way.”

Constructive defiance says, “Let us understand why we do it this way—and prove that a better way is possible.”

That is the rebellious spirit worth cultivating: not defiance for its own sake, but the determination to challenge established thinking and take responsibility for what comes next.