A method for decomposing user activities into goals, tasks, subtasks, steps, decision points and required resources so that system interfaces, workflows, training, or automation can be designed to support actual user work patterns.

Principle

Explicitly modelling the hierarchical structure of goals, actions, and decisions reveals dependencies, handoffs, and critical decision points; making these elements explicit enables targeted redesign, automation, or support for error‑prone steps.

Demonstration

Illustrative scenario — Situation: Library staff report delays when processing interlibrary loans. Recognition: Analysts perform a hierarchical task analysis of the loan workflow, documenting goals, substeps, decision rules, and exceptions. Action: Designers simplify redundant steps, add status cues at critical decision points, and automate routine checks. Consequence: Processing becomes faster and error rates at previously ambiguous steps decline, while training materials are updated to reflect clarified procedures.

Misapplication

Listing surface actions without linking them to user goals, alternatives, and contextual triggers. The semantic error is treating a flat checklist as a task analysis; this misses decision logic and exception handling that determine real user behaviour and system requirements.

Consequence

Task analysis produces precise requirements for interfaces, automation, and training and can reduce errors and inefficiencies; conversely, overly prescriptive decompositions can freeze workflows, reduce adaptability, and obscure creative or emergent work practices.

Reversal

For open‑ended, creative, or exploratory activities where goals and steps are fluid and contingent, strict hierarchical decomposition may misrepresent behaviour and impede support; in such cases, descriptive or situated approaches (e.g., contextual inquiry) are preferable.

Boundary

Clearly within: hierarchical decomposition of routine, repeatable tasks with identifiable steps and decision points. Boundary case: multi‑actor collaborative tasks where responsibilities shift dynamically—analysis may require role maps and communication flows. Clearly outside: high‑level strategic objectives that are not decomposed into operational steps.

Semantic Tension

Efficiency/Standardization ↔ Flexibility/Adaptability — the desire to optimize and standardize tasks can conflict with the need to accommodate variation, improvisation, and context‑sensitive decisions in actual practice.

Synthesis

Task analysis is most valuable when it exposes decision logic and exceptions rather than merely enumerating actions; combining hierarchical decomposition with contextual observation preserves both operational clarity and real‑world variability.