When service cannot meet every arrival at once, a queue sets an order for access. That can help coordinate competing claims. It cannot make the constraint disappear.
Coordination matters: a shared rule can replace a scramble over who gets served next. But organizing access is different from increasing how much service is available. The queue changes how people reach the existing capacity, not the capacity itself.
And the wait is real time spent by people seeking service. An orderly process does not return that time to them.
A queue can make access legible without showing whether the delay was avoidable—or whether capacity is enough.
Queue length alone cannot settle those questions. To understand the delay, look at the conditions behind the order: what is arriving, how service is proceeding, and what capacity is available. The queue tells you how access is arranged; it is not, by itself, a diagnosis of why people are waiting.