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.
Contextual inquiry is a semi-structured interview method to obtain information about the context of use, where users are first asked a set of standard questions and then observed and questioned while they work in their own environments. Four pri...
Testing of prototypes, products, or interfaces by users of a system in design development This gauges human expectations against a designed artifact, determining whether something is useful, usable, and desirable. Testing should collect per...
A storyboard is a graphic organizer in the form of illustrations or images displayed in sequence for the purpose of pre-visualizing a motion picture, animation, motion graphic, user interactions, or interactive media sequence. A visual nar...
The usability of a system is improved when its status and methods of use are clearly visible. The more visible functions are, the more likely users will be able to know what to do next. Incontrast, when functions are "out of sight," it makes the...
Hooked template, was represented through the Hooked book, and it helps us to find ways to Build Habit-Forming Products. A hook has four parts: Trigger: External & Internal. Need to shift from external to internal triggers over time. ...
The cognitive walkthrough is a usability evaluation method in which one or more evaluators work through a series of tasks and ask a set of questions from the perspective of the user. The focus of the cognitive walkthrough is on understanding the syst...