An approach where a system proactively anticipates user needs and surfaces relevant information or actions based on context, history, and learned preferences — reducing the effort required for common tasks. Examples include pre-filling form fields, surfacing shortcuts, and ordering items by frequency of use. The risk is removing user agency when predictions are wrong.
Common contexts
- Pre-filling a shipping address based on the user's last completed order
- Surfacing recently used templates at the top of a creation flow for returning users
- Reordering a navigation menu so the most-visited section appears first per user
Use when
Apply anticipatory design for high-frequency, low-variance actions where the prediction confidence is very high — such as returning users in a familiar flow. The rule of thumb is: if you can be right 90% of the time and the cost of being wrong is low, anticipate. If either condition fails, show options instead.
Avoid when
Anticipatory design backfires badly in high-stakes flows like payments, data deletion, or settings changes — a wrong prediction that the user doesn't notice before confirming can cause real damage. The more consequential the action, the more you want the user consciously in control.
The best anticipatory design is invisible when it's right and gracefully correctable when it's wrong — if the recovery path is unclear, you've just made an assumption users must now fight against.
Real-world examples
- Google Maps proactively shows traffic conditions and estimated travel time to a calendar appointment without the user asking, surfacing the information before they need it.
- Amazon's 'Subscribe & Save' automatically reorders household consumables at a chosen cadence, removing the need for users to remember to reorder.
- Spotify's Discover Weekly playlist is generated every Monday, anticipating the user's desire for new music before they search for it.