I once refreshed a visa application portal eleven times in one day. Nothing changed. I knew nothing would change. I refreshed anyway.
You know the moment. The confirmation email lands — "we've received your application" — and then… nothing. Days. Weeks. The service hasn't actually failed you yet. So why does it feel like it has?
The Insight: Silence Isn't Neutral. It's a Message.
Between "we've received it" and "here's your answer," the service knows things you don't. And when it doesn't share them, you don't experience that silence as nothing — you fill it. Usually with the worst-case story.
Harvard Business School's Ryan Buell calls the fix operational transparency: deliberately giving people a window into the work being done on their behalf. In one of his best-known findings — the labor illusion — people in experiments actually preferred a service that made them wait and showed its work over one that answered instantly. Same result, higher perceived value. That was in waits of a minute or less; for a months-long application, transparency won't make the wait feel worth more — but it changes what the wait feels like. (It's also the finding behind every fake progress bar you've ever watched. Hold that thought.)
Three things make the silent gap corrosive:
Silence is ambiguous. No update could mean "on track," "delayed," or "lost." Your brain has to pick one, and it rarely picks kindly.
Uncertain waits feel longer than known ones. David Maister — "you'll hear from us by the 14th" and "you'll hear from us soon" are entirely different experiences of the same wait.
Invisible work is undervalued work. If people can't see the operation, they assume nothing is happening.
Real-World Lens: A Tax Office, a Pizza, and a Blood Test
The UK government counted the cost of silence.
The DVLA (Britain's vehicle licensing agency) was taking 2.4 million phone calls a year from people asking one question: where's my stuff? Meanwhile the Carer's Allowance team cut unnecessary status calls by nearly 40% — by GDS's own count — with something almost embarrassingly small: an email confirming the application had been received. That discovery became GOV.UK Notify, the notification platform now used across the public sector. As GDS's Pete Herlihy put it, status-tracking pages are "channel shift for anxiety" — better to just tell people what the service already knows.
Domino's opened a window into the kitchen.
Herlihy was writing about government services, where waits are measured in weeks — there, a tracking page just gives your anxiety a URL, because you check daily and nothing has changed. Compress the wait to half an hour and the same page becomes something else. The 2008 Pizza Tracker showed your order moving through prep, bake, quality check, delivery, using order-state data the kitchen's systems already held — and because the state changed while you watched, checking it was never hollow. The pizza didn't arrive one second faster. But the anxious "did they even get my order?" wait became something you could watch — and weirdly, enjoy. It's now the canonical example researchers reach for when they teach operational transparency. (Pizza folklore holds that some stages ran partly on timers — Domino's disputes it — which is exactly why the honesty rule coming up matters.)
In a doctor's office, the silence gets dangerous.
A 2022 British Journal of General Practice study looked at how blood test results reach patients. The quietly alarming finding: patients assumed no news is good news, while GPs assumed patients would call in for results. Both sides were waiting for the other to speak. That's not a communication style problem — it's an undesigned gap, and an abnormal result can fall straight through it.
Under the Hood
The gap between received and resolved needs what the healthcare study was missing: an explicit contract for who says what, when — including when nothing has changed.
A playbook for the gap, assembled from the sources below:
The moment | The move |
|---|---|
Something arrives | Confirm receipt on arrival — by GDS's own count, this alone cut unnecessary calls to the Carer's Allowance team by nearly 40% |
Setting expectations | Promise a date you can actually forecast — a specific time that slips three times is worse than honest uncertainty |
Anything changes state | Push the update rather than making people call — and when a result needs interpretation, attach support (a callback offer, a plain-language explainer, a clear "here's what happens next"), don't add delay |
The promised date slips | Say exactly that. An update with no news still resets the clock |
The wait is irreducible | Show the work being done — visible effort is valued effort |
The outcome is "all clear" | Say that too. "No news is good news" is a hope, not a protocol |
That "attach support" clause in row three is earned. In 2021, a US rule required test results to reach patients the moment they exist — no more waiting for the doctor's call. Most patients preferred it that way, and formal complaint rates didn't budge. What appeared instead was a new species of complaint: people reading a life-altering result in a portal, alone, before anyone could explain what it meant. In one large survey, patients who received abnormal results this way were measurably more worried — and a clinician's heads-up beforehand didn't reliably prevent it. The moment of delivery itself is the design problem. Push the state; design the delivery of the meaning.
Two constraints keep the playbook from becoming its own failure mode. First, Buell warns that transparency can backfire — if it's faked, or if it reveals a broken process. When researchers accused Uber's map of showing "phantom" cars, years of reassuring animation turned into a story about deception. Fix the operation before you put glass on it. Second, every update you send devalues the next one — say less, but mean it.
Spotted This Week
Three silences I've been noticing:
👀 Job applications remain the one service where ghosting is the default state — and the same companies that never close the loop with candidates wonder why "we take your application seriously" reads as satire.
👀 A gate agent at my delayed flight announced: "No new information — next update at 3:40." Zero content, and the whole gate area visibly relaxed. An empty update still resets the clock.
👀 The lift in a friend's building broke, and the notice taped to it said only "Engineer called," with no date. Residents kept re-reporting the same fault all week — a tiny, perfect replica of the DVLA's 2.4 million calls.
So What?
The gap between "we've received it" and "here's your answer" is part of your service whether you design it or not. Silence in that gap isn't the absence of a message — it is the message, and it says "we've forgotten you." Communication won't shrink the queue — but it decides whether the queue is experienced as a process or as abandonment. Decide what your service says when there's nothing to say.
Reply and tell me: which service currently has you sitting in a silent gap — and how long has it been since they last told you anything?
I read every reply, and the best ones might show up in a future issue.
Found this useful? Forward it to someone who's refreshing a status page right now.
See you next week.
Sources: