Method

A journey map records intent, not action

Journey maps organise what a person set out to do. Task analysis describes the work that determines whether they arrive, and it is the level at which design decisions can be defended.

Two people may occupy the same stage of the same journey map, pursuing the same goal, and only one of them completes it. The map is not wrong about either. It is recording something other than the work.

A customer wishes to move money between accounts. On a journey map this is one stage, with a goal and a channel attached to it. Two customers reach it. The first selects a recognised payee from a stored list. The second copies an account number from an email, holds it while switching application, and types it into a field that offers no check against the source. Both intend the same outcome. Only the second is performing a transcription task under a memory load, against a string with no internal redundancy, with no feedback that would reveal a transposed digit before the transfer completes. The journey is identical. The work is not, and the difference in work is the whole of the difference in risk.

This is the limit of the method rather than a fault in it. A journey map records that users abandon a process; it does not establish whether the cause was information unavailable at the point of need, a mode the interface permitted, workload rising at one step, or feedback too weak to prevent a repeated action. Each implies a different fix, and none can be separated from the map alone, because abandonment is an outcome and design operates on causes.

The questions a journey map does answer are real ones, concerning service boundaries, ownership and customer expectation. The difficulty arrives when it is the only model of behaviour a team holds, because the part it sets aside is the part that governs error, workload and reliability.

A task model can be read against a design before release. Where a task requires visual comparison of similar values, transcription error is foreseeable. Where information must be carried across several screens, memory failure is foreseeable. No incident report is required to reach either conclusion, which is why regulated sectors model work: ISO 14971 obliges medical device manufacturers to identify reasonably foreseeable use-related hazard sequences, and a report that users found something confusing does not discharge it.

That burden is no longer confined to regulated industries. A journey map records where somebody intended to go. A task analysis describes what they had to do to get there.

Sources

Annett, J. and Duncan, K. D. (1967). Task analysis and training design. Occupational Psychology, 41, 211–221.

Stanton, N. A. (2006). Hierarchical task analysis: developments, applications, and extensions. Applied Ergonomics, 37(1), 55–79.

ISO 14971:2019, Medical devices — Application of risk management to medical devices, clause 5.4 (identification of hazards and hazardous situations).

Gibbons, S. (2018). Journey Mapping 101. Nielsen Norman Group. The description of what a journey map sets out to record follows this account.

Commentary comparing the scope of the two methods is analytical. No empirical performance claim is made beyond the cited literature.

← All writing