Where Should the Pack Table Go?

Years ago, I heard a facility manager dismiss Six Sigma and Continuous Improvement as a sham.

His example:

At his warehouse, the pack stations had been rearranged over and over again across the years. The pack table moved from one side of the work area to another…9 o’clock, 12, 3, 6…and eventually right back where it started.

His conclusion:
“All that Lean effort just ended up exactly where we began.”

But my first question was:
Did it?

The layout may have looked the same. The operation probably wasn’t.

The workforce changes.
The product mix changes.
Volumes change.
Customer expectations change.

A healthy operation adapts constantly, even if some solutions eventually cycle back around.

That’s the part people miss about continuous improvement:
it isn’t a one-time event or a quarterly initiative. It’s a culture.

At its core, it really comes down to three things:

Teams that feel empowered to identify problems and suggest changes
A disciplined process to evaluate and implement improvements
Reliable measurement to determine whether the changes actually worked

Simple in theory.

Very difficult in practice.

Continuous Improvement Is Not an Event

A few weeks ago, while touring a large 3PL warehouse near my home, the site leader proudly told me they require one continuous improvement event per quarter.

What struck me was that someone at his relatively senior level viewed continuous improvement as an event…a one-time thing…a task performed on a regular basis, instead of something every person should be doing every single day.

It reminded me of a story from World War II. Eisenhower was once quoted as saying:

“I don’t know what the hell this ‘logistics’ is that Marshall is always talking about, but I want some of it.”

A surprising number of senior leaders seem to have the same surface-level understanding of continuous improvement. They know a few buzzwords, and they know they’re supposed to do this thing, but the deeper philosophy is missing.

I imagine the reason a quarterly requirement exists is because it’s easy to measure. You can check the box, show that you completed it, and create a visible display of action.

In fact, I’ve been in meetings where someone mentioned an idea for a CI initiative, and someone interrupts:

“Wait, didn’t we just do one last month?”

I’ve always said this is the equivalent of going to the dentist twice a year…and that’s it. No brushing. No flossing. Your oral health box was already checked off last September.

True, lasting continuous improvement starts at the lowest level. It comes from individuals making small, incremental improvements to their jobs every single day.

Tiny 1% improvements that, over time, compound into something far more impactful than any quarterly event ever could.

The challenge is that those improvements are much harder to individually measure.

The organizations that truly embrace continuous improvement are not the ones that schedule it once a quarter. They are the ones that build cultures where people are expected, empowered, and encouraged to improve something every single day.

Continuous improvement is not an event.

It’s a mindset, a culture, and a daily habit.

A Scalable Process Doesn’t Depend on Heroes

What does it mean to say a process is scalable?

It’s simple.

It’s repeatable.

It doesn’t rely on Jim. Or Joe. Or Bob. Or any individual to be on shift that day.

A lot of operations look stable at smaller scale because experienced people are compensating for weak processes in real time. They know the shortcuts. They know the workarounds. They know where the problems usually happen.

But once volume increases, complexity increases, or new people enter the system, those gaps become much more visible.

That’s when organizations start confusing growth problems with operational maturity problems.

If performance depends heavily on individual heroics, the process probably isn’t scalable yet.

Small Frictions Become Big Operational Problems

One of my favorite CI projects was also one of the smallest.

A few extra seconds per transaction doesn’t sound meaningful…until it scales across an entire operation.

Lots of Continuous Improvement projects are ambitious. Some require massive investment in new tools, equipment, or warehouse reconfiguration. In fact, some leaders are convinced that all improvement needs to be on a grand scale. But my favorite CI project I’ve ever led centered around something incredibly small: one extra data entry.

At the time, I was leading a receiving operation with roughly 20 employees handling grocery inventory. Receivers would scan incoming product, stow it directly to shelf locations, and manually enter expiration dates into handheld scanners as part of the receiving transaction.

The process itself made sense. The system had expected shelf-life ranges configured by product type. If an employee entered a date outside the acceptable range, the system would prompt for a second entry as verification. That safeguard was designed to catch mistakes before inventory hit the floor.

The problem was that the product characteristic tables…the part of the code these entries would reference…was wrong. The data was bad. For most products, it was set to 1 day. A can of soup? One day. A gallon of milk? One day. So instead of prompting for re-entry only on exceptions, the system was requiring a second date entry for every single item received.

At first glance, it didn’t seem catastrophic. Nobody was stopping production. No alarms were going off. The operation continued moving.

But after spending time on the floor, it became obvious that the extra step was creating constant friction in some of the highest-frequency transactions in the building.

That observation led to a simple question:

“What is this actually costing us?”

Quantifying the Problem

The receiving team averaged roughly:

20 employees
7.5 working hours per shift
~120 units per hour per employee

That translated to approximately 18,000 units processed daily.

We estimated the unnecessary second date entry added about 2.5 seconds per item. Again, individually, almost nothing.

At scale:

18,000 units/day × 2.5 extra seconds
= 45,000 lost seconds daily
= ~12.5 labor hours per day

That equated to:

roughly 8% productivity loss
or nearly 2 full-time employees worth of capacity consumed by a software defect

Not because employees were underperforming. Not because the process design was poor. Simply because a small system issue had embedded itself into a high-volume workflow.

The Bigger Lesson

This experience reinforced something that applies far beyond warehouse operations:

Small inefficiencies become massive when attached to high-frequency work.

Most operations do not collapse because of dramatic failures. They erode through thousands of tiny interruptions:

extra clicks
duplicate entries
unnecessary approvals
avoidable motion
systems that force people to work around them

Individually, these seem trivial. Collectively, they quietly consume labor, attention, and throughput every day. They are waste.

Why Direct Observation Matters

What made this issue visible was not a dashboard or KPI report.

It started with direct observation on the floor. Watching the work happen in real time. Listening to operator frustration. Looking for moments where the process felt slower, heavier, or more repetitive than it should.

That is one of the most overlooked parts of continuous improvement.

You cannot improve work you do not truly understand.

The Outcome

Once the issue was quantified, it became much easier to prioritize and partner cross-functionally on a resolution. The discussion shifted from anecdotal frustration to measurable operational impact.

Fixing the defect effectively returned more than 12 labor hours of productive capacity back to the operation each day without adding headcount.

All from removing a few unnecessary seconds from a transaction repeated thousands of times daily.

At scale, small frictions stop being small.

Why Good Systems Don’t Rely on Reminders

I’ve owned the same food processor for decades. It has moved all over the world with me.

The main blade is sharp. Extremely sharp. Combined with the speed and power of the motor, it could easily be dangerous.

But the engineers assumed people would make mistakes. The blade won’t spin unless the bowl is locked into place and the lid is fully attached. Even the ingredient chute has a tall, narrow insert so you can add liquid while the machine is running but still can’t reach the blade.

It’s a layered safety system.

The earliest food processors didn’t have these features. Over time, through redesign and continuous improvement, the safeguards were engineered into the product.

Managers facing gaps in their processes often respond with “We’ll brief the team,” or “We’ll add more signage.”

These are short-term fixes.

Band-aids.

The manufacturer of my food processor could have added more warning labels. They could have put a larger warning in bolder font in the owner’s manual.

Instead, they redesigned the machine.

Real operational improvements work the same way.

The best processes aren’t protected by reminders.

The best processes are protected by layered systems.

Where in your operation are you relying on reminders instead of redesign?

Look Out for Irving

This story comes from an old This American Life episode.

In 1970, the Vienna Sausage Company of Chicago moved production from its 19th-century factory into a brand-new, state-of-the-art modern plant. They used the same ingredients. The same recipe. And yet the hot dogs did not taste right.

The color was off.
The texture lacked their signature snap.

Maybe the water on the south side of Chicago was different from the north side. Maybe the temperature in the new smokehouse was wrong. The company searched for over a year and a half without finding the cause.

Finally, during a casual conversation over a few beers at a local bar, someone remembered an old employee named Irving.

At the original factory, Irving’s job was to push a wooden cart around the plant, collecting sausages from different workstations. On his way to the smokehouse, he passed through warmer parts of the building, effectively giving the sausages a long pre-heat before smoking.

In the new modern plant, there was no Irving.

The layout was different. That warming step disappeared. The sausages went straight to the smokehouse cold. The result was different flavor and different color.

To fix the problem, the company eventually built an extra room to replicate Irving’s walk. Once the sausages warmed the same way, the product tasted right again.

The original factory and Irving’s walk were the product of evolution.

Many companies, from startups to long-established organizations, develop processes the same way. Incrementally, through feedback and learning over time. The challenge comes when we try to document, improve, or scale those processes.

When mapping out a value stream, the core question is simple. Where is value created, and where is time wasted?

On the surface, Irving’s walk looks like waste. And that is exactly what happened. It was eliminated.

But Irving’s walk was not waste.
It was essential value.

As companies grow and move workflows to new locations, the real challenge is not eliminating steps. It is knowing which steps matter.

So the question for any Lean effort is this:
What other Irvings are lurking out there?

This American Life. “20 Acts in 60 Minutes.” Episode 241, Act Fourteen. Produced by Chicago Public Media. Originally aired January 17, 2003.