You have transcripts, clips and a wall of notes from a dozen people. On their own they are anecdotes. Mapping turns them into structure by laying them along the one axis the research lost: time.
Put the order back and the gaps surface — the four-day wait nobody owns, the step where the user has to leave your product to get a number out of a colleague. Neither of those is visible while the findings sit as a list of quotes.
Two tools at two altitudes. A journey map covers the arc of a goal across channels and weeks. A task analysis covers one task, step by step. Choosing the wrong altitude is the common error: you cannot fix a broken form with a journey map.
Journey Mapping
A journey map lays out the stages of a goal as the user experiences it — their goal, not your funnel. Renewing the insurance. Getting a new starter productive. It runs from the moment they realise they need something to the moment they are finished, which is almost always wider than your product's edges.
For each stage, record four things: what they do, what they are trying to find out, how they feel, and which channel they are in. The feeling row does two jobs. It marks where trust breaks, which explains drop-off that click data cannot, and it marks the few moments people genuinely value, so nobody redesigns those away while tidying the rest.
Mark clearly which parts came from research and which you assumed. An unlabelled map made in a workshop becomes the team's shared belief within a week, and by then nobody remembers that no user was involved.
- Journey Mapping 101 — article
- Customer journey map explained: Everything you need to know — article
Task Analysis
Take one task — add a user, refund an order, upload a payslip — and write down every step needed to finish it, including what the person must already have in hand.
Number the steps, then mark each: does the system supply what is needed here, or does the user? Every step where they must bring something in — a reference number, a file in the right format, someone else's approval — is a place the task stalls, and a stall reaches your analytics as silence.
Mark the decision points too, and beside each write what the person is choosing between and what tells them which way to go. A branch with nothing to inform it is a guess.
Count the steps before and after a redesign. It keeps the conversation honest when a proposal tidies one screen and quietly adds two steps elsewhere.
The measure is not how tidy the flow looks. It is how many ways there are to fail on the way through, and every step you remove takes one of them with it.