---
name: workflow-analysis
description: Use when asked to examine how work actually flows through a process or organization — workflow mapping, time analysis, data-flow analysis, roles/responsibilities, decisions, controls — as the process-level counterpart to task-analysis's single-task focus.
---

# Workflow Analysis

Workflow Analysis (also called Process Analysis) is a systematic
examination and evaluation of the sequence of activities, tasks, and
information flow within a system, organization, or process — aiming to
understand how work happens, identify inefficiencies and opportunities,
clarify roles and responsibilities, and optimize the workflow. Where
[[task-analysis]] typically zooms into one task, workflow analysis zooms
out to the whole process a task sits within.

## Typical aspects

- **Workflow mapping** — represent the process, context, and
  relationships using flowcharts, diagrams, or process maps illustrating
  the sequence of tasks, decision points, and data flow (see
  [[flowchart]]).
- **Task analysis** — examine each activity in detail: its purpose,
  inputs, outputs, and required resources (see [[task-analysis]] for the
  general technique this draws on at the individual-task level).
- **Time analysis** — measure the time each activity takes, via
  observation, interviews, or historical data, to identify time-
  consuming steps and bottlenecks.
- **Data flow analysis** — analyze how data moves through the process:
  its sources, how it's transmitted, how it's used, and where problems
  occur.
- **Roles and responsibilities** — examine who's involved and how,
  ensuring clarity and accountability, understanding handoffs between
  roles, and identifying confusion or duplicated effort (see
  [[responsibility-assignment-matrix]] for a tool that formalizes this).
- **Decisions** — analyze the decision-making process: criteria, rules
  or guidelines followed, and dependencies or conditions influencing
  decisions.
- **Controls** — examine mechanisms for evaluating the workflow itself:
  customer feedback, employee suggestions, and performance metrics that
  drive improvement.

## Common pitfalls

- **Mapping the workflow as documented, not as actually performed** —
  the official process description and what people actually do under
  time pressure or exceptions often diverge; validate the map against
  real practice.
- **Ignoring handoffs between roles** — many workflow inefficiencies live
  specifically at the boundary between one person's/team's
  responsibility and the next, not within any single step.
- **Time analysis without identifying *why* a step is slow** — measuring
  duration alone doesn't explain whether the bottleneck is a resource
  constraint, an unclear decision rule, or a genuinely necessary review.
- **No feedback/control mechanism** — analyzing and improving a workflow
  once, with no ongoing way to detect when it drifts or degrades again.

## Learn more

- [[task-analysis]] for the single-task-level technique workflow analysis draws on.
- [[flowchart]] for a general-purpose diagramming technique used in workflow mapping.
- [[responsibility-assignment-matrix]] for formalizing roles and responsibilities uncovered during analysis.
