/ Library/ What Should We Remember/ Misattribution of Memory
Recall Bias № 089 · Last updated 6 June 2026

Misattribution of Memory.

"Users remember the fact but assign it to the wrong screen, brand, or version — source and content split apart."

01Overview

Misattribution of memory is remembering information correctly but attributing it to the wrong source — wrong app, wrong screen, wrong person, wrong time. Source memory is fragile; content memory is stronger. Users confidently cite your product for a policy they read elsewhere, or vice versa.

Designers encounter misattribution when users swear a feature was on your settings page (it was a blog post), when competitor comparisons blur after a research session, and when rebrand migrations inherit memories tied to old visual context. Content without clear source tagging becomes orphan memory waiting for wrong attribution.

02Detailed explanation

Misattribution spans several subtypes relevant to product work:

  • Users believe they consented on your site to terms they only saw in an email summary.
  • Beta participants attribute prototype bugs to production — or production polish to prototype memory.
  • Multi-tab research blends competitor features into your mental model.
  • Cryptomnesia-adjacent: users propose "new" ideas they encountered in your docs weeks ago — source lost, content familiar.

Distinctive context, source labels, and consistent visual language reduce misattribution. Generic UI patterns increase it — everything looks like everything else.

03Why it exists

Source monitoring requires cognitive resources at encoding. Under distraction, multitasking, or generic UI, content encodes without reliable source tags.

Repeated exposure across channels (ads, email, app, support) merges sources into one fuzzy brand memory — convenient until precision matters for compliance or support.

The short version

Users will remember what you said. They may not remember it was you who said it — or where.

04Effects on users

Users contact support citing "your website promised X" from a third-party review. Misattribution becomes dispute.

They mix up which app in a suite handles which permission — security-relevant misattribution.

05Effects on designers & teams

Teams trigger misattribution through design choices:

  • Generic design patterns without brand anchors. Modals that look like system dialogs.
  • Off-site policy only. Terms linked out, never shown in context of action.
  • Research protocols without source tags. Competitor features blur into synthesis.
  • Rebrand without migration cues. Old visual context lost; memories float unattached.

06Practical takeaways

  • Source-tag critical copy. "In this app, on this screen" for consent and pricing.
  • Keep legal actions in-context. Show terms at point of decision, not only in email.
  • Distinctive visual language for your product. Reduce confusion with system and competitor UI.
  • Research debrief source hygiene. Label which tool showed which feature in synthesis.
  • Rebrand with explicit mapping. "Formerly X, same account" bridges memory sources.
  • Support tools surfacing where user saw claim. Session replay for attribution disputes.

07Design examples

Consent

I never agreed to that

User denies marketing opt-in. Logs show in-app toggle; user remembers email footer only. Misattributed source drives trust ticket and regulatory inquiry.

Research

Your app had that feature

Synthesis recommends competitor feature users "loved in testing." Video review shows it appeared only in competitor prototype shown same day — misattribution into your roadmap.

Rebrand

The old green button

Users search for controls by retired colour language post-rebrand. Memory content intact; visual source tag lost.

Suite products

Wrong app, right memory

Enterprise user grants calendar access believing it was docs product. Permission model assumes accurate source memory — misattribution creates over-permissioning.

08Ethical risks

Misattribution enables plausible denial and false certainty in disputes — legal and ethical risk when consent source is ambiguous.

Dark patterns benefit from misattribution — users cannot reconstruct where they agreed, only that something felt authorised.

Self-test: Could a user honestly misremember where they saw your most important promise — and would your logs prove them wrong?

10Suggested reading

Browse recommended reading →