A queue is a line where jobs wait their turn. In software, a job might be “send this email” or “process this transcript”: the system puts it in the queue, and a worker picks it up, handles it, and moves to the next. The line keeps the system from getting overwhelmed when everything arrives at once. Queues pair naturally with automation and cron and scheduling: a scheduled job drops work into the queue instead of firing every send at once.
A front desk with a stack of intake forms shows the shape. Five people walk in at once. The clerk doesn’t throw away four forms because they can’t process all five instantly. They put them in order and work through them one at a time.
Why you care
In client work, “do this later” can be the correct design, as long as the job is captured, ordered, and visible. Work that disappears into someone’s head is a leak. A good workflow has queues at its handoff points: waiting on review, on client response, on data. Naming those queues shows where things pile up.