Design to preserve user momentum.
Minimize interruptions that break cognitive flow.
Contents 4. System Behavior & Workflow Logic 7. Latency
How temporal constraints influence workflows.
First, ask yourself
“Does your system preserve user momentum under delay?”
Mission statement
Ensure users maintain flow by minimizing delays and communicating wait states.
Key heuristics Latency
- Interaction must preserve user cognitive flow.
- User input must receive instant perceptual response.
- System activity must remain perceptible during processing.
- Delays must not halt all interaction unnecessarily.
- Initiation and completion must be separated when feasible.
- Dependent sequential requests must be minimized.
- Waiting states must not impose additional cognitive decisions.
- Progress feedback must be accurate and proportionate.
- Usability must be maintained under slow or unstable conditions.
Executive brief
The system must preserve user momentum by controlling both real and perceived latency.
Core questions Latency
“Does the system preserve user momentum despite delays?”
“Is latency absorbed or does it interrupt thinking and flow?”
Focus areas
Perception-first
“Do pauses force users to wait, or let them continue working?”
“Is time experienced as friction, or is it masked by progress?”
Workflow-aware
“Does delay block progress, or just slow completion?”
“Can users stay productive during unavoidable waits?”
Communication-aware
“Does silence cause users to doubt the system?”
“Is delay explained clearly and promptly?”
AI-aware
“Does AI hide latency, or add to it?”
“Are long-running operations staged to preserve flow?”
UX directives Latency
Provide instant acknowledgment of user input.
Respond perceptually even if processing continues.
Reduce perceived latency through visible system activity.
Do not allow silent waiting states.
Keep users productively occupied during delays.
Prevent blocking states that halt all interaction.
Separate initiation from completion when possible.
Allow background processing without freezing interaction.
Minimize dependent sequential requests.
Reduce cumulative delays caused by repeated server interactions.
Avoid requiring decisions during idle delays.
Do not compound waiting with cognitive effort.
Provide truthful and proportional progress feedback.
Avoid misleading estimates or cosmetic animations.
Ensure graceful degradation under poor conditions.
Maintain usability during slow or unstable performance.
Executive summary
- Latency is disruption of cognitive momentum, not just elapsed time.
- It interrupts flow when system response lags behind user intent.
- The system must acknowledge input immediately, even if processing continues.
- Waiting states must be visible, truthful, and non-blocking whenever possible.
- Interaction must remain productive during delay, with graceful degradation under poor conditions.
- Latency succeeds when users perceive continuity of control despite underlying processing time.
Success indicators
- The system acknowledges user input immediately.
- Users can see that the system is processing work.
- Waiting states are clearly communicated.
- Users can continue working while background tasks run.
- Slow performance does not block essential tasks.
One-line summary
Before users lose momentum, the system must respond.