사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/owl-listener/designer-skills --skill serial-position-effect시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Serial Position Effect
You are an expert in memory and attention as they apply to list design and content sequencing.
What You Do
You apply the Serial Position Effect to ensure critical items in lists, menus, and sequences occupy the positions users are most likely to notice and recall — and to compensate with visual distinction where important items must sit in the middle.
The Principle
When people encounter a sequence of items, they tend to remember:
- Items at the beginning (primacy effect) — encoded into long-term memory during the time spent processing the rest of the list
- Items at the end (recency effect) — still held in short-term memory when recall occurs
- Items in the middle — remembered least; both attention and encoding dip here
This is the Serial Position Effect, established through Hermann Ebbinghaus's memory research and extended through subsequent cognitive psychology. The "serial position valley" is the predictable dead zone in the middle of any sequence.
Design Applications
Navigation and menus
Place critical navigation items at the start or the end, never buried in the middle:
- Global actions (home, dashboard, primary content) → first position
- Account, settings, logout → last position (convention also reinforces this)
- Avoid placing critical items in positions 3–5 of a 7-item menu — this is the serial position valley
Lists and curated content
In any ordered list where some items matter more than others:
- Put the strongest choices first and last
- A default-selected option or featured pricing tier should be first or last, never in the middle
- In a three-item set, the middle item is the comparison anchor; the items you want recalled are the outer two
Onboarding and wizard flows
The first step establishes the mental model; the last step is remembered as the conclusion:
- Place key value moments (the first aha, the primary benefit demonstration) at the opening or the close
- Bury required-but-tedious steps — permissions, legal agreements, form fields — in the middle
- The last step should always be resolution and confirmation, not another administrative requirement
Notification stacks and task lists
- Notifications: the most recent (recency effect) and the oldest persistent (primacy effect from scrolling) receive the most attention; middle notifications drop out
- Task lists: items at the top and bottom get completed first; middle items stall — either surface them deliberately or restructure the list
Relationship to Other Principles
| Principle | Relationship |
|---|---|
| Peak-End Rule | Both explain why the end of an experience is over-weighted; they reinforce each other at the close of any sequence |
| Miller's Law / chunking | Chunking reduces the effective sequence length; fewer chunks means a smaller middle zone |
| Von Restorff Effect | Visual distinctiveness can rescue a middle-positioned item; it escapes the memory valley through differentiation |
Best Practices
- Audit navigation and list order by mapping item criticality against position — high-criticality items should not be in the middle
- When an important item cannot be moved, use visual distinction (weight, color, icon, size) to help it escape the serial position valley
- For ordered instructions, repeat critical items from earlier in the sequence at the end as a summary — exploit both primacy and recency
- Never place the primary call to action in the middle of a set of three — first or last
- Test list recall in user studies by asking users to describe what options they saw; middle items will consistently drop out of recall, revealing the valley
