/ Library/ What Should We Remember/ Suffix Effect
Recall Bias № 150 · Last updated 6 June 2026

Suffix Effect.

"Add one more thing at the end of the list and the last real item vanishes from memory."

01Overview

The suffix effect is the disruption of serial recall when an irrelevant item is appended after the list — the suffix interferes disproportionately with memory for the last legitimate items. It is not mere distraction; it is structural interference in short-term serial memory.

Products append suffixes constantly: "and don't forget to verify email" after a six-digit code screen; carousel dots after OTP fields; legal microcopy after recovery phrases; notification badges after instruction lists. Each suffix can eat the recency advantage users depended on for the last real step.

02Detailed explanation

Suffix interference appears in micro-interaction design:

  • OTP entry followed immediately by marketing checkbox — last digit errors rise.
  • Recovery codes displayed with animated footer CTA — copy-paste errors increase.
  • Multi-step verbal instructions with joke suffix — users omit prior step.
  • Chat bot adds "anything else?" before user completes remembered reply — suffix displaces rehearsed content.

Protect recency-sensitive tasks from trailing noise. Complete serial recall tasks before suffix content — or isolate critical lists in focused modal without appended chrome.

03Why it exists

Serial memory representation is vulnerable to trailing items that extend sequence past intended end — suffix mistaken as part of list or disrupts rehearsal.

Marketing and legal teams append suffix content without memory cost assessment — conversion and compliance compete with serial task integrity.

The short version

Do not append promotions to the screen where users are holding the last item in memory.

04Effects on users

Users lose last step of instructions when UI adds new message below — suffix effect plus change blindness.

Working memory limited users suffer more — suffix is accessibility issue.

05Effects on designers & teams

Teams suffix by default:

  • OTP plus newsletter opt-in same view. Suffix on serial task.
  • Animated upsell under codes. Motion suffix after static list.
  • Footer legal after security steps. Trailing text interferes.
  • Bot prompt stacking. New message before prior answered.

06Practical takeaways

  • Isolate serial recall tasks. Full-screen focus without trailing modules.
  • Defer suffix content to next screen. After task complete.
  • Minimise motion after code display. Let recency consolidate.
  • Order: critical list, confirm, then extras. Never interleave.
  • Test error rates with and without suffix UI. Measure interference.
  • Accessibility review for working memory load. Suffix hurts most when load high.

07Design examples

Auth

Code plus checkbox

OTP screen adds marketing opt-in below entry. Wrong-code rate rises 18% versus isolated OTP — suffix effect on recency digit.

Security

Recovery phrase footer

Users miscopy last word when animated upsell appears beneath backup codes. Remove animation; errors drop.

Support bot

Stacked prompts

Bot asks follow-up before user sends remembered account number. Users re-ask or omit digits — suffix message disrupted rehearsal.

Onboarding

Joke after steps

Setup list ends with humorous tip. Recall test shows step five forgotten more when joke present — suffix on procedural list.

08Ethical risks

Deliberately suffixing distractions onto security tasks to rush consent exploits memory interference — not benign UX clutter.

Users with cognitive disabilities face higher suffix cost — inclusive design removes trailing noise from serial tasks.

Self-test: What trailing content appears on screens where users hold ordered information in memory — and does it need to be there?

10Suggested reading

Browse recommended reading →