The Pursuit of Excellence
Richard Thorn,
“Perfection is not attainable. But if we chase perfection, we can catch excellence.”
— Vince Lombardi
Nobody running a factory seriously believes perfection is achievable. There will always be another breakdown, quality issue, constraint, customer requirement or process that could be made easier, faster, safer or more reliable. So if perfection isn't achievable, what's the point of pursuing it?
Excellence isn't a destination
A manufacturing operation can be performing well today and still have opportunities to improve tomorrow.
A process might be meeting its target.
A machine might be achieving its expected availability.
A product might consistently meet specification.
That's good. But good enough shouldn't automatically become the standard.
Could the changeover be simpler? Could a recurring stoppage be eliminated rather than managed? Could an inspection be reduced without compromising quality? Could an operator spend less time searching, walking or waiting?
These questions come from a simple belief: Today's standard doesn't have to be tomorrow's standard.
The factory tells you where to look
Walk through a manufacturing operation and you'll see evidence of yesterday's decisions everywhere.
A fixture designed around an old product.
A workstation arranged around the way someone used to do the job.
A maintenance routine created after a failure five years ago.
A workaround that quietly became part of the process.
None of those decisions were necessarily wrong. They may have been exactly right at the time. But circumstances change. Products, volumes, technology, people and customer expectations all move on. Which raises a useful question:
If we were designing this process today, would we design it this way?
Sometimes the answer is yes. Sometimes it isn't. Either way, asking the question is valuable.
Improvement starts with a standard
Continuous Improvement isn't about constantly changing things for the sake of change. You need to know what should be happening before you can meaningfully improve it.
So start with three questions:
What should be happening?
What is actually happening?
What could be better?
The gap between those three questions is where improvement begins. And that distinction matters because activity isn't the same as improvement. Meetings, workshops, action lists, ideas and reports can all create the appearance of progress. The real question is simpler:
What changed?
Did downtime fall? Did output increase? Did scrap decrease? Did quality improve? Did the process become safer or more reliable? Did the operator spend less time on non-value-adding work?
And most importantly: Did the improvement last?
Not every improvement needs a project
Pursuing excellence doesn't mean chasing every possible improvement. Time, people and resources are limited. Not every problem deserves a project, and not every idea needs immediate action. Good Continuous Improvement requires judgement.
Which problems matter?
Which opportunities are worth pursuing?
What would success look like?
How much investigation is appropriate?
How will we know whether the change actually worked?
The process should be proportionate. A two-minute improvement shouldn't require a two-month project. But a significant change shouldn't rely on enthusiasm and crossed fingers either. The organization needs a consistent way to decide where improvement effort is worth spending.
Improvement should become normal
The strongest Continuous Improvement cultures don't feel like they're running a permanent improvement program. Improvement simply becomes part of how people work.
Someone notices something.
They question it.
A better way is proposed.
The opportunity is evaluated.
The change is tested.
The result is measured.
If it works, the new method becomes the standard.
Then someone looks again.
That cycle might take two minutes or two months. The scale changes. The principle doesn't:
Find a better way. Test it. Learn from it. Make it stick. Then look again.
Excellence is built incrementally
The pursuit of excellence doesn't require transformation overnight.
A slightly better process. A slightly more reliable machine. A shorter changeover. A better quality result. An easier job.
None of these looks transformational on its own. But repeated improvement compounds. The more important question is:
Are we getting better at getting better?
Are people comfortable identifying problems?
Are ideas evaluated effectively?
Are improvements tested rather than assumed?
Are results measured?
Are successful changes standardized?
Are lessons shared?
If the answer is increasingly yes, the organization is building something more valuable than a collection of improvement projects. It's building the capability to improve.
Leadership sets the tone
That capability is shaped by leadership.
What happens when someone raises a problem? Are they thanked for finding it, or asked why it happened?
What happens when someone suggests a different way of working? Is the idea explored, or dismissed because “that's how we've always done it”?
What happens when an experiment doesn't work? Is it treated as failure, or as useful learning?
People quickly learn whether improvement is genuinely encouraged or merely talked about.
The goal isn't perfection
Perhaps the most useful interpretation of the pursuit of excellence is this:
You don't need to achieve perfection to benefit from pursuing it.
The objective isn't to create an organization where nothing ever goes wrong. It's to create an organization that doesn't become comfortable with problems simply because they've been there for a long time.
From mindset to method
A Continuous Improvement culture needs more than good intentions. People need a practical way to turn observations into action:
Opportunity → Evaluation → PDCA → Implementation → Verification
The process should be simple enough for everyday improvements, controlled enough for significant changes, and focused on outcomes rather than activity.
That's the thinking behind ZenKaizen.
ZenKaizen gives organizations a structured way to manage improvement ideas through evaluation, PDCA, implementation and outcome verification — helping make improvement consistent across a site.
Because the goal isn't to create the perfect improvement program. It's to make improvement part of how the organization operates.
Perfection may remain out of reach. But the pursuit of it can produce something very real:
Excellence, one improvement at a time.