There's a silent killer in your process. It doesn't show up on org charts. It's invisible in most metrics. It costs more than your most expensive resource.
It's waiting time.
And it's probably consuming 80% of your lead time while you obsess over the other 20%.
The Uncomfortable Reality
Ask most managers where time goes in their process, and they'll point to activities: processing, assembly, review, testing. They're focused on doing.
But track actual items through a real process and you'll find something disturbing:
| Where Time Goes | Typical Process | What Gets Measured | |-----------------|-----------------|-------------------| | Queue time (waiting) | 70-90% | ❌ Ignored | | Process time (working) | 10-30% | ✅ Obsessed over |
We measure and optimize the minority. We ignore the majority.
Why Queues Hide
Queues are invisible because:
- No one "owns" queue time. Work sitting between departments? No one's responsibility.
- It looks like inventory. Emails in an inbox, tickets in a backlog, parts in staging — it seems normal.
- Process maps ignore it. We draw activities, not the waits between them.
- Systems don't track it. Start time and end time, yes. Time sitting? Never.
The result: massive waste that no one sees and no one addresses.
The Real Cost of Waiting
Waiting isn't free. Every hour an item sits in a queue:
Direct costs:
- Space to store work-in-progress
- Inventory carrying costs
- Cash tied up in undelivered value
Indirect costs:
- Customer patience eroding
- Obsolescence risk increasing
- Defects becoming harder to trace
- Priority changes making work irrelevant
Hidden costs:
- Expediting and firefighting (because normal queue times are too long)
- Customer follow-ups asking for status
- Duplicate work when requesters give up and start over
Little's Law: The Queue Truth-Teller
There's a simple formula that governs all queues:
Lead Time = Work in Progress / Throughput
Or rearranged: WIP = Lead Time × Throughput
This means:
- More WIP → Longer lead times
- Reduce WIP → Lead times shrink
- It's mathematical, not optional
Want to cut lead time in half? Cut WIP in half. The queue will drain faster because there's less stuff competing for attention.
Where Queues Come From
Queues form when arrival rate exceeds processing rate — even temporarily. But they also form from:
Batch handoffs: "I'll send these 20 when they're all done" creates instant queue.
Priority thrashing: Constant reprioritization means nothing flows smoothly.
Unbalanced capacity: Fast upstream + slow downstream = growing pile.
Policies: "We review on Tuesdays" means 6 days of waiting built in.
Variability: Unpredictable arrivals and processing times cause queues even when averages seem fine.
That last point is crucial. A process with balanced averages but high variability will still have queues. This is why simulation matters — spreadsheets can't capture variability effects.
The Psychology Problem
Here's why queues persist: working on items feels productive, reducing queues doesn't.
A manager sees two scenarios:
Scenario A: Team processes 100 items, queue grows by 20
Scenario B: Team processes 80 items, queue shrinks by 10
Scenario A looks more productive. Scenario B is actually better for the system. But who gets praised? The team that processed more — even though they made the overall problem worse.
Five Queue-Busting Strategies
1. Make queues visible. Literally. Post WIP counts. Show waiting items. What's invisible can't be fixed.
2. Implement WIP limits. Cap how much can be in progress. When you hit the limit, finish something before starting something new.
3. Attack handoffs. Every handoff creates a queue opportunity. Eliminate handoffs where possible. When necessary, make them instant (no batching).
4. Level the flow. Don't dump work in batches. Smooth arrivals throughout the day/week.
5. Balance capacity. Resources after your bottleneck? They should never starve. Add buffer before the bottleneck if needed.
The Queue Walk
Here's an exercise: follow one item through your process. Not the fastest item — an average one.
Time stamp:
- When was it requested?
- When did active work begin?
- Every hand-off, when did it arrive? When did work resume?
- When was it delivered?
Now calculate: what percentage was active work versus waiting?
Most people doing this exercise for the first time are shocked. "We spent 3 minutes on this. It took 3 days?"
Yes. And now you know where to focus.
The Mindset Shift
Stop asking: "How do we process items faster?"
Start asking: "How do we eliminate the waiting between processes?"
The first question optimizes 20% of your lead time. The second question attacks the other 80%.
Today's Action: Find the biggest queue in your process. How many items are sitting there right now? How long do they typically wait? That queue time multiplied by volume is your improvement opportunity. Start tracking it.
Queues are hard to see but easy to simulate. ProcessModel visualizes every queue in your process, calculates wait times automatically, and helps you test queue-reduction strategies before implementing them.