Zero backlog isn't good news

I've walked a lot of buildings where a department lead proudly points at an empty staging lane. "We're fully caught up." Everyone nods. It feels like winning.

It usually isn't. An empty queue means the team downstream of it has nothing guaranteed to work on tomorrow. One hiccup upstream — a late trailer, a system outage, a call-out-heavy Monday — and that department is standing around on payroll. Backlog is a buffer, and buffers exist for a reason. The goal was never zero. The goal is controlled.

Backlog has two failure modes, and they cost you in opposite directions. Too much, and you're drowning: SLAs slip, overtime climbs until you're weighing it against adding a head, and leadership starts managing by walking toward whatever pile looks scariest. Too little, and you're starving: labor idles, throughput gets fragile, and every upstream wobble hits the customer directly. A building that swings between the two — buried one month, empty the next — has the worst of both, because nobody can staff or plan against a number that won't hold still.

The fix isn't a motivational push to "catch up." It's a range. Every department should have a backlog floor and a ceiling — enough work banked to keep tomorrow safe, not so much that commitments slip. Staff to hold the range, not to chase zero. When a department breaches its range, that's not a crisis; that's your operation telling you where the constraint moved. In one operation I ran, department backlogs swung anywhere from zero to 25 weeks before we built throughput targets that made the whole building visible — and stabilized between two and eight weeks after. The stability was worth more than any single week's heroics.

So this week, ask each department lead two questions. How much backlog do you have right now, in hours or days of work? And what should it be? If the second question gets a blank stare, you don't have a catching-up problem. You have a visibility problem — and it's fixable. Finding and fixing that kind of gap is most of what an operations consultant actually does.