Leveling and Sharpening.

01Overview

Leveling and sharpening (Allport & Postman) describe how stories change in transmission: some details are omitted or flattened (leveling), others are emphasised or distorted (sharpening). Memory is not playback — it is re-authoring with each recall and retelling.

For designers, user interviews about past journeys, NPS verbatims, and stakeholder war stories are all second- or third-hand transmissions. The boring steps vanish. The dramatic glitch grows teeth. Synthesis built on retelling inherits editorial choices users never consciously made.

02Detailed explanation

Serial reproduction studies show predictable drift:

• Multi-step checkout stories level into "it was a hassle" — sharpening one bad moment, losing which step failed.
• Internal launch retros sharpen hero moments and level near-misses that could teach process fixes.
• Support macros level technical detail; users sharpen emotional peak — mismatch in bug reproduction.
• Community lore about product history sharpens scandal, levels routine improvement years.

Leveling reduces dimensionality; sharpening increases salience. Together they produce concise, compelling, partially false memories — optimised for storytelling, not for design specification.

03Why it exists

Memory capacity is limited; narratives require coherence. Leveling drops inconsistent or low-arousal details. Sharpening amplifies what fits the emerging moral or emotional arc.

Each share adds social incentive to sharpen what entertains and level what does not. By the time research hears the story, it has been through several editors.

04Effects on users

Users remember journeys as simpler and more dramatic than telemetry shows — peaks sharpen, waits level away.

Word-of-mouth marketing amplifies sharpening: products become known for one exaggerated trait — "great support" or "always broken" — leveled from nuance.

05Effects on designers & teams

Teams build on sharpened lore:

• Interview synthesis without session replay. Sharpened quotes drive sprints; leveled steps hide fix location.
• NPS deep dives on extremes only. Promoters sharpen delight; detractors sharpen pain — middle levels out.
• Institutional memory loss. Old incidents sharpen into myth; context levels away.
• Case studies for sales. Customer stories sharpen ROI; implementation friction leveled.

06Practical takeaways

• Triangulate stories with artefacts. Logs, recordings, analytics alongside retellings.
• Ask step-by-step reconstruction. Walk timelines slowly to reduce leveling of middle steps.
• Version institutional memory. Write post-mortems before lore sharpens them.
• Tag sharpened themes in research repos. Note when multiple users sharpen the same detail — signal, not gospel.
• Design for peaks you want sharpened. If memory will exaggerate endings, engineer good endings.
• Correct lore actively. When community memory sharpens false scandal, publish leveled factual timelines.

07Design examples

08Ethical risks

Acting only on sharpened horror stories can over-correct for rare events while leveled chronic harm persists — inequitable prioritisation.

Sales sharpening customer outcomes sets expectations users remember — disappointment when leveled reality arrives is a trust debt.

Self-test: Which product story does your team repeat — and what boring detail might leveling have removed?

09Related biases