---
name: task-analysis
description: Use when asked to break down a complex task or activity into its component steps — the identify/collect/decompose/sequence/document/evaluate/improve process — as the general umbrella technique behind more specific methods like hierarchical-task-analysis and cognitive-task-analysis.
---

# Task Analysis

Task analysis is a systematic method for breaking down complex tasks or
activities into smaller, more manageable steps — studying and
documenting the actions, processes, and cognitive activities required to
complete a specific task or achieve a particular goal, to identify
bottlenecks, errors, or inefficiencies and find ways to optimize.

## General process

1. **Identify the task** — select a specific task or activity to
   analyze: a complex work task, a user interaction with a software
   application, or any other goal-oriented activity.
2. **Collect information** — observe individuals performing the task,
   interview subject matter experts, or consult existing documentation.
3. **Decompose the task** — break it down into smaller steps or
   subtasks, starting from a high-level view and decomposing into more
   detailed actions; each step should be discrete and meaningful.
4. **Sequence the steps** — arrange them in the order they need to be
   performed, considering dependencies and relationships to ensure a
   logical flow.
5. **Document** — create a detailed record, in writing or with visual
   aids like flowcharts, diagrams, or a [[hierarchical-task-analysis]]
   diagram.
6. **Evaluate** — identify missing steps, redundant actions, or unclear
   instructions; refine with input from experts and stakeholders.
7. **Improve** — optimize performance, reduce errors, or simplify
   processes, through redesign, training, or automation.

## Specific techniques within task analysis

This general process is the umbrella several more specific, named
techniques sit under, each suited to a different kind of task or
research question:

- **[[hierarchical-task-analysis]]** — decomposes a task into a
  hierarchical structure of subtasks, actions, and operations.
- **[[cognitive-task-analysis]]** — focuses specifically on the mental
  processes and decision-making behind a task, not just its observable
  steps.
- **[[workflow-analysis]]** — examines a task in the context of a
  broader process, including roles, handoffs, and data flow.
- **[[critical-incident-technique]]** — gathers detailed accounts of
  specific significant events rather than analyzing routine task
  execution.
- **[[diary-study]]** — captures how a task or experience unfolds over
  time, from the performer's own ongoing record.

## Common pitfalls

- **Stopping at a high-level decomposition** — a task analysis that
  never gets past broad steps misses the detail needed to actually spot
  bottlenecks or design improvements.
- **Skipping stakeholder validation** — an analysis built purely from
  documentation or observation, without checking it against the people
  who actually perform the task, can miss real-world exceptions and
  workarounds.
- **Treating the analysis as a one-time artifact** — a task, and how
  it's actually performed, tends to drift over time; an analysis that's
  never revisited goes stale.
- **Choosing the wrong specific technique for the question** — a
  process-flow question calls for [[workflow-analysis]], a mental-
  process question calls for [[cognitive-task-analysis]]; picking a
  technique mismatched to the actual question wastes effort.

## Learn more

- [[hierarchical-task-analysis]], [[cognitive-task-analysis]], [[workflow-analysis]] for the more specific techniques built on this general process.
- [[critical-incident-technique]], [[diary-study]] for adjacent qualitative research methods often used alongside task analysis.