Design state to offload user memory.
Ensure the system remembers context so users do not have to reconstruct it.
What a system remembers for users.
First, ask yourself
“Does your system reliably remember and reveal state that affects users’ outcomes?”
Mission statement
Ensure users understand system status by making current state visible.
Key heuristics State
- System state must relieve users of reconstructing context.
- Outcome-relevant state must be perceptible.
- State affecting user work must be viewable and understandable.
- Different state types must be behaviorally and visually distinguishable.
- All meaningful state changes must be clearly indicated.
- Stored context must be modifiable and resettable.
- State must survive interruption and navigation.
- Remembered state must clearly reflect user intent.
- Stored state must be safeguarded for integrity, security, and privacy.
Executive brief
The system must remember for users in ways they can see and trust.
Core questions State
“What is the system remembering for users?”
“Can they see it, understand it, and control it?”
Focus areas
Visibility-first
“What state exists right now? Where is it visible?”
“If users leave and return, what will still be there?”
Continuity-aware
“Can users resume exactly where they stopped?”
“What survives interruption? What does not?”
Control-aware
“Can users reset, edit, or override what is remembered?”
“Is saved state helping users, or getting in the way?”
AI-aware
“What is explicitly set versus inferred?”
“Does adaptive memory stay clear and understandable over time?”
UX directives State
Make outcome-relevant state visible.
Do not allow hidden conditions to influence results without perceptible indications.
Make sure state is inspectable.
Ensure users can view and understand the state that affects their work.
Differentiate state types explicitly.
Distinguish local, session, and persistent states in both behavior and presentation.
Signal all meaningful state changes.
Prevent modifications to state without clear and timely feedback.
Make state reversible and resettable.
Provide clear mechanisms to modify or undo stored context.
Persist state across interruptions.
Ensure work and context survive pauses, navigation, and session breaks.
Align remembered state with user intent.
Do not preserve or apply state that contradicts user expectations or goals.
Treat state as protected user data.
Apply integrity, security, and privacy safeguards to stored context.
Executive summary
- State is remembered context, not invisible system memory.
- It offloads user memory by preserving what affects outcomes and continuity.
- The system must make relevant state visible, inspectable, and understandable.
- State types and changes must be explicit, not silently inferred.
- State must be reversible, persistent across interruption, and aligned with user intent.
- State succeeds when users never have to reconstruct what the system should already know.
Success indicators
- The system remembers user context so users do not rely on memory.
- Important state information is visible and easy to understand.
- Changes in state are clearly signaled.
- Users can review, modify, or reset system state when needed.
- Work and context persist across navigation, pauses, and interruptions.
One-line summary
Before users can decide what to do next, they must know what has already happened.