experience-design

Experience Design — fix the felt moment, not the metric

Engineers optimise the average and the total. Humans remember the peaks, the end, and how uncertain they felt. The cheap, high-leverage fix is almost always in the feeling of a moment, not in the metric that describes it.

The principle

The number ("8 minute wait," "3 second load," "5 form fields") is not the experience. Attack the experience directly:

• Uncertainty hurts more than delay. Not knowing how long is worse than waiting a known amount. A progress bar, an ETA, or a visible queue position can beat an actual speed-up — at a fraction of the cost.
• Occupied time feels shorter than idle time. People aren't angry about waiting; they're angry about waiting with nothing happening. Give the wait a purpose or a view and the same duration feels fine.
• People judge an experience by its peak and its end (peak-end rule), not its average. One great moment and a strong finish outweigh a mediocre middle. Engineer a peak; never let it end on a low.

Canonical examples (steal these patterns)

• The Uber map. Showing the car moving toward you on a map didn't make it arrive faster — it killed the uncertainty. The anxiety, not the wait, was the problem. (Same insight: arrivals/departures boards, "your food is being prepared," package tracking.)
• The airport baggage walk. An airport got complaints about waiting at the carousel. Instead of speeding up the bags, they routed arriving passengers on a longer walk to the carousel — so the bags were already there when people arrived. Total time up, complaints down: idle waiting became occupied walking.
• Progress bars and "almost there." Showing progress (even slightly padded) makes the same wait tolerable, because it removes uncertainty and occupies attention.

How to apply

1. Map the journey as emotions, not steps. Walk it as the customer and mark where they feel anxious, ignored, uncertain, or bored — not where the process is technically slow.
2. Attack uncertainty first (cheapest win). Wherever someone is waiting blind, add visibility: an ETA, a status, a progress indicator, a "we've got it" acknowledgement. This usually beats making the thing actually faster.
3. Occupy idle time. Turn dead waiting into something with a view, a purpose, or a small useful action.
4. Engineer the peak and the end. Add one genuinely good moment, and make sure the experience finishes well (a thank-you, a confirmation, a small delight) — that's what gets remembered and retold.
5. Compare against the metric-fix. Always show the user the trade: "Reducing the actual wait costs $X and weeks. Removing the uncertainty costs a status indicator. Try the feeling first."