“Check means to reflect.”

“Check means to reflect.”

Taiichi Ohno

Taiichi Ohno’s words are easy to quote, but they become much more powerful when we slow down and ask what they mean in practice. In the Plan-Do-Check-Act cycle, the word *Check* is often misunderstood as a simple comparison: Did we hit the target or not? Did the numbers match the plan? Did we succeed?

But in Ohno’s view, *Check* goes far deeper than measurement. It is not merely about verifying outcomes. It is about reflection — a disciplined, honest look at what actually happened, why it happened, and what it reveals about our process.

Ohno put it bluntly:

“Everyone investigates the reason for not accomplishing the target, but almost no one reflects on why we accomplished the goal. It is important to deeply investigate and utilize.”

Wow, Mr. Ohno. I must first confess that NOT everyone investigates why the target was not met. Instead, they are busy making excuses. 🫣

That is a profound challenge. We are usually quick to explain failure, but far less disciplined when things go well. Yet if we only study misses, we learn very little about what truly drives performance. The real opportunity lies in understanding success with the same seriousness we give to failure.

Why did we hit the target?

That question sounds simple, but it can uncover very different truths.

1. Sometimes success is explained away

In organizations where people are quick to make excuses for poor results, they often do the same for good results. A target is met, and the response becomes, “The product was easy,” or “The machine was in good condition,” or “The team had a lucky day.”

When that happens, the target loses meaning. Success is treated as an accident instead of something worth studying. And if we refuse to examine what worked, we also refuse to build on it.

2. Sometimes the numbers hide the real cost

Not every accomplished target is a true achievement. If the result was reached by breaking standards, skipping preventive maintenance, adding people without improving the process, or sacrificing quality for volume, then the number may look good — but the organization has not actually improved.

That is why reflection matters. A good result deserves celebration only when it is achieved in a way that strengthens the system rather than quietly weakens it.

3. Sometimes success reveals a better standard

This is where reflection becomes valuable. Imagine a factory struggling to meet its target. One day, one shift succeeds. Instead of shrugging it off as a one-time event, the team investigates how it happened. They discover that the team leader’s pre-shift routine was different. That insight gets standardized across all shifts, and performance improves.

This is the heart of improvement: not just achieving a result once, but understanding the method that made it possible and turning it into a better standard.

4. Sometimes stable performance is the start of deeper kaizen

Even when targets are consistently met, the work is not finished. In fact, stable performance creates room for a new question: what more can we improve?

Can we reduce required manpower? Increase flexibility for small batches? Lower inventory? Improve flow? Simplify changeovers?

Good management does not stop at celebration. It uses success as evidence that the system can be pushed further.

The real lesson of “Check”

Ohno’s insight is not just about manufacturing. It applies to any team, any organization, and any person trying to improve.

Reflection means asking:

- What happened?

- Why did it happen?

- Was it the right kind of success?

- What should we standardize?

- What should we improve next?

That is why *Check* is not passive. It is an active discipline. It helps us learn from both failure and success, and it keeps us from mistaking a good number for real progress.

In the end, the best results are not simply achieved — they are understood, tested, and turned into better standards.

And that is what makes improvement last.