Setting the vision: Scenarios and Design requirements.
In this chapter , you learn that different product teams my encounter a serious hurdle soon after they begin a new project. There needs to be a connection between the research and the product design. There is the first half of a process for bridging this research-design gap, here they are
· Developing stories or scenarios as a means of imagining ideal user interactions
· Using those scenarios to extract design requirements.
· Using these requirements in turn to define the product’s fundamental interaction framework.
· Filling in that framework with ever-increasing amounts of design detail
One powerful creative method is Narrative and is a very effective way to share good ideas among team members and stakeholders. Not only that but narrative lends itself to effective visual depictions of interactive products.
There are Scenarios and use cases are both methods of describing the user’s interaction with a system. There are different functions which is Goal-Directed scenarios. They is an iterative means of defining a product’s behavior. The other is Use cases, which are a technique based on exhaustive descriptions of the system’s functional requirements,
The scenario based design is used to describe a “method of design problem solving by concretization: using a specific story to both construct and illustrate design solutions. “This consists of an environmental setting and also includes agents or actors who are abstracted stand-ins Persona-based scenarios are using a product or service to achieve specific goals which describes a persona. These can capture the nonverbal dialog between the user and a product, and the structure and behavior of interactive functions.
There are three types of scenarios the context scenario explores, at a high level, how the product really reaches the needs of the persona. The second is a Key Path scenario which is all about the user interacting with the product. Lastly is the validation scenarios to see what a design resolution would be in different scenarios. The Requirements Definition tells one what the product is and how it should work there are five steps to it
1 Create problem and vision statements
2 Explore/brainstorm
3 Identify persona expectations
4 Construct context scenarios
5 Identify design requirements