---
name: User Journey & Friction Mapping
description: Draws an end-to-end user journey map, annotates the emotion curve and the experience friction at each stage, and turns the worst drop-offs into tested, conversion-lifting recommendations grounded in real research and analytics. A structured read of where users struggle, why, and what to try next — with every inference labelled as such. For UX, product, and CX teams.
audience: UX · product · CX
---

# User Journey & Friction Mapping

## What this is

A method for mapping a user's path across stages — awareness, onboarding, first value, habitual use, renewal — and overlaying two things at each step: the emotion curve (where confidence rises and where it dips) and the concrete friction (the click that fails, the field that confuses, the wait that erodes trust). It grounds those overlays in whatever real evidence exists — session recordings, funnel analytics, support tickets, interviews — and it names the highest-leverage friction points, then proposes changes framed as hypotheses to test, not fixes to assume.

## What this is NOT

Not a substitute for real user research. Emotion curves and friction points are hypotheses: where analytics or research back them, that is stated; where they are inferred from heuristics or a single data point, they are labelled inference, not fact. Recommendations are proposals to be validated by testing, never presented as guaranteed conversion lifts. A journey map drawn from the team's imagination alone is the team's self-image with arrows on it.

## Method

1. **Frame the journey and the goal.** Define the persona, the trigger that starts the journey, and the single conversion or outcome each stage should move toward — a map without a goal ranks nothing.
2. **List the stages as the user experiences them.** Use the user's mental model and vocabulary, not the internal funnel names; misnamed stages hide the friction between them.
3. **Attach evidence to each stage.** Pull real signal — funnel drop-off, recordings, tickets, interview quotes — and cite it per stage; where no evidence exists, mark the stage as inferred.
4. **Plot the emotion curve.** Note where confidence rises and where it dips, tying each inflection to an observed behaviour or a labelled hypothesis, never to a guessed mood.
5. **Catalogue the friction.** For each dip, name the specific obstacle — cognitive load, dead end, latency, unclear copy, forced step — and classify it by type so patterns surface.
6. **Rank by leverage, not by count.** Score friction points by drop-off size × traffic × fixability, and surface the one or two that actually gate conversion, not a checklist of every imperfection.
7. **Propose breakthrough changes as hypotheses.** For each top friction, write a concrete change and the metric it should move, phrased as a prediction to test — reduce steps, remove the dead end, rewrite the ambiguous label.
8. **Define the test and the re-read.** Specify how each change will be validated (A/B, usability session, funnel watch) and schedule a re-map on the same basis once evidence returns.

## Quality bar

Stages use the user's vocabulary · every emotion and friction claim is backed by cited evidence or labelled inference · friction is typed and ranked by drop-off × traffic × fixability · recommendations are hypotheses with a target metric, never guaranteed lifts · a validation test is named for each · the map is re-read on a stable basis after evidence returns.

## Guardrails & escalation

This is a design-and-research method, not a promise of outcomes — no recommendation is guaranteed to convert; each is a hypothesis for testing. It does not replace real user research: findings drawn without analytics or user input are marked as inference and treated as low-confidence. Accessibility friction surfaced here is design-level and routes to a proper accessibility pass; decisions involving personal data or consent in the journey route to the relevant privacy and legal owners.

## References

- Catalogue: https://edwson.com/consumer-design-system.html · Contracts: https://edwson.com/cds/components.json · Agent brief: https://edwson.com/cds/AGENTS.md
- Related within this kit: the dark-pattern & trust audit (trust dips on the emotion curve), the A/B testing & personalization skill (how to validate the proposals), and CDS design-review.