Every organization has an official process and a real one. The official process lives in documentation. The real one lives in queues.
Watch where work waits and you understand the system. A task sitting in someone’s inbox for three days isn’t a people problem — it’s a queue problem. The bottleneck has a location. It’s measurable. It’s usually obvious once you stop looking at the flowchart and start looking at the pile.
Good process design is mostly queue management. Where does work accumulate? Who touches it, and how many times? What decisions are made at each handoff, and are those decisions necessary or just habitual?
The organizations that move fast aren’t staffed differently. They’ve reduced unnecessary queue depth. Work enters, gets acted on, moves forward. When something stalls, there’s a clear reason — not ambient friction from a process no one audited in five years.
Scott Andrew Alpaugh has observed this in a dozen operational contexts: the teams that complain about being overwhelmed are almost never under-resourced. They’re under-organized. The work is circling instead of flowing.
Fix the queue before you hire. Map where things pile up before you add another tool. Most “we need more capacity” problems are actually “we have too many handoffs” problems in disguise.
The queue doesn’t lie. Everything else might.