During the design phase, we use an iterative process to develop user models and begin prototyping. We gather user feedback to help us evaluate and revise our designs.
User Models After gathering all the customer and workplace data, our next step is to create a user model. The user model is the most critical aspect of usable software. It must resonate with users so that they can use the product seamlessly and efficiently. A model maps all of the identified goals and assumptions to interface elements. The resulting design has to satisfy the users' explicit needs and help create a coherent view of the whole. (That coherent view is usually formed via some kind of metaphor.) This view of the whole is the user model. It describes how the user will view and understand the software.
Deliverable
Rough Concepts
WHY:
Explore alternative user models.
HOW:
Sketches, storyboards, paper designs.
Deliverable
Detailed Early Designs
WHY:
Create screen drawings to establish the navigation model, the layout grid, and the basic structure. Develop paper prototypes that illustrate key tasks.
HOW:
Screen drawings, grids, and paper prototypes.
Deliverable
User Feedback
WHY:
Collect user feedback on paper prototypes. Iterate user model.
HOW:
Gather data and redesign paper prototypes.
Prototypes Once the user model has been created, tested, and refined, we develop an online prototype. The goal of the prototype is to demonstrate the human—computer interaction for a set of typical tasks drawn from the Top—10 list. The prototype is used for usability testing, and it acts as the design specification for ongoing development.
Deliverable
Online Prototype
WHY:
Demonstrate the user model and detailed designs. Use the prototype as design specification.
HOW:
Multi—disciplinary team using rapid prototyping tools.
Deliverable
User Study
WHY:
Uncover usability problems in the prototype.
HOW:
Run study, with real users, to identify design problems. Re—design the interface.
