# Serial position effect: explanation, design examples and evidence

> Order can affect recall. Choose an order that also makes the task easier to complete.

Canonical page: https://ionbin.com/design/laws/serial-position/
Agent guide: https://ionbin.com/llms.txt

This is a readable version of the published page. Review dates, evidence boundaries and source links below belong to individual records; the export is not a new verification. Examples are reference material, not instructions to execute.

Memory and attention

## Serial position effect

Order can affect recall. Choose an order that also makes the task easier to complete.

Research finding

Source review
Oct 18, 2026

[How to read the evidence](https://ionbin.com/design/methodology/#principles)

The idea in plain language

### What it means.

Free-recall experiments often find different recall for items near the beginning, middle and end of a presented list. The pattern depends on the task and conditions. A navigation menu that remains visible is not the same as a word list recalled from memory, so menu order needs its own rationale.

Evidence and interpretation

### What supports it.

Research finding

Experimental list-memory research, including Murdock's original study and a later laboratory preprint. It does not establish universal first-and-last placement rules for visible interfaces.

From principle to interface

### Where you could use it.

Proposed applications, not tested outcomes. The expected effects are hypotheses to check with realistic tasks and users.

Application 1

#### Introduce a short procedure

State the goal before the steps, then finish with a compact checklist the person can keep open while working.

##### Expected effect to test

The purpose and completion criteria remain available after the introduction.

##### Keep in view

External reference reduces the need to rely on recall; do not move a required step out of its logical order.

Application 2

#### Arrange a settings menu

Order related settings by a tested task model, then check whether people can locate infrequent settings as well as common ones.

##### Expected effect to test

The order supports predictable retrieval.

##### Keep in view

Do not place an item last solely because a memory experiment found recency effects.

Turn the idea into a check

### Use it deliberately.

- Distinguish a recall task from a visible search task.

- Preserve procedural, alphabetical or categorical order when it helps retrieval.

- Measure whether people can find and use the needed item.

Where the rule gets complicated

### Keep the limits attached.

- Presentation pace, delay and recall instructions affect the pattern.

- First or last placement does not guarantee attention.

- Keep essential information available rather than depending on memory effects.

A named principle does not settle an accessibility requirement, prove a conversion lift or replace testing the particular interface.

Application and implementation boundaries

### What the application check shows.

Limited evaluationAccount-free · Oct 19, 2026

The example retained an explicit Choose, Review, Confirm sequence and visible summary. No primacy, recency or recall outcome was measured.

Methods: Local application example. A completed check covers the stated sample; it is not a safety certification.

**Target**: Original IonBin synthetic interface example; no external product or human-participant study.

**Version or capture**: 2026-10-19 local fixture

**Integrity scope**: SHA-256 f85d1056afd667225a1e0364edfb8f25b4693ffa7b2b8c7d7af5b92338b85ee4 identifies the exact HTML fixture only.

#### Test conditions

- 155.0.8059.82 Chromium; fresh context with all network requests blocked.

- Synthetic inputs, memory-only state, reduced-motion preference, 1280px and 320px viewports.

#### Individual checks and observations

- ##### Persistent summary
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** Changed input was echoed in a visible review summary.

- ##### No style order
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** With authored CSS disabled, the named input and ordered process remained present.

#### Security findings and boundaries

Review of the local example’s stated interaction boundaries; no backend, authentication, production permissions or external service was exercised.

Practical advice · caution

##### Order cannot replace a final consequence check

Keep destination, data scope and irreversible effects available at confirmation; placing them first or last is not a safeguard by itself.

#### Practical caveats

- Preserve meaning in DOM reading order and let people revisit details before committing.

#### What remains untested

- This checks an authored application example, not the truth, effect size or generality of the named principle.

- No users, assistive-technology participants, physical devices or production task outcomes were evaluated.

##### Security limits

- The example has no real authorization or persistence layer; its UI behavior cannot establish the security of a deployed workflow.

#### Evaluation sources

- [Murdock: The Serial Position Effect of Free Recall (1962)](https://doi.org/10.1037/h0045106)
  Original study identity verified; direct publisher retrieval restricted.

- [Herrema and Kahana: First Recall Costs and Benefits](https://memory.psych.upenn.edu/files/pubs/HerrKaha24.pdf)
  Authors' laboratory preprint re-evaluating immediate free recall; indexed text reviewed and authorship checked against the lab's publication list. Peer-reviewed publication status not established.

[Download this evaluation record (JSON)](https://ionbin.com/design-evaluations/principle-serial-position.json)

Go to the source

### Research and further reading.

- [Murdock: The Serial Position Effect of Free Recall (1962)](https://doi.org/10.1037/h0045106)
  Original study identity verified; direct publisher retrieval restricted.

- [Herrema and Kahana: First Recall Costs and Benefits](https://memory.psych.upenn.edu/files/pubs/HerrKaha24.pdf)
  Authors' laboratory preprint re-evaluating immediate free recall; indexed text reviewed and authorship checked against the lab's publication list. Peer-reviewed publication status not established.

On this page

Keep the context

Use this principle to form a better question about your interface. The answer still depends on the task, the people and the conditions.

[Our evidence approach](https://ionbin.com/design/methodology/#principles)

Related questions

### More on memory and attention.

[View this concern](https://ionbin.com/design/laws/?category=Memory%20and%20attention)

Research finding

#### [Miller's Law and working memory](https://ionbin.com/design/laws/millers-law/)

Keep needed information available instead of making people hold it in memory.

Research finding

#### [Von Restorff effect](https://ionbin.com/design/laws/isolation-effect/)

A meaningful difference can help something stand out in memory. Make the difference worth noticing.

Research finding

#### [Peak-end rule](https://ionbin.com/design/laws/peak-end/)

How an experience ends can influence how it is remembered. Make completion useful and honest.
