What is task analysis?
Also called: Hierarchical task analysis, HTA, User task analysis
Task analysis in UX is the process of breaking down how people accomplish a goal into the steps, decisions, tools and information each step needs, so you can design a product around the work as people actually do it.
Updated
What it produces
The output is a structured description of a task: the goal at the top, the subtasks beneath it, the order they happen in, and what triggers each one. Good task analyses also record where people switch tools, wait on someone else, or work around a missing feature. Those are usually the design opportunities.
Hierarchical vs cognitive task analysis
- Hierarchical task analysis (HTA) breaks a goal into subgoals and steps, plus plans that say when each step happens. It comes from Annett and Duncan's work on training design (1967) and is the version most UX teams mean by task analysis.
- Cognitive task analysis focuses on the thinking behind the steps: what people need to know, notice and decide. It suits expert work, such as a support agent triaging a ticket, where the visible steps are simple but the judgement is not.
A worked example
Goal: "Pay a supplier invoice" for a finance user in a B2B tool. A hierarchical breakdown might read: 1. Receive invoice (email or portal). 2. Match it to a purchase order. 3. Get approval (plan: only if over the approval limit). 4. Schedule payment. 5. Record it in the accounting system. Observation shows step 2 happens in a spreadsheet outside the product and step 3 runs through chat messages. Those two steps are where a redesign would save the most time.
How to run one
- Pick one goal and one user group. A task analysis of everything a role does becomes a job description.
- Gather data by watching people do the task: contextual inquiry, screen-shared sessions on their own data, or a diary study for tasks spread over days. Interviews alone miss the steps people do on autopilot.
- Draft the hierarchy, then walk it back through with two or three participants to catch missing steps and wrong order.
- Mark each step with problems you observed: errors, waits, workarounds, tools outside the product.
How it connects to other methods
Task analysis feeds usability test tasks, since you know which steps matter, and it is the input a cognitive walkthrough needs: you can't walk through a task until someone has written down its correct sequence of actions. Journey maps cover a wider span with less step-level detail.
Go deeper
- Contextual inquiry guide
Observe people doing the task in their own environment.
- Usability testing guide
Turn the steps you mapped into test tasks.
- Customer journey mapping
The wider view across a whole journey, above the step level.
- Efficiency interview template
Interview questions about how people get a task done today.
Questions
What's the difference between task analysis and a user journey map?
A journey map follows a person across a whole experience, including feelings and touchpoints outside the product. Task analysis zooms into one goal and breaks it into steps and decisions. Teams often use a journey map to find the painful stage, then a task analysis to redesign it.
Can you do task analysis from interviews alone?
You can draft one, but expect gaps. People skip steps they do without thinking and describe the official process instead of their workaround. Ask them to share their screen and do the task, or follow up with observation, before you design from it.
Run the study, not just the method
Great Question handles recruiting from your own customers, scheduling, incentives, interviews, tests and analysis in one place.
No credit card required.
Related terms
Full glossary- Cognitive walkthrough
A cognitive walkthrough is a usability inspection method where evaluators step through a specific task in an interface and, at each action, ask whether a new user would know what to do, find the control and understand the result.
- Think-aloud protocol
A think-aloud protocol is a usability research method where participants say what they are thinking, looking at and trying to do while they complete a task, so you hear the reasoning behind each action instead of guessing at it.
- Time on task
Time on task is a usability metric that records how long a participant takes to complete a task, from the moment they start to the moment they finish or give up. It's used to measure efficiency and to compare designs or versions.