What Is the Serial Position Effect?
In 1962, Bennet Murdock Jr. ran a free-recall experiment that became the standard reference for this effect: participants viewed lists of 10 to 40 words, each shown for one second, then had 90 seconds to recall as many as they could in any order. Regardless of list length, the same pattern held - people recalled the first three or four words and the last several words far more reliably than anything in the middle. Plotted against list position, the result is the serial position curve: a sharp bump at the start, a bump at the end, and a flat stretch in between. The early-item advantage is the primacy effect; the late-item advantage is the recency effect. Related observations go back further - Hermann Ebbinghaus noted something similar in his 1885 serial-learning work - but Murdock's paper is what established the curve as a measurable, repeatable result.
Why Primacy and Recency Happen
The two effects come from different mechanisms. Early items get rehearsed more - by the time item five shows up, item one has already been mentally repeated several times, pushing it into longer-term storage. Late items don't need rehearsal to be recalled; at the moment of the test, they're still sitting in working memory. Interrupt the recall task with a delay or a distractor before testing, and the recency effect collapses while primacy holds - the delay empties working memory but doesn't touch what's already been consolidated.
Implications for UX Design
- Navigation menus: Put the most important items first and last. Middle items get measurably less attention - don't bury your primary destination in the centre of a nav bar.
- Onboarding flows: The first screen and the completion screen do the most work in shaping how someone remembers the whole experience - this is the same mechanism behind the Peak-End Rule.
- Feature and pricing lists: With six features listed, put your strongest differentiators at positions one and six. The middle four get skimmed, not read.
- Forms: The first field sets expectations; the last field frames the act of submitting. Both deserve more thought than a field in the middle of the form.
Working With Recency in Notifications
Recency bias also explains why the most recent experience with a product dominates someone's overall opinion of it. An app that crashes on the way out gets remembered as "the buggy one," even after ninety-nine smooth sessions. Exit states, success screens, and session endings deserve the same design attention as onboarding - they're the part users carry with them.
