Confabulation.

01Overview

Confabulation is the production of fabricated, distorted, or misinterpreted memories or explanations — without intent to deceive and often with full sincerity. The person experiencing confabulation does not know the story is constructed. It feels like recall. It functions like insight.

For designers, confabulation is the hidden tax on "why did you do that?" research. Users post-rationalise clicks, skips, purchases, and abandonments with narratives that fit their self-image and cultural scripts. The narrative is articulate. The causal chain is fiction. Teams build roadmaps on autobiographies that never happened.

02Detailed explanation

Confabulation appears whenever the brain must explain behaviour whose causes were automatic, forgotten, or never consciously represented:

• Participants describe deliberate comparison shopping after a single-click impulse buy — the story preserves the identity of a careful decision-maker.
• Users attribute abandoning a form to "privacy concerns" when eye-tracking shows they never read the privacy section — a respectable reason substitutes for confusion or fatigue.
• Stakeholders reconstruct project history so the successful outcome looked inevitable — confabulation at team scale.
• Split-second aesthetic judgments become elaborate design rationales in exit interviews.

Confabulation overlaps with narrative fallacy but emphasises sincerity and amnesia about the gap. The user is not lying to you. They are lying to themselves with your microphone open.

03Why it exists

Coherent self-narrative is a social and cognitive requirement. "I don't know why I did that" is uncomfortable. The brain supplies reasons from available cultural templates — price sensitivity, trust, time pressure — whether or not they drove the act.

Interfaces rarely leave memory traces of micro-decisions. Without traces, explanation becomes invention. The more you ask for reasons, the more polished the fiction becomes.

04Effects on users

Users believe their confabulations. They will argue passionately for reasons that telemetry contradicts — not because they are difficult, but because introspection accessed a narrative module, not a log file.

They also confabulate future intent: "I would definitely use feature X" becomes a prediction dressed as preference, built from who they want to be in the interview room.

05Effects on designers & teams

Research practice often amplifies confabulation:

• Why-heavy interview guides. Sequences of "why?" pressure participants to produce causal chains where none exist.
• Treating quotes as mechanisms. A vivid line in a report becomes "the reason" for churn without behavioural corroboration.
• Retrospective journeys. Asking users to reconstruct multi-week flows produces chronological stories with invented decision points.
• Ignoring null introspection. "I just clicked" gets prodded until a better quote emerges — usually a confabulation.

6Introspective view

Look inward. Users invent plausible reasons for behaviour they can't actually explain, so 'why' answers need scrutiny.

From an introspective perspective, ask how Confabulation may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.

07Practical takeaways

• Lead with behaviour, not rationale. Observe tasks first; ask "what were you thinking?" only where behaviour is ambiguous.
• Use concurrent think-aloud, not only retrospective. Narratives formed during action are closer to process — still imperfect, but less polished.
• Triangulate three sources. Self-report, interaction data, and context (device, time, interruptions) before elevating a quote.
• Ask for specifics, not philosophies. "What did you look at on this screen?" beats "Why don't you trust us?"
• Design for observed failure modes. Ship fixes for what users do, not only what they say they do.
• Train teams on sincere fiction. Confabulation is a feature of cognition, not bad faith from participants.

08Design examples

09Ethical risks

Building for confabulated reasons can harm users whose real barriers — literacy, disability, economic stress — never appear in sanitised interview narratives.

Surveys that force causal attributions invite confabulation and then weaponise the results against users — "you said you cared about privacy" when the UI never tested that claim.

Self-test: Which favourite user quote from your last study would collapse if you checked session replay?

10Related biases