The Steady Churn of the Deli Counter
I spent an hour last week waiting at the deli counter, a place I normally find frustrating. But this time, trapped by the promise of good ham, I was forced to observe. And in that observation, I found a strange, brutal kind of productivity wisdom. It wasn't in the fancy meat slicer, but in the butcher himself. His work was a masterclass in what I’ve come to call the 'single-queue, single-server' model.
You see, he had one job: serve the line. There was no multitasking. He didn't answer the phone. He didn't restock the shelves while someone pondered the difference between Black Forest and Virginia baked. He stood at his station, took a ticket, acknowledged the person, fulfilled the order, and moved to the next. The entire system was built around this uninterrupted flow. The customer takes a number, accepting their place in the queue. The server processes one ticket at a time, start to finish. The clarity is absolute.
Contrast this with our own digital workspace. We are the butcher, the ticket dispenser, and the anxious customer all at once. We have multiple queues—email, Slack, project management tabs—and we are constantly context-switching between them. We are 'serving' a message while simultaneously 'taking a ticket' from a notification, and internally 'waiting in line' for our own deep work to get attention. It’s a chaotic, multi-server environment where nothing gets the undivided attention it needs.
The butcher’s method imposes a powerful constraint: you can only do one thing at a time, so the system must be designed to accommodate that truth. Our mistake is building workflows that pretend we can do ten things at once. The deli counter doesn't pretend. It is honest about its limitations, and in doing so, becomes incredibly efficient. The slow, steady rhythm isn't a sign of laziness; it’s the sound of sustainable throughput.
The Ticket in Your Pocket
So, how do we borrow this? We need our own ticket system. This isn't about a fancy app; it’s about the principle. For me, it’s a small notepad. When an interrupt comes in—an email that needs a long reply, a request from a colleague—I don't jump to it. I write it down on the next available line. This is my ticket. It now has a number. My primary task—the 'customer' I am currently serving—gets my full attention until it is complete or reaches a natural stopping point. Only then do I pull the next ticket from the pad.
The goal is to stop being an open counter where anyone can shout an order. It’s to become a system with a clear, fair, and orderly process. The relief is immediate. The anxiety of the infinite to-do list fades because the list is no longer a chaotic swarm of demands; it’s a linear queue. You are not responsible for everything at once, only for the single ticket in front of you. The others will wait their turn, just like at the deli.
It feels slow at first, this deliberate processing. You’ll feel the urge to skip the line for a 'quick' task. Resist it. The integrity of the entire system depends on honoring the queue. The payoff is not just in the work you complete, but in the immense mental quiet that comes from knowing exactly what you're doing, and more importantly, what you're not doing. It’s the quiet focus of a professional who knows the value of a steady, unbroken rhythm.
Notes & further reading
A few pages I came back to while writing this: