The Gap Wasn’t Hidden–It Was Ignored | Observations from the Shop Floor
Michael Gardner, COO
One of the most misunderstood concepts in business is the idea of a gap analysis.
The phrase sounds technical, as though it belongs in a consulting engagement, a strategic planning session, or the early stages of a software implementation. Yet after spending years in warehouses, manufacturing facilities, accounting departments, and conference rooms, I’ve come to believe that most operational gaps are neither hidden nor difficult to find.
In fact, someone usually knows exactly where they are.
- The warehouse supervisor knows.
- The customer service representative knows.
- The accounts payable clerk knows.
- The production scheduler knows.
The people closest to the work often experience the gap every single day.
The challenge is that organizations gradually become accustomed to working around problems. What begins as a temporary adjustment slowly becomes part of the routine. An extra spreadsheet gets created. A manual verification step gets added. Someone sends a daily email because they don’t fully trust the information in the system.
Over time, nobody remembers when the workaround started.
They only remember that it exists.
Eventually, the workaround becomes the process.
One of the most valuable lessons I learned early in my career was that the most important part of a discovery meeting was rarely the software demonstration or the requirements document. It was listening.
Not listening for what people wanted.
Listening for what frustrated them.
Listening for the moment someone says:
“What we usually do is…”
I’ve learned that those five words often reveal more about an operation than hours of formal process discussions. What follows is usually a workaround, and workarounds are clues. They are breadcrumbs that lead directly to operational gaps.
I have watched organizations spend hundreds of thousands of dollars implementing new technology while preserving the very process that created the problem in the first place. The software changed. The screens looked different. Reports were redesigned.
The gap remained.
The reason is surprisingly simple. The conversation focused on the symptom instead of the cause.
The question became:
“How do we make this process faster?”
Instead of:
“Why does this process exist at all?”
Those are very different conversations.
One assumes the process is necessary and seeks efficiency. The other challenges whether the process should exist in its current form in the first place. Meaningful improvement often begins with the second question.
What makes these gaps particularly dangerous is that they rarely announce themselves as major problems. Most of them arrive quietly.
It may be nothing more than a few extra minutes spent reconciling information, a spreadsheet maintained outside the system, a report that gets checked twice, or an email chain that exists because people have learned to trust one another more than they trust the process. Individually, these activities seem harmless. Collectively, they consume time, attention, and confidence. Because they develop gradually, they often become invisible to the people experiencing them.
The organizations that improve the fastest tend to share a common characteristic: they are curious.
When someone points out a weakness, they don’t become defensive. They become interested. They understand that discovering a gap is not criticism; it is an opportunity to learn something about how the business actually operates.
Many operational improvements begin with a simple question:
“Help me understand why we do it this way.”
That question has uncovered more opportunities than any software demonstration I’ve ever conducted.
The irony is that many organizations spend considerable time searching for solutions while spending very little time listening for problems. Yet the people closest to the work usually know where the friction exists. They know which reports are exported to spreadsheets. They know which numbers get checked twice. They know which processes require someone to intervene before things move forward.
The challenge is rarely gathering the information. It is creating an environment where people believe someone is genuinely interested in hearing it.
After years on shop floors, in warehouses, accounting offices, and conference rooms, I’ve come to a simple conclusion: the people closest to the work usually know exactly where the friction exists.
Once you start listening, the gaps become easy to find.
The difficult part is deciding that the workaround is no longer acceptable.
Final Observation
Most operational gaps are not hidden. They are discussed in hallways, mentioned in meetings, and worked around every day. The spreadsheet, the manual check, the extra phone call, the daily email—all started as temporary solutions.
Over time, they became accepted parts of the operation as the workaround became the process.
The organizations that improve the fastest are not necessarily the ones with the best technology. They are the ones that listen when someone says, “We’ve always had to work around that.” Because that sentence is rarely describing the solution… it’s usually describing the problem.