Users should not have to remember information across screens
Aliases: cross-page memory · context preservation · form comparison
What it is
In multi-page flows, comparisons, and multi-object operations, users should not have to memorize an ID, price, permission, filter, or step choice from the previous page. Recognition over recall requires necessary context at the current decision point, or a low-cost way to return and inspect it.
Why it happens
Screen changes clear the user’s organized focus; working memory holds only a few unrelated items, and time pressure and interruption accelerate loss. If two objects must be compared, show them side by side; if later fields depend on earlier choices, show the selected summary and its effect. Requiring memory disguises errors as carelessness and adds burdens of returning, screenshotting, and external note-taking.
Studying it
Contrast a context-preserved against a context-cleared version of the same cross-page task. Dependent measures: error rate, number of back-navigations to re-inspect the earlier page, completion time, and accuracy of post-task recall. Independent variables: number of steps spanned, the delay between steps, and whether an interleaved distractor task is inserted to stand in for real-world interruption.
Think-aloud earns its cost here. Ask people to verbalise at the moment of each page change and count where hedges like "I think I picked…" appear. That locates the decision points that actually need a carried-over summary, instead of spreading summary affordances evenly across the flow on guesswork.
Where it stops holding
Not all history needs permanent exposure. Context summaries can collapse and audit details expand on demand; sensitive data may need masking. Secure workflows sometimes intentionally restrict copying across screens, but must state the rule and provide controlled confirmation. Long flows should support drafts rather than requiring completion in one session.
Applying it
- Preserve selected objects, filters, orders, drafts, and current steps across pages; do not reset them on return.
- Provide side-by-side views or pinnable summaries for comparison, and show key source fields when a form references a record.
- Display decision context such as “3 selected, budget remaining X, step 2 of 4” on each page.
- Test leave-and-return paths and record which pieces of information can be restored only from screenshots or notes.