Silence is an intervention

The orthodoxy has receipts, and they are good ones. In 1982 two IBM researchers, Walter Doherty and Arvind Thadani, published a 400 millisecond response-time threshold, the point below which a person stops waiting on a machine and starts thinking with it, and the number still sets targets in interface work forty years later. Google measured the same law from the other side in 2009, when a controlled experiment adding between a tenth and four tenths of a second of delay to search results reduced the number of searches people ran, with the effect persisting for weeks after the delay was removed. Latency is a tax. We are not disputing the finding.

We are disputing where it generalizes. Doherty measured programmers editing code. The Google experiment measured people looking things up. Both are transactions, tasks with a right answer and a person who wants it and then wants to be gone, and in a transaction the wait is pure overhead, which is exactly why removing it is pure gain. Carry the same instinct into a moment where somebody has just said something difficult, and the technically excellent instant reply communicates that nothing happened in between. The interval before a reply is itself a message about the kind of attention being paid, which means a system that drives the interval to zero has not removed a cost, it has overwritten what the pause was saying.

So the delay is written into the specification rather than left to taste, because a number nobody wrote down loses every argument with a performance dashboard. Our design system states outright that the system does not optimize for minimum time to first token in session contexts, and requires a presence indicator to hold for a minimum duration before the first character of text appears, so that an immediate model response does not arrive with the uncanny quality of an answer that was waiting. The motion specification sets a default initial response delay of roughly a second and a half, extended to between two and four seconds in high-arousal emotional contexts, and paces streamed text at around three words per second with pauses at sentence and clause boundaries rather than revealing it token by token. Before any waiting indicator appears at all there is an attentive silence window of three to five seconds, and a companion rule that silence is never left past five to seven seconds without a minimal acknowledgment, because unmarked absence stops reading as presence and starts reading as failure.

The doses are the argument. Slowness is not a virtue here, and an interface that made a person wait to seem thoughtful would be running the same manipulation as the one that answers instantly to seem capable, only with worse manners. That is why the same specification bypasses the silence behavior entirely for urgent or safety-critical content, and why the pacing targets vary by phase rather than sitting at one pious constant, faster for structured task work and slower where something is being processed. The pause is instrumentation for a particular kind of moment, not a house style.

Every one of those numbers is a number a dashboard would flag as a regression. Time to first token is the metric the whole industry ships against, and the honest description of what we are doing is that we accept a worse score on it in the contexts where the score measures the wrong thing. This is what designing against your own incentives looks like in practice, not a manifesto but a default in a spec file that costs something real on a chart somebody reports upward every month. A product cannot protect a pause it has not agreed, in writing and in advance, to lose an argument about, and the pauses worth protecting are the ones where a person is deciding what they actually think.