Experience spans the whole arc before, during, and after use
Aliases: whole journey · expectation and memory · peak-end rule
What it is
Experience is not the time between opening and closing the app: users arrive carrying expectations (ads, word of mouth, memories of past versions) and leave carrying evaluation and memory (will they recommend it, come back, tell friends). The interface is only the middle segment of that timeline—expectation sets the interpretive frame, and memory decides whether they return.
Why it happens
Remembered evaluation is not the average of the whole arc: memory samples peaks and endings (the peak-end rule), so a flow that ends in frustration drags down the whole recollection while mediocre middles are heavily discounted. Expectation works through comparison—the same performance reads as delight above expectation and disappointment below it. Neither the before nor the after lives inside the interface, yet both decide how the interface experience gets told and whether it repeats.
Studying it
Design studies across all three segments: measure pre-use expectation (from claims and others' opinions), in-use momentary ratings and critical-incident logs, and post-use recalled evaluation plus peak/end events and behavioral intent. Diary studies capture day-scale evolution; delayed follow-ups measure what memory keeps after filtering. Diffing the momentary rating curve against the recalled evaluation locates the direction of memory distortion.
Where it stops holding
"Before and after matter" does not make the interface optional: the middle is where peaks and endings happen, and a bad middle yields no good ending. Peak-end effects are unstable in small single-task samples and weight differently across functional and entertainment contexts. For tool products, the "ending moment" is usually the instant of flow completion—easier to own than in consumer products.
Applying it
- Map the full experience: from the moment the need arises to a week after completion, tagging every touchpoint.
- Design the ending of every critical flow: a completion screen with a clear result, next step, and saved state—never let the flow die at a system toast.
- Audit expectation sources: marketing claims, onboarding copy, and notification wording all set the frame; align promises with real capability.
- Collect both momentary ratings and two-week-later recall; use the gap to find what memory inflated or erased.