Serial Position: Use the Beginning and End Deliberately
Use openings for orientation and endings for resolution without treating the middle as disposable.
Start with the moment where the interface asks too much.
A navigation has eight equal items. The team places the most important product in the middle because the list looks balanced. In testing, people remember the first destination, the account action at the end, and little between. The middle was not worthless. It was unprotected.
Beginnings establish orientation and endings shape resolution. Use sequence to help comprehension and recall, not to manipulate attention or treat middle content as disposable.
Show the failure and the correction.
The lab uses controlled markup instead of raster text so the lesson stays legible, accessible, and easy to revise.
- The list looks balancedRecall and orientation drift.
- The page opens weaklyThe rest of the story has to repair the opening.
- The ending is vagueAttention fades without action.
- Sequence gets designedThe whole path becomes easier to remember.
Orient early
Use the beginning to name audience, promise, context, and first route.
Make the useful path easier.
Use cautiously
Do not claim people always remember only first and last. Use the effect as a practical prompt to design openings, landmarks, and endings with intent.
Protect the middle
Subheads, grouping, summaries, and progress markers keep middle content from becoming a long undifferentiated run.
Ethical order matters
Do not bury price, risk, terms, or consequences in the forgettable middle. Sequence should support understanding, not concealment.
Turn critique into a usable rule.
Remove
Political navigation order
Internal importance overrides visitor orientation.
Slow opening
The page spends early attention on atmosphere before naming the useful promise.
No resolution
A long page ends without summarizing what changed or what comes next.
Build
Orient early
Use the beginning to name audience, promise, context, and first route.
Develop with landmarks
Break middle content into memorable sections with clear jobs.
Resolve honestly
End sections and pages with a conclusion or next action that follows from what came before.
Use it on a real page.
Let readers scan the page or navigation briefly.
Ask what the page promised.
Ask which facts supported it.
Ask what action concluded it.
Check whether important middle content had memorable landmarks.
- Use recall notes and route analytics only as supporting evidence.
- Recall matches the intended story, including protected middle content.
- People remember only decorative endpoints or miss material information.
The rule should help the person making the next decision.
Business owner
Do not order pages and nav only by internal departments.
Designer
Design beginnings, middle landmarks, and endings as different tasks.
Developer
Keep anchors, headings, and previous/next navigation stable for long pages.
Reviewer
Ask what people remember after a short scan and compare it with the intended story.
Meaning, convention, and frequency can outweigh position. Do not move an item to an edge if that breaks an established mental model or harms task flow.
Check the page, then answer the doubt.
- The opening names the promise and context.
- Navigation order follows user orientation.
- Middle sections have strong landmarks.
- Endings resolve with a clear next step.
- Material facts are not buried.
- Mobile sequence is rechecked after stacking.
- Do users ignore the middle of a page?
- No. The middle needs structure, landmarks, and relevance. The effect is a caution, not a dismissal.
- Where should important navigation items appear?
- Where they best support user orientation, convention, and frequency—not simply at the beginning or end by rule.
- How should long pages maintain attention?
- Use meaningful section landmarks, summaries, progress, and relevant resolutions instead of one long undifferentiated scroll.
Standards and research links support the factual parts of the rule. They do not replace original judgment on the page.
Use the rule on the page that matters.
Use this when the reader is ready to inspect their own page before asking for a rebuild.
Get the conversion checklist