# Task Analysis

The systematic study and representation of the actions, decisions, information, tools, and constraints involved in achieving a user goal.

- Type: method
- Domain: Research & behavior
- Level: Intermediate
- Last reviewed: 2026-09-25
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/task-analysis/>)

## What it means

Task analysis investigates how people pursue a goal and decomposes the work into meaningful tasks, subtasks, sequences, decisions, dependencies, and cognitive or environmental demands. It describes work as performed or needed, not merely the steps encoded in an existing interface.

## Why it matters

Products fail when they optimize screens while ignoring the real work surrounding them. Task analysis reveals prerequisites, workarounds, handoffs, failure points, and information needs that can shape workflows, content, automation, and support.

## When to use it

Use it for complex, safety-critical, expert, multichannel, or unfamiliar work and when redesigning an established workflow. A lightweight journey or direct usability test may be enough for a narrow, well-understood interaction.

## How it works

1. Define the user goal, population, context, and boundaries of the work.
2. Gather evidence through observation, contextual inquiry, records, interviews, or activity logs.
3. Identify tasks, subtasks, order, decisions, frequency, tools, information, and exceptions.
4. Represent the work in a hierarchy, flow, or other model and validate it with practitioners.
5. Use the model to identify requirements, risks, simplification opportunities, and research gaps.

## A practical example

A pharmacy team studying prescription transfer maps identity checks, phone calls, insurance lookups, queue handoffs, and exception paths. It discovers that the biggest delay occurs outside the app at a missing-authorization handoff.

## Where it breaks

A model simplifies variable work and may become obsolete as policy or tools change. Self-report misses tacit activity, observation can alter behavior, and decomposition can obscure social coordination or broader goals.

## Common mistakes

- Documenting only clicks in the current interface.
- Assuming the official process matches work as performed.
- Producing a detailed diagram without validating it or using it to make a decision.

## Sources

1. [Task Analysis: Support Users in Achieving Their Goals](<https://www.nngroup.com/articles/task-analysis/>) — Nielsen Norman Group · Professional guidance
2. [Task Analysis](<https://www.usabilitybok.org/task-analysis/>) — Usability Body of Knowledge · Professional body reference

## Related topics

- [Contextual Inquiry](<https://wiki.soroush.uk/topic/contextual-inquiry/>)
- [Field Study](<https://wiki.soroush.uk/topic/field-study/>)
- [Cognitive Walkthrough](<https://wiki.soroush.uk/topic/cognitive-walkthrough/>)
