|
Usability of Interactions
 A usability goal is specific and has measurable business value
 Usability goals consist of attributes and measurement criteria
 Attributes having business value:
 Ease of learning
 Ease of use
 Ease of navigation
 Usefulness (matches job function to workflow)
Preview: A Usability Process
A Quick View of Steps, Deliverables, and Tips for Usability Evaluations
Step 1 - Quick View: Determine Test Site
Deliverable: Commitment for a suitable location to conduct the performance support test
 Select a usability lab or identify a location suitable for a test.
 Consider connectivity, set up and testing.
 Consider evaluator travel and parking (evaluators are performers: those who do work using the system)
 Get commitments for space and equipment for the times you intend to conduct the lab plus some time before and after.
Step 2 - Quick View: Select Evaluators (aka Performers)
Deliverable: Commitment by suitable evaluators to participate in the test
 Determine an appropriate number of evaluators.
 Determine the levels of evaluator necessary for the test.
 Consider evaluator travel, parking, and other needs.
Step 3 - Quick View: Document Performance and Usability Goals
Deliverable: Set of measurable goals that reflect business performance and usability
 Determine measurement criteria to evaluate performance and usability.
 Determine attributes of concern.
 Determine the measurements of concern.
 Document goals.
Step 4 - Quick View: Develop Scenarios
Deliverable: Set of business scenarios suitable to test the performance and usability goals
Consider processes, tasks, and activities which:
 enable measurement of performance (e.g., time for task completion, accessiblity and use of embedded support)
 enable measurement of usability goals;
 reflect the performers' environment;
 are realistic with respect to frequency of tasks;
 are appropriate for the diversity of performers;
 will be performed in production;
 have representative degrees of complexity;
 impact business performance if not performed correctly;
 represent business criticality;
 accurately represent volumes; and
 considers performers outside of your organization if appropriate.
Step 5 - Quick View: Develop Evaluator Briefing
Deliverable: Briefing document and plan for delivering the briefing
The briefing is designed to orient evaluators to:
 what they will do;
 what will be done with the results.
 the sequence of events;
 understand that the product is being tested, not them;
 that the test is being filmed;
 advance training;
 how to get help;
 how to proceed through the scenarios;
 pencil and paper for making notes;
verbalize their thoughts;
 taking breaks as they would on the job.
Step 6 - Quick View: Develop Evaluator Debriefing
Deliverable: Debriefing document and a plan for delivering the debriefing
The debriefing is designed to capture information critical to determining whether or not the performance and usability goals are met. It should capture attributes like:
 visual clarity;
 consistency;
 compatibility;
 informative feedback;
 explicitness;
 flexibility and control;
 error prevention and control;
 ease of use;
 intuitiveness of labels and messages;;
 layout of elements;
 ease of learning;
 likes /dislikes;
 affordance;
 use of specific system features; and
 use of color.
Step 7 - Quick View: Schedule Evaluators
Deliverables: Evaluator schedule, memo to evaluators, and commitments from evaluators
 Create a schedule based on evaluators arriving 1 - 1.5 hours apart.
 Base time per evaluator on anticipated scenario time x 1.5, plus 30 minutes total for brief & debrief.
 Determine schedule for evaluation based on lab availability, product readiness, availability of evaluators.
 Send invitation to each evaluator
 Confirm changes to schedule.
Step 8 - Quick View: Set Up Lab or Evaluation Area
Deliverables: Evaluation area, completely tested and ready for the evaluation
Consider the following:
 connectivity requirements;
 software functionality (that it behaves as in the workplace);
 simulated work environment and sufficient privacy to conduct an evaluation; and
 ability to observe without disturbing the evaluator or invalidating the test.
Step 9 - Quick View: Select Observation Team
Deliverables: Commitments from an appropriate number and type of people to serve as usability test observers
 Consider the following:
 representatives from business, technical/developer, and management roles;
 not too many;
 keep them out of view of the evaluators;
 roles and responsibilities; and
 need to observe.
Step 10 - Quick View: Conduct Dry Run
Deliverables: Final versions of Briefing, Scenarios, Debriefing, and Roles / Responsibilities
The Dry Run must:
 be run as an actual performance/usability evaluation;
 objectively evaluate if the test is workable;
 ensure that all connectivity, hardware, and software functions as expected;
 ensure that briefing accomplishes objectives;
 ensure that scenarios are easy to follow;
 ensure that debriefing questions make sense; and
 be viewed as an opportunity to make changes to all materials, roles, and responsibilities.
The Dry Run is a usability test of this test!
Step 11 - Quick View: Conduct Usability Evaluation
Deliverables: Video tapes, logger sheets, and observer comments
 Provide a waiting area for evaluators away from observation team.
 Try to stay on schedule, but if this is not possible set expectations for next evaluator.
 Brief evaluator in a relaxed, friendly manner. Stick to prepared briefing.
 Observers must not be heard by evaluators.
 Stay focused on the test goals and record what you see.
 Debrief evaluator in a relaxed, friendly manner. Stick to prepared questions.
 Do not share the goals with evaluators.
 Do not lead evaluators.
Step 12: Document Test Findings
Deliverables: Documentation of test results and recommendations for improvement
 Document what was observed, not speculation.
 Determine which goals were met and which were not met.
 For goals that were not met, recommend changes to enable performance and make the application usable.
 Distribute findings to all stakeholders.
|