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
- Discipline
- Participatory, Design & Futures
- Loss type
- Vestigial
- Stage
- Definition, Design
- Data
- Qualitative
- Effort
- Days
Steps
- Write problem scenarios describing current practice from field data.
- Extract claims about current practice and its tradeoffs.
- Write activity scenarios describing new ways of working.
- Elaborate into information and interaction scenarios for the proposed design.
- Derive usability specifications and test scenarios from them.
- 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