Within a one-second delay, the user's train of thought stays intact
Aliases: 1-second rule · unbroken train of thought · thought continuity
What it is
Open a card, switch a tab, see the first batch of search hits — if those land inside about one second, people can still finish the sentence they were holding. That ceiling is continuity of thought: the current goal in working memory has not been cleared, so the next step still attaches. Past that second, people start reconstructing “what was I about to do”. What breaks is the train of thought, not the finger.
It is an order of magnitude wider than the instantaneous causal window. Instantaneity asks whether the act still counts as mine; this one asks whether I still remember what I meant to finish.
Why it happens
The current goal, the options just seen, and the next intended click all sit in a small working-memory store. That store has a decay clock: a second or two without relevant new input and the slots start being stolen. If the system returns the result inside that second, the new input splices onto the old goal and thought need not open a new session. If the system stays silent past a second, decay has begun, and people do two extra things: rehearse the goal (“I was looking for the invoice”) or leak attention to whatever else is in the environment.
Nielsen wrote 1 s as the bound at which the user’s train of thought stays uninterrupted, tracing back to Miller’s pacing of man–computer conversation. The number is not a hard neural constant. It is the empirical edge at which a dialogue still feels like a continuation rather than a new opening.
Studying it
Give a two- or three-step task (find a card, edit a field, confirm) and insert 0.3, 1, 2, 4 s delays between steps. Watch whether people can continue the next step without re-reading the UI.
Independent variables: inter-step delay, whether the step depends on content that just appeared, presence of environmental interruption. Dependent variables: whether the first act after the delay still aims at the original goal, count of spoken goal rehearsals, count of looks back at labels or titles.
Lab tasks are short and quiet, so 1 s looks generous. On a phone, notifications and nearby speech spend working memory early and the continuity threshold drops. Do not declare “one second is enough” from a silent lab alone.
Where it stops holding
Experts repeating a well-worn path keep the goal in long-term memory; a one-second pause hurts less. Novices, cross-page jumps, and people who were just interrupted sit on a tighter threshold. Reading a long article or watching a video is not “will the next step still attach”; continuity here governs an in-flight operation chain. Screen-reader users often act only after a full spoken phrase, so their “step” is already longer than 1 s. Continuity has to be counted in utterance units, not visual seconds.
Applying it
- Make the short steps on an interaction chain (open, switch, pop, first results) completable inside 1 s via local or cached paths. Full network payloads can follow.
- Do not insert a full-page refresh or a full-screen veil between steps; that forcibly clears working memory.
- If a step will exceed 1 s, keep the previous step’s goal visible during the wait (the selected item, the query, the title being opened), an external hook for decaying memory.
- How to check: have someone new to the product do a three-step task and stretch the middle step to about 1.5 s. If they re-read the title or ask “what was I doing”, continuity has already broken.