As the team transitions from interviewing and collecting insights from users, scenarios prepare the team to launch deeply into the design stage begins. A written description of a user's process, scenarios can sound a little bit like this: "she needed this to understand that, so she checked here and saved it in that file". With real names and tasks defined, scenarios illuminate the details of an ideal, improved workflow.

Method

Usually 2 or 3 paragraphs in length, scenarios represent the outcome of interviews with primary users, and can activate a meaningful discussion amongst the team about what we want the system to be able to do for that primary user. After collaborating to clarify those details, scenarios serve as a shared frame of reference for the team's storyboarding or visioning discussions. Scenarios can also be used to test the usability of the product, in the prototyping stages or in the lab after wireframes are prepared.

Results

This scenario excerpt integrates three different parts of a site with the goal of developing a user's interest in donating money to a clinical research institution:

He sees a Clinical Trial that his brother would be eligible for, and he moves to "Email this Clinical Trial to a Friend". This pulls up a separate form page wherein he emails his brother about the clinical trial with a note attached. When that email form closes, he is back on the Clinical Trial page. He looks it over, and finds a descriptive preview of "research volunteers". He realizes that, even if his brother doesn't qualify for the study, he would like to help out. He jots the (800) number to call and find out, and then follows the link to "Advancing Research".

Timeframe and Preparation

Assuming the user research is completed, the scenario design process is, in effect, the transition from research and analysis to design.  It can, therefore, take a few weeks to get it absolutely straight and agreed-upon by the team.

Additional Readings

About Face 2.0: The Essentials of Interaction Design, Alan Cooper and Robert Reimann (2003).  Amazon carries it.

Scenario-based Design: Envisioning Work and Technology in System Development, Edited by John Carroll (1995).  Amazon links to sellers of used copies.