By the end of this topic, you should be able to...
apply task analysis techniques to break down a process into steps and identify the critical points for design improvement.
Guiding Question
How does understanding user needs directly impact the design of products and services?
The Design Intelligence Behind Task Analysis
Before defining the methods, it is essential to understand why task analysis exists as a discipline — what problem it solves, and why it is positioned in the Design Technology syllabus within the broader theme of human factors and usability.
The fundamental problem task analysis addresses is this:
Designers are not their users.
A designer who has spent six months developing a product knows it with an intimacy that no user will ever share. They know what every button does, why every menu exists, where every function is located. This expertise is, paradoxically, their greatest analytical liability — it makes it structurally impossible for them to experience their own product as a first-time or intermittent user would. This cognitive barrier has a name in the human factors literature:
"The curse of knowledge — once we know something, it becomes difficult to imagine not knowing it. In design, this manifests as the expert designer who cannot understand why users find their product confusing."— Heath, Chip, and Dan Heath. Made to Stick: Why Some Ideas Survive and Others Die. Random House, 2007.
Task analysis is the methodological antidote to the curse of knowledge. By breaking a user's activity into its observable, granular constituent steps — and examining each step with systematic rigour — the designer exits their own perspective and enters the user's lived experience of performing the task. The distinction between assumed use and actual use is almost always where design failures originate.
The Theoretical Foundations
Annett and Duncan — The Origin of Hierarchical Task Analysis
The foundational theoretical work underpinning modern task analysis is the Hierarchical Task Analysis (HTA) framework, developed by John Annett and Keith Duncan at the University of Sheffield in 1967 — originally in the context of industrial training design, subsequently extended to product design, human-computer interaction, and safety-critical systems.
Annett and Duncan's core insight was that human activities are not flat lists of sequential actions but hierarchically nested structures of goals and sub-goals:
"The basic assumption of HTA is that tasks can be described in terms of a hierarchy of goals, sub-goals, and operations — where an operation is the basic unit of behaviour performed by a human being in response to a signal from the task environment."— Annett, John, and Keith D. Duncan. "Task Analysis and Training Design." Occupational Psychology, vol. 41, 1967, pp. 211–221.
This hierarchical structure is not merely a cataloguing convenience — it reflects the actual psychological architecture of purposive human action. A user approaching a task does not think in terms of individual physical micro-actions (move finger to button, apply 0.3 N force, release) but in terms of goal-directed plans at multiple levels of abstraction simultaneously.
HTA maps this multi-level structure — and by mapping it, exposes the design implications at every level of the hierarchy, not just at the level of the individual physical interaction.
User Journey Mapping
The following five techniques represent the core analytical repertoire:
What It Is
User journey mapping — also called experience mapping or customer journey mapping — is a task analysis technique that extends beyond the discrete physical/cognitive task to map the full temporal and emotional arc of a user's interaction with a product or service. Unlike HTA and task flow diagrams (which focus on task structure and decision points), journey mapping captures the emotional trajectory of the user — identifying moments of frustration, confusion, satisfaction, and delight alongside the task steps that produce them.
"A journey map is a visualisation of the process that a person goes through in order to accomplish a goal. In its most basic form, journey mapping starts by compiling a series of user actions into a timeline. Next, the timeline is fleshed out with user thoughts and emotions in order to create a narrative."— Gibbons, Sarah. "Journey Mapping 101." Nielsen Norman Group, 9 Dec. 2018.
What Journey Mapping Reveals
Journey mapping is particularly powerful because it identifies the emotional nadir — the point of greatest user distress — which is frequently the design's highest-priority improvement opportunity. In the hospital discharge example above, the medication confusion at home scores -3 (most negative emotional point) and also carries the highest real-world consequence (patient safety risk). The intersection of maximum emotional distress and maximum consequence severity is an unambiguous signal of a critical design improvement opportunity — exactly what the IBO Design Technology Guide (First Assessment 2025) requires students to identify.
Common Errors and How to Avoid Them
Error | Why It Fails | Correction |
Listing task steps without analysis | A numbered list of steps is not task analysis — it is a procedure description. The analysis is the examination of each step for design implications | For each step, annotate explicitly: what could fail here? What is the design implication? Is this a critical point? |
Identifying critical points without justification | Calling a step "critical" without applying the severity × frequency logic is unsupported assertion | Justify every critical point identification: why is failure at this step frequent or consequential? Cite evidence |
Stopping at diagnosis without prescription | The learning objective is to identify "opportunities for improvement" — diagnosis without prescription is incomplete | Every identified critical point must be followed by a specific, feasible design intervention |
Task analysis without a defined user | Tasks are always performed by a specific user type with specific knowledge, context, and constraints — generic task analysis misses critical user-specific failure modes | Define a specific persona (age, knowledge level, context, goal) before beginning the analysis |
Sources
Annett, John, and Keith D. Duncan. "Task Analysis and Training Design." Occupational Psychology, vol. 41, 1967, pp. 211–221.
Card, Stuart K., Thomas P. Moran, and Allen Newell. The Psychology of Human-Computer Interaction. Lawrence Erlbaum Associates, 1983.
Crandall, Beth, Gary Klein, and Robert R. Hoffman. Working Minds: A Practitioner's Guide to Cognitive Task Analysis. MIT Press, 2006.
Gibbons, Sarah. "Journey Mapping 101." Nielsen Norman Group, 9 Dec. 2018, www.nngroup.com/articles/journey-mapping-101.
Heath, Chip, and Dan Heath. Made to Stick: Why Some Ideas Survive and Others Die. Random House, 2007.
International Baccalaureate Organization. Design Technology Guide. International Baccalaureate Organization, 2023. First Assessment 2025.
Norman, Donald A. The Design of Everyday Things. Rev. ed., Basic Books, 2013.
Stanton, Neville A. "Hierarchical Task Analysis: Developments, Applications, and Extensions." Applied Ergonomics, vol. 37, no. 1, Jan. 2006, pp. 55–79.
Linking Questions
To what extent does UCD rely on a strong foundation of ergonomics? (A1.1)
How important is a good understanding of user-centred research methods to ensure effective UCD? (A2.1)
To what extent can the UCD process be influenced by the quality of modelling and prototyping of potential design solutions? (B2.2)
To what extent should a UCD process focus on ensuring inclusive design? (C1.2)
What influence can product analysis and evaluation have on the effectiveness of UCD? (C3.1).