Facts from other pages must remain visible here

What it is

The decision is on this page; the facts it needs stayed on the last one. That is a working-memory haul. When memory load is already high, a failed haul is not carelessness—the design outsourced record-keeping to internal memory. Cross-page information visibility requires that facts this step will use appear on this screen, to be read here, not recalled.

Visible is not “type it again.” An order number printed in a sidebar is visible; asking the user to re-key it is a different failure. A review at the end of the flow is also not this leaf: review happens last. This leaf is the current step missing its grounds.

Why it happens

A page turn costs delay and new content at once. Items just held decay; new judgements crowd the same processing resource, so “remember the last page, use it here” is far more fragile than designers assume. Cognitive disability and ageing shorten that path further.

Putting the grounds on the current page is cognitive offloading: working memory stops hauling, the interface holds. What must be offloaded are the facts this judgement depends on—selected plan, price, deadline, the previous answer—not a thumbnail of the entire last screen. A thumbnail still asks someone to read a picture that is no longer in focus; offloading did not finish.

Studying it

Walk every place where a fact appeared on the previous screen and is still needed to judge or fill this one, and ask whether it remains as readable text. A harder behavioural marker than satisfaction is how often people go back to check: high returns mean this page did not put the grounds down.

Independent variables: whether the critical fact is present as text, whether it sits next to the point of use. Dependent variables: back-to-check counts, error rate on fields that depend on the fact, time to complete.

Laboratory memory-span numbers are not a cap on “how many facts this page may show.” The question is whether the needed facts are here, not information density.

Where it stops holding

Personal facts the user already knows (their own name) need not be pasted forward. Product-generated identifiers, prices, and chosen configurations must. When security forbids printing a full card number, last four digits plus issuer still count as usable grounds on this page. A single-screen form has no cross-page problem; splitting one page into steps and leaving the grounds behind is what trips this leaf.

Applying it

• Repeat the constraints this step needs in text: plan, price, date, quantity, next to the judgement, not as a flash at the top of the page.
• A sticky summary or sidebar is fine if it is readable text, not a hope that the user remembers the summary once appeared.
• Verify: print or screenshot only the current step and give it to someone who never saw the earlier ones. If they cannot make the judgement the page asks for, the grounds are still elsewhere. Count real users’ returns to the previous page; high returns are the same defect in behaviour.

Related

• Same group: J4.09.2 Do not ask again for information already given · J4.09.3 Provide a review and summary before submission
• Nearby: A6.02 Working memory capacity · A6.21 External memory and cognitive offloading · J4.07 Cognitive accessibility
• Search terms: cross-page information visibility · working memory · cognitive offloading