Gumshoe · Method reference

Task analysis

Break a goal into the concrete steps, sub-tasks, and decisions people perform to accomplish it.

Conceptual illustration of task analysis.
Effort
Medium
Participants
Needed
Remote friendly
Yes
Evidence / output
Direct user

What it is

A systematic breakdown of how users accomplish a goal: the tasks, sub-tasks, sequence, decisions, and information needed at each step, often as a hierarchical task analysis.

When to use it

During Immerse and Synthesize, when you need to understand real work in detail before redesigning it.

Why (value)

Reveals the true complexity of a task, exposes unnecessary steps and information gaps, and grounds design in how work is actually performed.

How to run it

  1. Define the top-level goal.
  2. Observe or interview users performing the task.
  3. Decompose the goal into tasks and sub-tasks.
  4. Capture sequence, decisions, and information needs.
  5. Analyze for redundancy, friction, and opportunity.

Inputs and outputs

  • Inputs: Access to users performing the task, or reliable records of it.
  • Outputs: A task hierarchy or flow with friction points and opportunities.

Time and effort

Medium. Observation plus decomposition.

Evidence and limitations

Strongest when built from observed behavior (direct-user); a task analysis written from assumption reflects how the team imagines work, not how it is done. See Evidence and limitations.

Tips and pitfalls

  • Observe real work rather than assuming the steps.
  • Capture decisions and information needs, not just actions.
  • Watch for hidden workarounds people have normalized.

Variations

Hierarchical task analysis, cognitive task analysis, task-flow diagrams.

Need help planning research or facilitating this method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Explore related methods

  • Task flow diagramming — Diagram the single sequence of steps to complete one task, without user-specific branching.
  • Mental model diagramming — Map how people think about a task and align your features against those mental models to find gaps.
  • Use cases — Specify the steps of an interaction between a user and system, including alternate and error paths.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.