Losing luggage almost feels like one of those unavoidable risks of flying.
Think about everything that has to happen correctly.
A bag is checked in, labeled, transported through an airport, sorted, loaded onto the correct aircraft, unloaded at the destination, transported again, and ultimately delivered to the right baggage carousel.
Now repeat that process thousands upon thousands of times.
With that many handoffs and opportunities for error, occasionally losing a bag seems almost inevitable.
But one airport has achieved something remarkable.
Kansai International Airport in Japan opened in 1994 and has been widely recognized for an extraordinary baggage-handling record: no passenger luggage lost due to the airport’s own handling operations over its first 30 years.
How does an organization achieve that level of consistency?
The answer provides a powerful lesson in continuous improvement.
Extraordinary Results Often Come From Ordinary Processes
When we encounter an extraordinary result, we tend to assume there must be an equally extraordinary explanation.
Maybe there is groundbreaking technology.
Maybe someone developed a revolutionary new system.
Maybe the organization has resources no one else has.
But excellence often comes from something far less glamorous:
Doing the basics exceptionally well.
That is one of the central ideas behind continuous improvement.
Organizations don’t necessarily become exceptional through one giant breakthrough. They improve through countless small actions that make processes safer, simpler, more reliable, and more consistent.
In baggage handling, seemingly small disciplines such as checking, verifying, communicating, and following standards can have enormous consequences when they are repeated consistently.
Check. Verify. Communicate. Standardize. Improve. Repeat.
Nothing on that list sounds revolutionary.
The results can be.
Don’t Tell People to Be More Careful. Improve the Process.
When a mistake happens in an organization, one of the easiest responses is:
“We need to be more careful.”
And then everyone moves on.
Until the mistake happens again.
Continuous improvement asks us to approach the problem differently.
Instead of only asking:
Who made the mistake?
Ask:
What about the process allowed the mistake to happen?
Could the error have been detected earlier?
Could another check have prevented it?
Could information have been clearer?
Could the process make the correct action easier?
Could we make the mistake difficult, or even impossible, to make?
Now we’re no longer simply asking people to try harder.
We’re improving the system in which they work.
That’s an enormously important distinction.
Design Quality Into the Process
This concept is closely related to quality at the source.
The goal isn’t simply to inspect quality at the end of a process and discover what went wrong.
Ideally, we want to detect problems as close as possible to where they occur and, whenever possible, prevent them from happening in the first place.
Lean practitioners often refer to this concept as poka-yoke, or error proofing.
The underlying question is simple:
How can we design this process so the mistake is less likely to happen?
Think about your own organization.
Where are employees expected to remember something important every single time?
Where does the process depend on someone noticing a small detail?
Where can information easily be misunderstood?
Where does an error pass through several steps before anyone discovers it?
Those are opportunities for improvement.
Standard Work Doesn’t Mean “Never Change”
There’s another lesson here that often gets misunderstood.
Standardization and continuous improvement aren’t opposites.
Standard work establishes a consistent way to perform a process based on the best-known method at that point in time.
Then we learn.
Someone discovers an easier way.
A problem exposes a weakness.
A team develops a better check.
Customer expectations change.
The process improves.
That improvement can then become part of the new standard.
So the cycle becomes:
Create a standard → Follow it → Learn → Improve it → Create a better standard
And then repeat.
Standard work creates the foundation that makes improvement possible.
Without a standard, it can be difficult even to determine whether a change actually made the process better.
Reliability Is Built One Small Action at a Time
Perhaps that’s what makes the Kansai International Airport story so compelling.
Thirty years is a long time.
Organizations change.
Employees change.
Technology changes.
Customers change.
Workload changes.
Yet operational excellence depends on processes continuing to produce reliable outcomes despite all that change.
And this is where the lesson extends far beyond airports.
You might work in a hospital.
A veterinary practice.
A warehouse.
A manufacturing facility.
A restaurant.
A call center.
A school.
Or an office.
You probably aren’t responsible for getting thousands of suitcases onto the correct airplanes.
But you do have processes where errors matter.
Appointments need to be scheduled correctly.
Medications need to go to the right patient.
Orders need to reach the right customer.
Invoices need to contain accurate information.
Requests need to reach the right person.
Projects need to move from one step to another.
Customers need to receive what they were promised.
In every one of those situations, we have a choice.
We can hope people don’t make mistakes.
Or we can continually improve the process so that mistakes become less likely.
Stop Looking for Heroes
There’s also a leadership lesson hidden in this story.
Organizations sometimes build processes that depend on exceptional people constantly saving the day.
Someone remembers the detail everyone else forgot.
Someone stays late to correct an error.
Someone catches the problem seconds before it reaches the customer.
Those people deserve appreciation.
But heroics shouldn’t be the operating model.
A great process should help ordinary people produce extraordinary consistency.
When employees repeatedly have to rescue a broken process, the answer isn’t always to find more heroic employees.
Sometimes the answer is to fix the process.
That’s one of the most powerful shifts leaders can make:
From:
“How do we get people to perform better?”
To:
“How do we create a process that helps people succeed?”
Excellence Eventually Becomes “Just How We Work”
The ultimate goal of continuous improvement isn’t to run an improvement project every few months.
It’s to create a culture where improvement becomes part of everyday work.
Problems become opportunities to learn.
Employees feel comfortable pointing out weaknesses.
Standards evolve when better methods are discovered.
Mistakes trigger curiosity rather than blame.
Teams don’t simply work around broken processes. They improve them.
Eventually, behaviors that once required extraordinary effort simply become:
“The way we do things here.”
And that’s when continuous improvement becomes much more than a collection of Lean or Six Sigma tools.
It becomes culture.
The Real Lesson From Kansai
The story of Kansai International Airport is impressive because the result seems extraordinary.
But perhaps the more useful lesson is how we think about achieving extraordinary performance.
Operational excellence doesn’t always require a revolutionary idea.
Sometimes it starts with a simple question:
How could we make this process just a little more reliable?
Then you make the improvement.
You standardize it.
You learn from it.
And tomorrow, you ask the question again.
One small improvement may not seem significant.
But repeat that thinking across hundreds of processes, thousands of decisions, and years of work, and small improvements begin to compound.
Eventually, the result may look extraordinary from the outside.
But inside the organization?
It’s simply how the work gets done.
That’s continuous improvement.
Want to learn more about continuous improvement? Take our online Standard Continuous Improvement Certification course.