What it is
Structured descriptions of how an actor interacts with a system to achieve a goal, detailing the main success path plus alternate and exception flows. More formal and complete than a scenario.
When to use it
During Synthesize, when interactions are complex enough to need explicit main, alternate, and error flows.
Why (value)
Ensure edge cases and failure paths are considered, not just the happy path, and give development a precise interaction spec.
How to run it
- Identify the actor and their goal.
- Describe preconditions and triggers.
- Write the main success flow step by step.
- Add alternate flows and exception handling.
- Note postconditions and validate for completeness.
Inputs and outputs
- Inputs: Actors, goals, system behavior, and interaction rules.
- Outputs: Documented use cases with main, alternate, and exception flows.
Time and effort
Medium. More rigorous and slower than scenarios.
Evidence and limitations
A specification artifact, not user research. It documents intended behavior, not validated user need. See Evidence and limitations.
Tips and pitfalls
- Always cover alternate and error flows, that is the point.
- Keep them at interaction level, not UI-detail level.
- Do not confuse them with looser scenarios.
Variations
Casual vs. fully-dressed use cases, use-case diagrams.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Scenarios — Narrate how a specific person accomplishes a goal so the team designs for realistic context.
- Task flow diagramming — Diagram the single sequence of steps to complete one task, without user-specific branching.
- User stories — Capture a need from the user's perspective in a small, buildable increment.
