Just This Once — How Exceptions Become the Standard

Just This Once — How Exceptions Become the Standard

Years ago, I heard a story about the owner of a company that manufactured shampoo.

He had spent years trying to get his product into Walmart.

The product was good. He believed in it. He had approached them several times.

And several times, Walmart had said no.

Until one day, they finally said yes.

Not only that.

They placed an initial order for 10,000 cases.

For a small manufacturer, this was not simply another purchase order. It was the opportunity they had been waiting for.

The owner returned to the company excited and gathered his managers to share the news.

Everyone celebrated.

Except the production manager.

He was doing the math.

Ten thousand cases.

Available capacity.

People.

Machines.

Materials.

Time.

And eventually he said what nobody else wanted to hear:

We cannot produce that quantity by the requested date under our current conditions.

The room probably became a little quieter.

Because suddenly the biggest opportunity the company had received was also a problem.

And then came four very dangerous words:

“Just this once…”

Maybe they could add another shift.

Maybe postpone preventive maintenance.

Maybe skip a verification.

Maybe accept more overtime than usual.

Maybe move people from another operation.

Maybe inspect less frequently.

Maybe temporarily change a process that had been established for a reason.

Whatever the specific compromise was, the logic would have been understandable.

This customer could change the future of the company.

We cannot lose the order.

So, just this once.

And that is where an exception begins.

Not necessarily because someone is careless.

Sometimes it begins because people care very much.

They want to protect the customer.

They want to protect the business.

They want to deliver.

They want to solve the immediate problem.

And sometimes the exception may even be the right decision.

The danger comes later.

When the exception works

Imagine they make it.

Ten thousand cases produced.

The truck leaves on time.

The customer is satisfied.

Everyone is exhausted, but everyone is celebrating.

And something very subtle has happened.

The organization has learned:

We can do it.

The maintenance that was postponed did not immediately cause a breakdown.

The extra overtime did not immediately create a visible problem.

The skipped verification did not result in a customer complaint.

The workaround worked.

Nothing terrible happened.

So when the next urgent order arrives, the conversation becomes easier.

“We did it last time.”

Then again.

And again.

What began as an exception slowly becomes a workaround.

The workaround becomes a habit.

The habit becomes an expectation.

And eventually the expectation becomes the new standard.

Exception → Workaround → Habit → Expectation → Standard

The interesting part is that nobody ever formally decided to change the standard.

It simply changed through repetition.

Standards do not exist by themselves

This is where the conversation becomes bigger than procedures.

A standard is not supposed to be an arbitrary rule.

Ideally, there is something behind it.

Values → Principles → Standards → Actions

Values describe what matters to us.

Principles guide how we make decisions around those values.

Standards translate those principles into repeatable ways of working.

Actions are what we actually do when reality puts all of them under pressure.

And pressure is where this chain becomes visible.

A company may say:

Quality first.

But suppose every time delivery is at risk, quality controls are relaxed.

The posters may still say “Quality First.”

The presentations may still say “Quality First.”

Leadership may still say “Quality First.”

But the system is teaching people something else:

Delivery first. Quality when possible.

And people eventually believe the system more than the speech.

That is why exceptions deserve much more attention than we usually give them.

They reveal what the organization truly protects when two priorities collide.

Breaking a standard is not always abandoning a principle

There is an important distinction here.

Standards should not become dogma.

Reality changes.

Customers change.

Technology changes.

Conditions change.

Sometimes following the existing standard may no longer be the best decision.

Sometimes an unusual situation genuinely requires an unusual response.

So temporarily breaking a standard does not automatically mean abandoning the principle behind it.

But it should create a question.

Why did reality force us outside the standard?

That question matters.

Because if the exception was necessary, something in the system deserves attention.

Perhaps capacity is insufficient.

Perhaps the standard no longer reflects reality.

Perhaps the planning process failed.

Perhaps the equipment is unreliable.

Perhaps the customer demand pattern changed.

Perhaps the process was designed with assumptions that are no longer true.

The exception is information.

And information should trigger learning.

The Andon after the emergency

We normally think about Andon as something that happens when an abnormal condition appears.

Stop.

Signal.

Ask for help.

Understand the problem.

Restore the process.

But some situations cannot be stopped immediately.

Sometimes the customer still needs the order.

Sometimes the truck still has to leave.

Sometimes the organization consciously accepts a temporary risk because the alternative is worse.

Fine.

Handle the emergency.

But the Andon should not disappear simply because the emergency is over.

In those situations, perhaps we need something like an Andon after the fact.

Once the immediate pressure is gone, the exception itself should become a problem to study.

What condition forced us to deviate?

What did we compromise?

What risk did we accept?

What needs to change before this happens again?

And perhaps the most important question:

What must be different before we allow the same exception one more time?

Because “we survived” is not the same as “the process worked.”

Exceptions need an expiration date

An exception should never quietly become permanent.

If we consciously decide to operate outside the standard, that decision should carry an expiration date.

Not necessarily a date on a calendar.

A condition.

We will do this temporarily until ______ changes.

Until capacity is increased.

Until the equipment is repaired.

Until the standard is revised.

Until another supplier is qualified.

Until the root cause is understood.

Until the system can operate again without depending on the workaround.

Without that condition, temporary solutions have a remarkable ability to become permanent.

And once they do, people may stop seeing them as abnormal.

That is perhaps the most dangerous moment.

Not when someone breaks the standard.

But when nobody remembers that it was ever broken.

What pressure teaches

Every organization eventually faces situations where values collide.

Quality versus delivery.

Safety versus speed.

Cost versus reliability.

Customer urgency versus employee burden.

There will not always be a perfect answer.

But those moments teach the organization something.

People watch what leaders protect.

They watch what gets sacrificed.

They watch which standards become negotiable when pressure increases.

And they remember.

Culture is built partly through those moments.

Not through what we say matters when everything is going well, but through what the system protects when keeping everything becomes impossible.

That is why the phrase “just this once” deserves attention.

It does not always mean the decision is wrong.

Sometimes it may be exactly what the situation requires.

But it should always leave a trace.

A question.

An Andon.

A reason to learn.

Because the dangerous words are not really:

“Just this once.”

The dangerous part is when nobody asks:

What must change before there is a next time?