What is task analysis in UX?
Task analysis in UX is the study of how people complete a goal, broken down into the individual steps, decisions and tools involved from start to finish.
also calledhierarchical task analysis · task decomposition · task breakdown
Ask someone to describe how they make a cup of tea and you will get a sentence. Watch them do it and you will find twenty small steps, a few decisions and a surprising number of workarounds. Task analysis is the habit of watching closely and writing all of that down before you design anything.
- Task analysis breaks a user goal into its real steps, decisions and tools.
- Observe people doing the task, since they forget shortcuts and workarounds when describing it.
- Include detours, errors and interruptions, not only the happy path.
- Use results to remove, merge or reorder steps and to feed flows and test tasks.
What a task analysis actually produces
The output is a structured description of how a goal gets done. You start with a top-level goal, such as 'renew a car insurance policy', and split it into sub-tasks: find the policy number, compare offers, update details, pay. Each of those can break down further.
The point is to see what people really do, in order, including the awkward parts: switching between a paper letter and a website, waiting for an email, asking a colleague. A good analysis shows where effort is spent and where mistakes are likely.
How to do one, step by step
- Pick one specific goal and the user group performing it. 'Using our app' is far too broad.
- Collect information through observation, interviews and contextual visits. Watching beats asking, because people forget their own shortcuts.
- List the main steps in order, then split each into smaller pieces until you reach actions you can observe.
- Note the details at each step: what information is needed, which tools are used, what can go wrong, how long it takes.
- Draw it as a diagram or an indented outline so others can read it quickly.
- Check it with real users and fix what you got wrong.
Two flavors worth knowing
Hierarchical task analysis breaks a goal into a tree of sub-goals and the plans that connect them, and is common in more formal or safety-critical settings. Cognitive task analysis goes deeper into the thinking behind the actions: what people notice, remember and decide.
The easy version is often enough. A sticky-note wall that lays out steps left to right, with problems marked in a different color, can teach a team a surprising amount in an afternoon.
How the results are used
Once you see the real task, design questions get sharper. Steps that nobody needs can be removed, steps that always go together can be combined, and information people hunt for can be placed where they need it.
The analysis also feeds other work. It supplies the raw material for user flows, journey maps and usability test scripts. When you design a test task, you know what a realistic one looks like.
Where it goes wrong
Analyzing the task as your system imagines it rather than as users do is the classic miss. Another is stopping at an idealized path. Real tasks have interruptions, errors and detours, and those are where design help is needed most.
It can also be overdone. You do not need a ten-page tree for a one-click action. Match the depth of analysis to how complex or risky the task is.
Task analysis: your questions, answered
What is task analysis in UX?
It is a research method for understanding how people accomplish a goal by breaking it down into the steps, decisions and resources involved. It reveals where effort goes and where errors happen, so designers can simplify the process or support it better.
How do you perform a task analysis?
Choose a specific goal and user group, observe real people doing it, and record each step in order. Break large steps into smaller ones, note tools, information needs and problems, and then check your description with users. Present it as a diagram or outline.
What is hierarchical task analysis?
It is a formal approach that splits a main goal into sub-goals and then into actions, usually shown as a tree. Each level also includes a plan describing in what order or under what conditions the parts are done.
What is the difference between task analysis and a user flow?
Task analysis describes how people really complete a goal, including steps outside your product. A user flow maps the path through your own product or design. The first informs the second, so analysis usually comes before drawing flows.
When should you do a task analysis?
Do it early, before designing a new workflow, or when you are trying to understand why an existing process is slow or error-prone. It is especially useful for complex, repeated or high-risk tasks such as medical, financial or technical work.
More quick answers
Is task analysis qualitative?
Mostly yes, since it relies on observation and interviews, though you can add timing and error counts to make parts of it quantitative.
What is the difference between task analysis and contextual inquiry?
Contextual inquiry is a way of gathering data by observing people in their own setting. Task analysis is how you structure what you learned.
What is a user flow?
It is a diagram of the path a person takes through a product to complete a goal, including decision points.
How many people should you observe?
A small number, often a handful per user group, will reveal most common steps and problems. Add more if groups differ a lot.
What tools help with task analysis?
Sticky notes, whiteboards and diagramming tools are enough. The value comes from the observation, not the software.
Contextual inquiry in UX is a research method where you observe and question users in their own environment while they do real work with a product.
A user flow in UX is a diagram showing the steps a person takes through a product to complete a task, including decisions and possible detours.
A user journey map in UX is a visual timeline of the steps a person takes to reach a goal, showing their actions, thoughts, emotions and pain points.
Usability testing in UX is a method where you watch real people try to complete realistic tasks with a product to find where they struggle.
User research in UX is the practice of studying people who use or might use a product, to understand their needs and behavior so design rests on evidence.
Found this useful? A GitHub star helps other designers find it.