Why a wait is judged against what it buys you — sometimes the service itself, sometimes an explicit trade a system builds on purpose — and why neither of those is the same thing as who gets served first.
Imagine a checkout screen offering two options: free delivery in seven days, or a few dollars more for delivery tomorrow. This is a hypothetical, not a documented case — but it’s a familiar enough shape to think with. Nobody here is being served ahead of anyone else. There’s no shared queue at all. The two options simply differ in what you get for what you’re willing to wait.
Three things this course keeps apart#
Week 8 asked what happens when a system deliberately treats classes differently within the same queue — priority as a redistribution of position. This week is not that question, and it splits into two further questions that also aren’t each other:
- Implicit value. Sometimes a wait is tolerated simply because what’s coming is worth it. Nobody designed a trade; there’s no offer, no incentive, no alternative option. The value was just already there in what you’re waiting for.
- Explicit exchange. Sometimes a system deliberately builds a trade on purpose — offering you something (money saved, more flexibility, more certainty) in return for a longer or shorter wait. This is a designed feature of the system, not a fact about the thing you’re waiting for.
Keep these two, plus Week 8’s priority redistribution, as three separate mechanisms. A “pay more, wait less” option can look like all three at once if you’re not careful — this week’s job is learning to tell them apart.
A practitioner’s proposition about implicit value#
Maister proposed that the more valuable a service is to the person waiting for it, the more willing they may be to tolerate waiting for it. Treat this exactly as this course has treated Maister’s other propositions before now (Weeks 2 and 8): a named, long-standing idea from service-management practice, not a tested finding. Nobody in this course’s source list has measured it. It explains nothing on its own — it names a plausible tendency worth watching for, and nothing more.
A measured instance of an explicit exchange#
Dietl, Voigt and Kuhn studied one specific version of an explicit trade: whether offering people an incentive changes their stated willingness to accept a longer delivery wait when shopping online for fashion, shoes, or accessories (Dietl, Voigt & Kuhn, 2024). In a within-subjects, repeated-measures online survey of 323 participants in a German-speaking context, they tested several incentives against a longer delivery scenario. Among their findings: shipping-cost savings significantly increased stated willingness to accept a longer delivery wait in the study.
Read that claim at exactly the scope it earns. This is one bounded retail sector — online fashion, shoes, and accessories — with a non-probabilistic recruited sample, specific delivery-time and incentive levels chosen by the researchers, and a measure of stated willingness rather than observed purchasing or waiting behaviour. It is not a finding that people are willing to pay more for shorter waits — it’s closer to the opposite: people reported more willingness to accept a longer wait when offered a saving in return. Nothing here generalises to other sectors, to physical queues, or to waiting in general.
What this doesn’t establish#
Dietl et al.’s result doesn’t tell you what would happen at a supermarket checkout, a transit stop, or any queue this course has already studied — it’s a single study of one incentive type in one online retail context, measuring what people say they’d accept, not what they actually do. Maister’s proposition remains exactly as untested here as it was in Weeks 2 and 8. Neither source licenses a claim about waiting in general, and neither should be read as proof of the other — one names an unmeasured tendency about value inherent in an outcome; the other measures a stated preference under one specific, deliberately designed incentive.
Why this matters#
Waiting is an experience, not merely a duration — and this week adds one more way that experience can be shaped without anyone’s queue position changing at all: what a wait is exchanged for, whether that exchange was ever designed or simply already there in what’s being waited for. This closes the block Weeks 5 to 9 have been building, each asking a different question about how a waiting system is built rather than just how it’s experienced by one person in it: interfaces, environment, queue structure, priority, and now value. The Queue Case Study, due at the end of this week, asks you to hold several of these mechanisms together in one real system — which means telling them apart correctly matters more now than it ever has.
What you’re doing this week#
The session asks you to read one real system for exactly this: does it change what you get, or does it change who’s served first? The two aren’t always distinguishable from the outside, and saying so honestly is itself part of the answer.
Teaching team
- Marisol Quaye — convenor