Feedback dwell time must match the importance of its information

What it is

Feedback dwell time is how long a state, confirmation, warning, or result remains visible. It should match importance, time needed to read and act, whether it can be recovered elsewhere, and current workload. A low-consequence confirmation verifiable through object change can be brief; a message requiring understanding, choice, repair, or later trace should persist until handled, superseded, or reliably recoverable. Duration is part of information access, not an ornamental animation parameter.

Why it happens

Attention is not always available at the moment a notice appears: people may be entering text, watching an object, obscured by a keyboard, scrolling, or distracted. Brief messages require a perfectly timed shift and can lose important content. Long persistent messages consume space, cover work, and become background through repetition. Appropriate duration balances information value against attention cost, giving actionable states a chance to be understood without making low-value confirmation continuously disruptive.

Studying it

Vary duration across workload, device, reading length, and location. Measure discovery, accurate understanding, completed action, occlusion errors, and voluntary dismissal. Test whether people can recover information while entering text, scrolling, with keyboard visible, amid notice stacking, and after a brief absence. “Was it too long?” is not enough; establish whether required content was obtained before disappearance or can later be recovered.

Where it stops holding

Important does not always mean permanently persistent. Sensitive information, one-time errors, and constrained screens may move after initial display into a safe history or notification center. Conversely, low-risk content that changes a next action cannot vanish merely because it is “just a hint.” A universal number of seconds cannot fit language, screen reader, zoom, cognitive load, and setting. Let duration follow the comprehension/action task, not brand motion rhythm.

Applying it

• Grade feedback by consequence, required action, object-level verifiability, and recoverability; define brief, persist-until-confirmed, persistent record, or background-notice policy.
• Give actionable notices explicit controls, visible dismissal, and a reliable review route; auto-disappearance cannot be the only ending.
• Check reading completion and occlusion cost in localization, zoom, screen reader, and high-load tasks rather than timing only short default copy.
• Use interruption tests: after missing initial display, users should still recover important state. Loss or chronic obstruction signals an imbalanced duration policy.

Related

• Within the group: D1.14.2 Brief feedback can vanish before being read · D1.14.3 Persistent feedback becomes noise · D1.14.4 Users should shorten or extend duration
• Adjacent: D1.01 Immediate operation feedback · D1.15 Intensity proportional to consequence
• Search terms: feedback dwell time · message duration · transient feedback