Use anticipation to reduce user effort.
Design anticipatory behavior to remove friction rather than demonstrate intelligence.
Contents 4. System Behavior & Workflow Logic 2. Anticipation
What a system brings forward proactively.
First, ask yourself
“Does your system surface the next likely need for users without commandeering?”
Mission statement
Ensure users act with less effort by predicting and supporting likely needs.
Key heuristics Anticipation
- Anticipatory behavior must remove friction, not display intelligence.
- Anticipatory features must maintain user agency.
- Users must recognize when the system is predicting or assisting.
- Anticipatory assistance must appear at the moment it supports the current task phase.
- Anticipation must be based on current task, state, and history.
- Anticipatory interventions must be limited.
- Users must be able to dismiss or ignore anticipatory assistance without penalty.
- Incorrect anticipatory actions must be easy to ignore or reverse.
Executive brief
The system must anticipate user needs without overriding user control.
Core questions Anticipation
“Does the system anticipate user needs without taking control?”
“Is help timely, helpful, and under user control?”
Focus areas
User-agency first
“Does anticipation assist decision-making rather than preempt it?”
“Can users easily ignore or decline suggestions?”
Timing-aware
“Is help delivered neither too early nor too late?”
“Does anticipation reduce preparation work effectively?”
Transparency-aware
“Are predictions and suggestions understandable?”
“Can users see why the system anticipates certain actions?”
AI-aware
“Are predictions legible and bounded?”
“Does learning improve assistance without reducing trust?”
UX directives Anticipation
Preserve user control in anticipatory features.
Offer suggestions rather than automatic irreversible decisions.
Make anticipatory behavior perceptible.
Ensure users recognize when the system is assisting or predicting.
Deliver anticipation at the moment of relevance.
Trigger assistance only when it meaningfully supports the current task phase.
Base anticipation on current context.
Use task, state, and history signals to ensure relevance.
Limit anticipatory interventions.
Do not overwhelm with excessive or unnecessary suggestions.
Ensure anticipatory assistance is optional.
Allow users to dismiss or ignore suggestions without penalty.
Minimize the cost of incorrect anticipation.
Ensure mistaken suggestions are easy to ignore or reverse.
Executive summary
- Anticipation is friction reduction, not intelligence display.
- It assists by predicting relevance without removing user control.
- The system must make anticipatory behavior perceptible and contextually justified.
- Anticipatory suggestions must be optional, limited, and easily dismissible.
- Incorrect anticipation must carry minimal cost and never compromise user work.
- Anticipation succeeds when assistance feels timely, helpful, and fully subordinate to user intent.
Success indicators
- The system offers helpful suggestions that reduce user effort.
- Suggestions appear when they are relevant to the current task.
- Users can clearly see when the system is making a suggestion.
- Suggestions are easy to accept, ignore, or dismiss.
- Incorrect suggestions do not interrupt work or create extra effort.
One-line summary
Before users are forced to search or prepare, the system must already be ready.