Gomoll Research + Design | Process: Analysis

Process: Analysis

The analysis phase of our process includes workflow modeling, task analysis, and usability benchmarks.

Workflow Modeling
On each customer site visit, we observe and videotape people as they work and interact with technology and other people. Then we conduct interviews. During the interviews, we ask people to describe a typical day. We zero in on their relevant tasks by asking them to walk through a typical case, demonstrating the tools and techniques they use. As they work, we prompt them as needed to draw out information. We use the data we collect to characterize the current workflow and identify inefficiencies.

Deliverable		Workflow storyboards and videotapes
WHY:		Understand the collaborative work environment from a user's point of view. Create a "big picture" view of the current workflow, concentrating on "day-in-the-life" scenarios. Describe the tasks people do, the environment they work or play in, and the roadblocks they encounter.
HOW:		Group, filter, and sequence the data from the site observations. Use storyboards to visualize task examples. Create: • Scenarios • Affinity diagrams • Workflow models • Storyboards

Task Analysis
Before we can start design work, we need a detailed description of the tasks the software should satisfy. We use a systematic process to develop this list of the most frequent and important tasks. We then create detailed descriptions of the tasks. The task descriptions will drive the software development.

Deliverable		Top-10 Task List
WHY:		Identify the most important and frequent tasks.
HOW:		Surveys, interviews, and observation.

Deliverable		Detailed Task Examples
WHY:		Develop detailed task descriptions to be used in specifying, developing, and testing the software.
HOW:		On—site observations. Create storyboards, task maps, etc.

We use the detailed task descriptions to guide and test our design throughout the product development cycle. Underlying this approach are the following assumptions:

•	Software development should focus on user tasks, not just feature lists.
•	Focusing on a limited set of tasks helps a development team focus its efforts.
•	Focusing on a prioritized set of tasks guarantees that the most important functionality gets done and helps a development team combat "featuritus."
•	Wrote formal test reports
•	Working from detailed examples keeps decision—making in the concrete and out of the abstract.

Usability Benchmarks
We create a set of specific usability objectives for the product. These objectives can be used to evaluate the effectiveness of the new system. The benchmarks define goals such as relevance, efficiency, learnability, attitude, and availability.

Deliverable		Set of Measurable Usability Criteria
WHY:		Determine measures of successful performance. Evaluate future prototypes and/or products.
HOW:		Elicit management goals and user needs.