Why a wait can keep the same clock duration, the same disclosed information, and the same structure while one thing still changes — whether the person waiting has any meaningful choice over whether, when, or how they remain in it — and what one service-encounter study on perceived control does, and doesn't, tell us about that.
Two queues, identical length, identical information at every point along the way. In one, you’re free to step out and rejoin whenever you like. In the other, a ticket system means leaving forfeits your place, so once you’ve joined, you’re in until it’s over. Nothing about the duration or what you’re told has changed. Something else has — and this week names that something.
This week’s claim, plainly#
When a wait’s clock duration, disclosed information, and structure stay the same, one thing changes — whether the person waiting has any meaningful choice over whether, when, or under what conditions they remain in it — and that difference is what this course names control.
Control is the degree to which a waiting person has, or perceives themselves to have, meaningful choice over whether, when, or under what conditions they remain in the waiting situation.
Set this immediately against Week 4’s mechanism, because the two are easy to blur:
- Information: “I know what is happening.”
- Control: “I have an available choice or action that changes my situation.”
A countdown or a queue-position display can be fully informative while offering no choice at all. Control is not “having information,” and it is not generic empowerment, self-determination, or autonomy in the broad psychological sense — it is specifically about a person’s choice over their own presence in a wait.
Nine mechanisms this isn’t#
Time asks how long a wait was judged to be, not whether anyone had a say in it — a high-control and a low-control wait can be judged equally long. Attention is what occupies the mind, independent of agency: you can be fully occupied with no way to leave, or bored with total freedom to. Expectation is a belief fixed before a wait starts; control concerns what’s actually available once it’s underway. Interfaces represent a process; control is about what a person can do, not what’s shown to them. Environment is a physical or digital backdrop — and this needs saying plainly, because this week’s own source uses crowding as part of its design: the density of other people in a space is Week 6’s mechanism. This week’s mechanism is the choice a person has over entering or remaining in that setting, not the crowding itself. Queue structure is an external ordering rule, verifiable or not, independent of any one person’s agency within it. Priority is a class-based criterion imposed from outside; a person can have no priority and full control, or top priority and none. Value is what’s exchanged for time — a paid queue-skip can still lock someone into a slot they can’t leave, and a free queue can still be one they can abandon at will.
What Hui and Bateson actually studied#
Hui and Bateson study perceived control as a mediator of consumer response within a service encounter (Hui & Bateson, 1991). Their design examines two conditions: consumer density — how crowded the setting is — and consumer choice, meaning specifically whether entering into, and staying in, the service situation was the person’s own decision. Their result: perceived control mediates the effect of both density and choice on how pleasant the service experience is judged to be, and on whether the response is approach or avoidance.
Read that at exactly the scope it earns. The choice variable they tested is a “whether” question — whether entering and staying was voluntary at all. This course’s definition above widens that to “when” and “under what conditions” a person can remain — a deliberate course-level extension of the same idea, in the same way Week 7 named “legibility” as this course’s own term rather than one borrowed intact from a source. Keep the two apart: the “whether” component is what Hui and Bateson’s design actually tests; “when” and “under what conditions” is this course’s own extension of it, not a further finding of theirs.
This evidence concerns service encounters and perceived control, not waiting duration itself. Hui and Bateson did not measure judged waiting duration. Their result does not establish that control makes a wait feel shorter. Their setting is a service encounter in general, not a physical queue specifically, and a single study of one context doesn’t generalise to waiting systems as a whole.
What this doesn’t establish#
None of this licenses “giving people control shortens a wait” or “more choice always improves an experience” as general claims. It licenses something narrower: within a service encounter, perceived control was shown to carry the effect of crowding and of a choice-to-enter-and-stay condition onto how pleasant the experience was judged and whether the response was approach or avoidance. It says nothing about how long anyone thought the wait took. And it’s worth naming a distinction the study’s own choice variable raises directly: whether a choice actually existed (actual control) is not the same as whether the person felt they had one (perceived control) — the two can diverge, and this course’s own experiment, below, has to keep them apart rather than treat “control” as one undifferentiated thing.
Designing the manipulation#
Any experiment on control has to resist two easy mistakes. The first is turning it into a Week 4 experiment by mistake: if a design varies what information a person is given and then measures “control,” it has tested information, not control, however the write-up labels it. The second is treating crowding, from this week’s own source, as if it were the thing to manipulate — density is Week 6’s mechanism, present here only as the setting of the source being read, not as this week’s teaching variable.
A course-designed way to avoid both: hold the wait-time and status information identical across two conditions, and vary only whether a genuine, no-penalty choice to continue or leave is available. In one condition, a person must remain until the process finishes; in the other, they’re told plainly they may continue or leave at any point, with nothing else about the wait changed. One honest complication is worth stating directly rather than glossing over: telling someone a choice exists is itself a piece of information — what’s held constant is the wait-time and status information, while the independent variable is the availability of a genuine choice, not the presence of information as such. This is a course-designed simulation, not a description of Hui and Bateson’s own procedure, and it tests whatever can actually be observed — a self-reported sense of control, or whether someone given the option actually leaves — not judged duration, unless a specific design deliberately says otherwise.
Why this matters#
Every mechanism from Week 1 to Week 9 was something done to or communicated to the person waiting. This is the one about what they can do about it — the last individually taught mechanism, and the first one this course teaches through a deliberate manipulation rather than observation alone. The Waiting Experiment, due at the end of this week, asks you to design and run exactly one such manipulation, on control by default or on a mechanism a genuine Case Study gap or a named source limitation points you toward instead — this lecture isn’t asking every student to test control, only teaching what a control-specific test looks like when that’s the right one to run. And the discipline this week asks for — separating what’s evidenced from what’s interpreted, holding “directly evidenced” apart from “caused” — is exactly what the Waiting Audit will ask of every one of the ten mechanisms in Week 12, where a mechanism’s classification and the strength of its evidence are kept as two separate questions, not one.
What you’re doing this week#
The session has you draft one full experiment protocol — prediction, manipulation, measure, and all — and pressure-test it against exactly the failure modes this lecture named, before it becomes the assessment you submit.
Teaching team
- Marisol Quaye — convenor