Where Operational Waste Hides: A Field Guide for Growing Companies

The Approval Queue

The first hiding place is sequential approval. A request that touches three departments waits in three queues, and the elapsed time is the sum of everyone's 'when I get to it'. Nobody is idle; the organization is simply serial where it could be parallel.

Mapping where requests actually wait — not where the policy says they should be, but where they sit — is often the most revealing exercise in an operational review. The fix is rarely removing control; it is designing control that runs alongside the work instead of after it.

Duplication That Growth Created

Growing companies layer systems without retiring old ones. The new inventory tool coexists with the spreadsheet it was meant to replace; the regional office keeps its own customer list because the central one 'does not show what we need'. Every duplicate record is a small, permanent tax: entered twice, reconciled twice, disputed eventually.

The tell-tale sign is reconciliation work. Wherever staff spend real hours making two systems agree, the organization is paying for its duplication with its most expensive resource — capable people doing work that creates no value for the customer.

The Cost of Workarounds

Workarounds are a gift of information disguised as an irritation. The side-log the team keeps because the official system is clumsy, the messaging group that actually coordinates deliveries, the supervisor who personally remembers which clients need special handling — each is the organization telling you where its formal process fails.

Treat workarounds as free consulting. The question is never 'how do we stop this?' but 'what does this know that our process does not — and why does the process not know it?'

Measure Before You Redesign

Operational redesign without measurement is opinion with a budget. Before changing anything, watch the actual flow of work: where it waits, where it bounces back, who checks whose work and why. Simple counts — requests received, elapsed days per stage, rework loops — are enough to turn an argument about effort into a conversation about evidence.

In our process reviews, the moment the numbers are laid on the table, the debate changes character. Departments stop defending territory and start solving the shared problem, because the problem finally has a name and a place.

Small Fixes, Compounding Returns

The drama of operational efficiency is that its biggest wins rarely look dramatic: one approval moved from sequential to parallel, one duplicate report retired, one workaround promoted into the official process. Each change returns hours to the week. Compounded across teams and months, they are the difference between an organization that grows by hiring more coordinators and one that grows by doing fewer useless things.