Scenario-Based Design

Description

Uses concrete narrative scenarios of use as the central design representation from analysis through evaluation, paired with claims analysis.

Scenario-based design treats stories of people using a system as the primary design artefact. It moves through problem scenarios (current practice), activity scenarios, information and interaction scenarios, and finally usability-test scenarios, each paired with claims about consequences. The treatise presents claims analysis as born within this approach. Scenarios keep design grounded in specific activity, are accessible to non-specialists and expose assumptions. Contemporary practice retains user stories and scenarios as fragments, but rarely uses them as a systematic, staged method linked to claims, which is why the method is vestigial.

Attributes

Loss type
Vestigial
Effort
Days

Steps

  1. Write problem scenarios describing current practice from field data.
  2. Extract claims about current practice and its tradeoffs.
  3. Write activity scenarios describing new ways of working.
  4. Elaborate into information and interaction scenarios for the proposed design.
  5. Derive usability specifications and test scenarios from them.
  6. Iterate scenarios and claims as evaluation results come in.

Sources

  • Lost Methods in UX — A Complete Treatise (Gopinath)
  • Carroll JM (Ed) (1995) Scenario-Based Design: Envisioning Work and Technology in System Development
  • Rosson MB & Carroll JM (2002) Usability Engineering: Scenario-Based Development of Human-Computer Interaction

Also known as

  • SBD
  • Scenario-based development

Categories

  • Design
  • Participatory, Design & Futures