> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/psychology/serial-position-effect.md).

# Serial Position Effect

Users are most likely to remember items at the beginning and end of a list.

The Serial Position Effect or sometimes called The Serial Position Principle is a psychological concept that says people tend to remember things at the beginning and end of a list better than the things in the middle. It encompasses both the Primacy Effect and the Recency Effect.

The **Primacy Effect** is like the "first impression." People tend to remember the items at the beginning of a list better. It's a bit like when you meet someone for the first time; you remember that meeting more clearly.

The **Recency Effect** is about what you remember last. Items at the end of the list are often remembered well because they are still fresh in your mind, just like how you can easily recall what you did recently.

However, the things in the middle of the list are usually the hardest to remember.

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=n0IOkxGlufQ>" %}

#### Further Reading

{% embed url="<https://lawsofux.com/serial-position-effect/>" %}

{% embed url="<https://www.interaction-design.org/literature/article/serial-position-effect-how-to-create-better-user-interfaces>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/psychology/serial-position-effect.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.