Scenarios describe the stories and context behind why a specific user or user group comes to your site. They note the goals and questions to be achieved and sometimes define the possibilities of how the user(s) can achieve them on the site.
- A narrative exploring the future use of a product from a user’s point of view
- A scenario is a believable narrative, usually set in the future, of a person’s experience as he or she engages with a product or a service.
- By making design ideas explicit and concrete, the design team can empathetically envision the future ways in which a product is likely to be used.
- The scenario should focus efforts on building culturally meaningful artifacts that augment actual human activity, rather than designing toward technical requirements.
- Scenarios bring personas to life. Both deliverables therefore reinforce the value of the other.
- Scenarios should range from baseline, status quo to high-stress situations with less-than-optimal conditions.
- Scenarios can be written to follow a traditional story arc, with a trigger event, scene, and preconditions, and task resolution with technology that assists and delights.
Scenario Description Swimlanes
A holistic visualization of the activities of multiple actors in a flow of events
- It can benefit any project where several processes or actors have to come together to shape the outcome of the same flow of events.
- Multiple scenario description swimlanes should be created from user research, each focused on its own specific story with the following elements:
- Storyboard lane: Captures the events in a user story using comics, photographs, illustrations, or sketches.
- User Experience lane: This is a flowchart depicting the story with more detail and insight into the process of the user experience.
- Business Process lane: This is the business logic providing the required processes that facilitates the steps of the user experience.
- Tools and Systems lane: Back-end technology that is involved to support user actions and business goals.
- The method visually connects an overarching user story with problems being solved at both a macro perspective and detailed micro view.
Wizard of Oz prototyping. Wizard of Oz prototyping (WOZ prototyping) is a design methodology used in rapid product development to improve the user experience (UX). WOZ prototyping requires developers to create a rudimentary model of the completed pro...
The Pareto principle (also known as the 80/20 rule, the law of the vital few, or the principle of factor sparsity) states that, for many events, roughly 80% of the effects come from 20% of the causes. Management consultant Joseph M. Juran suggested t...
By now UX researchers are familiar with the importance of understanding the usage context of an interface–the physical environment where people are normally using an interface. Remote research opens the door to conducting research that also happens...
Design ethnography is ethnographic qualitative research set within a design context. It delivers results that inform and inspire design processes, for instance service design processes. It offers reference material about people's everyday life; thei...
The Fogg Behavior Model shows that three elements must converge at the same moment for a behavior to occur: Motivation, Ability, and Trigger. When a behavior does not occur, at least one of those three elements is missing. [caption id="attachment_...
Web analytics is the measurement, collection, analysis and reporting of web data for purposes of understanding and optimizing web usage. What we care about - as designers: This process provides a gateway for your organization to become invest...