This is the fifth installment in my Service Management learning series. This time, we dive into operations design.
The case study in class featured a small, popular restaurant in a prime urban location. Just 44 seats. On weekend mornings, hour-long lines are the norm. And yet, repeat customers keep coming back.
Why would people wait an hour just to eat here? The answer lies in the “psychology of queues.”
- 1 This Restaurant’s “Design by Elimination”
- 2 The Psychology of Queues — 8 Principles
- 2.1 ① Unoccupied time feels longer than occupied time
- 2.2 ② Anxiety makes waits feel longer
- 2.3 ③ People are more patient when waiting for something valuable
- 2.4 ④ Unfair waits generate anger
- 2.5 ⑤ Pre-service waits feel longer than in-service waits
- 2.6 ⑥ Unexplained waits feel longer
- 2.7 ⑦ Solo waits feel longer than group waits
- 2.8 ⑧ Physically uncomfortable waits feel longer
- 3 How This Restaurant Eliminated “Waiting Stress”
- 4 Perceived Wait Time vs. Actual Wait Time
- 5 The Brilliance of the “No Seating Until You Have Your Food” Rule
- 6 The Real Source of Dissatisfaction Is “Uncertainty”
- 7 Recommended Reading to Deepen This Session’s Learning
- 8 Next Time
This Restaurant’s “Design by Elimination”
First, the restaurant’s service design is distinctive in what it chooses NOT to offer.
- No seating until you’ve received your food (cafeteria style)
- All communal seating — no private, spacious dining
- No table service — customers line up at the register and carry their own food
- Open kitchen where the entire cooking process is visible
Full-service hospitality, comfortable ambiance, privacy — this restaurant has deliberately discarded many of the values a typical restaurant provides.
Instead, it focuses intensely on one proposition: “High-quality, handmade food at an incredibly affordable price, in a prime location.” Rather than trying to appeal to everyone, it breaks through with a specific value. In the context of the Service-Profit Chain (SPC) we studied previously, this is a textbook example of deliberately designing along the value line.
This “design by elimination” is actually a familiar concept in the IT world. In microservices architecture, each service focuses on “doing one thing well.” A service with a narrow, focused scope ultimately delivers more value than a monolithic system that tries to do everything. This restaurant is essentially the embodiment of microservices thinking applied to service design.
The Psychology of Queues — 8 Principles
The most striking part of the lecture was the psychology of queues. There are eight principles governing how people perceive the act of waiting. These principles, proposed by David Maister, form the foundation of service design.
① Unoccupied time feels longer than occupied time
Simply standing and waiting feels longer than it actually is. Time passes faster when you’re doing something. That’s why waiting rooms have magazines and restaurants show menus to people in line. Theme parks place decorations and mini-games in queue areas for the same reason. Some theme parks show a prologue to the attraction’s story during the wait, transforming wait time itself into part of the experience.
② Anxiety makes waits feel longer
“Not knowing when it will end” causes the most stress. When hospital waiting rooms don’t display queue numbers, when you want to ask a restaurant “How many groups ahead of me?” — uncertainty amplifies the stress of waiting. More hospitals now use number display screens, and that alone significantly reduces patients’ perceived wait time.
③ People are more patient when waiting for something valuable
If you think “This food is worth waiting for,” the same one-hour wait feels less painful. What matters is the perception that something of high value awaits at the end. People lining up at a famous ramen shop already carry the expectation that “this ramen is worth the wait.”
④ Unfair waits generate anger
“That person arrived after me but got seated first” — queue-cutting and opaque rules generate frustration that exceeds the wait time itself. A simple first-come-first-served rule ensures fairness. Banks shifted to single-line queuing because having separate lines per counter created the stress of “the other line is moving faster.”
⑤ Pre-service waits feel longer than in-service waits
Waiting 15 minutes before placing your order versus 15 minutes after ordering — the psychological weight is completely different. After ordering, there’s a sense of reassurance that “the process has started.” That’s why excellent restaurants bring water the moment you sit down and immediately explain the menu. The signal that “your service has begun” is crucial. The same logic applies to progress bars on app loading screens — just displaying “Processing…” helps users perceive that things have started.
⑥ Unexplained waits feel longer
Simply knowing WHY you’re waiting increases acceptance. When a train delay is announced as “due to a signal malfunction,” passengers feel less irritated than with an unexplained delay. People are creatures who want to know “why.” A wait without explanation creates a feeling of being ignored.
⑦ Solo waits feel longer than group waits
Waiting in a group passes time through conversation, but waiting alone feels subjectively longer. Disney’s “single rider” lines serve partly to improve the solo waiting experience. Similarly, designing waiting room seating layouts that encourage interaction is based on this principle.
⑧ Physically uncomfortable waits feel longer
Waiting standing in the heat versus sitting in an air-conditioned room — the same 30 minutes feels completely different. Physical discomfort directly amplifies waiting stress. Comfortable chairs and proper climate control in hospital waiting rooms aren’t just amenities — they’re wait experience management.
How This Restaurant Eliminated “Waiting Stress”
The restaurant masterfully addressed the psychology of queues.
Eliminating “idle waiting”: Drinks are served at the end of the line. The open kitchen lets you watch the chefs’ craft. Wait time becomes entertainment. This addresses both Principle ① and ⑦ — holding a drink gives you “something to do” and also creates a conversation starter with the person next to you.
Eliminating “uncertainty”: A clear first-come-first-served rule. The cafeteria format lets you see your own progress. You naturally understand “how much longer.” This simultaneously resolves Principles ② and ⑥.
Eliminating “perceived unfairness”: No reservations — everyone follows the same rules. No VIP treatment, no special treatment for regulars. You eat in the order you lined up. This addresses Principle ④.
Elevating “value expectation”: The open kitchen builds anticipation — “this must be delicious.” Furthermore, the “effort” of standing in line and following the rules psychologically increases the perceived value of the reward. This is close to what behavioral economics calls the “IKEA effect” — the tendency to overvalue things you’ve invested effort in.
Perceived Wait Time vs. Actual Wait Time
The most important insight from queue psychology is this: what customers take issue with is not the “actual wait time” but the “perceived wait time.”
Psychology research shows that wait time with nothing to do is perceived as 1.3 to 1.5 times the actual duration. Conversely, with the right design, you can make waits feel shorter than they actually are.
This means there are two approaches to improving operations: reducing actual wait time (process improvement) and reducing perceived wait time (psychological design). The former involves engineering approaches like capacity expansion and bottleneck elimination. The latter is the queue psychology we studied this time.
What’s fascinating is that the latter is often far more cost-effective. Installing monitors in a theme park queue costs a fraction of building another ride. Adding a skeleton screen (placeholder layout) to an app loading page significantly reduces user drop-off — even though actual processing speed hasn’t changed at all.
The Brilliance of the “No Seating Until You Have Your Food” Rule
What personally impressed me most was the “no seating until you’ve received your food” rule. At first glance, it seems unfriendly. But this rule has profound operational rationale.
If customers could claim seats first, you’d get a state where “a seat is occupied but no food has been served.” Seats filled with no food being consumed — this is a resource deadlock. Kitchen production capacity and seat turnover fall out of sync, and throughput drops.
The “no seating” rule synchronizes the kitchen’s 40-second cooking cycle with the average 19-minute seat occupancy. Only people with food sit down, so every seat stays in an “actively dining” state. Zero waste.
In IT terms, this is a resource mutual exclusion and scheduling problem. The “no seating” rule optimizes the lock granularity for the seat resource.
Digging deeper, this rule eliminates one of the four conditions for deadlock prevention: “Hold and Wait.” In a typical restaurant, customers “hold” the seat resource while “waiting” for the food resource. When this state persists, seat turnover drops and lines grow longer — a vicious cycle. The no-seating rule makes it structurally impossible for the “holding one resource while waiting for another” state to occur.
In IT infrastructure design, controlling resource allocation order to prevent deadlocks is fundamental. Database lock management, cloud infrastructure resource pool management, container orchestration scheduling — they all deal with the same structural problem. This restaurant’s rule is essentially a textbook implementation of resource management in physical space.
The Real Source of Dissatisfaction Is “Uncertainty”
If I were to summarize this session’s learning in one sentence, it would be this:
The biggest driver of customer dissatisfaction is not the length of the wait itself, but the uncertainty of not knowing when it will end.
The same applies to IT projects. Being told “we’re behind schedule” is less stressful than being told “we don’t know when it will be done.” Making progress visible and sharing forecasts — that alone completely transforms the customer experience.
Speaking from my experience as an IT delivery manager, the most important element in project status reporting is the outlook for “when it will be done.” Even when there are delays, customers will accept them if you say “we’re delayed by X days for this reason, and here’s the recovery plan.” The worst situation is when “we’re currently checking” drags on indefinitely. This is Principle ② of queue psychology in its purest form.
Just as theme parks display “Current wait time: approximately 45 minutes,” IT projects should constantly visualize remaining tasks, progress rates, and estimated completion dates. Set up dashboards and create real-time visibility. Technically, none of this is difficult. What’s harder is cultivating the mindset of “making things visible.”
Recommended Reading to Deepen This Session’s Learning
For a systematic study of queue psychology and operations design, I recommend the following book. Written by Professor Hidehiko Yamaguchi of GLOBIS, it provides a panoramic view of service management while offering numerous practical frameworks for queue management and service operations design covered in this session.
Next Time
This time we explored queue management. Next, I’ll write about another key to operations design — the power of “making things visible.” There’s a fascinating experiment showing that simply letting customers see the cooking process increased satisfaction by 22%.