Gumshoe · Method reference

Task flow diagramming

Diagram the single sequence of steps to complete one task, without user-specific branching.

Conceptual illustration of task flow diagramming.
Effort
Low
Participants
Not required
Remote friendly
Yes
Evidence / output
Inference

What it is

A linear diagram of the steps required to complete a specific task, typically the canonical path, used to understand or design a single task’s sequence. Distinct from user flows, which model different users’ varied paths.

When to use it

During Synthesize and Prototype, to analyze or design a specific task’s steps.

Why (value)

Clarifies the exact sequence for a task, exposes redundant or missing steps, and grounds interaction design in the real procedure.

How to run it

  1. Define the task and its start/end.
  2. List the steps in order.
  3. Note required inputs and system responses.
  4. Identify friction and unnecessary steps.
  5. Redesign the sequence to reduce effort.

Inputs and outputs

  • Inputs: A defined task and knowledge of its procedure.
  • Outputs: A task flow diagram of the step sequence.

Time and effort

Low. An hour per task.

Evidence and limitations

A procedural model; whether it matches reality depends on grounding it in observed behavior (task analysis). See Evidence and limitations.

Tips and pitfalls

  • Keep one task per diagram.
  • Distinguish task flows (one path) from user flows (many).
  • Base it on how the task is really done.

Variations

Linear task flows, swimlane task flows.

Need help choosing and applying a 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

  • User flow diagramming — Diagram the paths a user takes through a product to reach a goal.
  • Task analysis — Break a goal into the concrete steps, sub-tasks, and decisions people perform to accomplish it.
  • 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.