1.
You will learn about . . . Conceptual framework for Usability and . . . An inventory of methods and . . . Intro to user testing Usability – Everyone wants it, everyone claims to have it, but just what is it?

2.
Redengine <ul><li>Who Are We? </li></ul><ul><ul><li>Edmonton based company </li></ul></ul><ul><ul><li>Operating since 1997 </li></ul></ul><ul><ul><li>12 employees </li></ul></ul><ul><li>What We Like to Do. </li></ul><ul><ul><li>Web Design </li></ul></ul><ul><ul><li>User Research and Testing </li></ul></ul><ul><ul><li>Content Management </li></ul></ul><ul><ul><li>Designing Web Based Applications </li></ul></ul>

3.
What is Usability? The technical definition: The ISO defines usability as: “…the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use.”

4.
Defining the Problem specified users: Who will use the system? specified goals: What tasks do they need to complete? specified context: Where will they use the system?

5.
The Elements of User Experience What is the purpose of this site / application? What functions will achieve these purposes? How will people move through these functions? How should these functions be presented? What visual style would best represent our brand? Diagram: Jesse James Garrett, Adaptive Path

6.
Filling the Gap <ul><li>Website development needs to balance: </li></ul><ul><ul><li>business priorities </li></ul></ul><ul><ul><li>functional requirements </li></ul></ul><ul><ul><li>technical implementation </li></ul></ul><ul><li>Adapting a strong user-centered approach can achieve the balance. </li></ul>

7.
Methods

8.
Task Analysis <ul><li>Taskflows: </li></ul><ul><ul><li>Show users’ decision points </li></ul></ul><ul><ul><li>Show when users will have to perform actions </li></ul></ul><ul><ul><li>Suggest page order </li></ul></ul><ul><ul><li>Show where menus, information and controls need to be included </li></ul></ul>

10.
Wire-frames <ul><li>Wire-frames are: </li></ul><ul><ul><li>A detailed view of the product, representing basic screen real estate </li></ul></ul><ul><li>Benefits: </li></ul><ul><ul><li>Fast and cheap </li></ul></ul><ul><ul><li>A common language </li></ul></ul><ul><ul><li>Easy to iterate </li></ul></ul><ul><ul><li>Easy to test </li></ul></ul><ul><ul><li>Retire risk at an earlier stage </li></ul></ul>

14.
User Testing <ul><li>User testing is: </li></ul><ul><ul><li>Task-based </li></ul></ul><ul><ul><li>Observational </li></ul></ul><ul><ul><li>One-on-one </li></ul></ul><ul><ul><li>Designed to measure performance </li></ul></ul><ul><li>Benefits: </li></ul><ul><ul><li>Reveals how people actually use your system </li></ul></ul><ul><ul><li>Helps to uncover usage patterns and break points </li></ul></ul>

16.
User Testing - Scope <ul><li>You can conduct informative user tests on: </li></ul><ul><ul><li>Existing site and applications </li></ul></ul><ul><ul><li>HTML prototypes </li></ul></ul><ul><ul><li>Redeveloped sites </li></ul></ul><ul><ul><li>Wireframes and mockups </li></ul></ul><ul><li>Keep in mind: </li></ul><ul><ul><li>Restricted task movement when you have limited functioning paths </li></ul></ul>

17.
User Testing Preparation – 8 Steps <ul><ul><li>Define the goals/concerns that are driving the test </li></ul></ul><ul><ul><li>Determine the profile for the participants </li></ul></ul><ul><ul><li>Recruit participants </li></ul></ul><ul><ul><li>Select and organize tasks to test </li></ul></ul><ul><ul><li>Create task scenarios </li></ul></ul><ul><ul><li>Decide measures </li></ul></ul><ul><ul><li>Prepare other materials </li></ul></ul><ul><ul><li>Conduct a pilot and revise </li></ul></ul>

18.
1. Define the goals/concerns that are driving the test <ul><ul><li>You can’t test everything </li></ul></ul><ul><ul><li>Priority should be on </li></ul></ul><ul><ul><ul><li>Mission critical </li></ul></ul></ul><ul><ul><ul><li>Common tasks </li></ul></ul></ul><ul><ul><ul><li>Representative tasks </li></ul></ul></ul><ul><ul><ul><li>Specific areas of concern </li></ul></ul></ul><ul><ul><ul><li>Specific audiences </li></ul></ul></ul>

19.
2. Determine Participant Profile <ul><ul><li>You should already have audiences defined </li></ul></ul><ul><ul><li>Use general research as input </li></ul></ul><ul><ul><li>Segment </li></ul></ul><ul><ul><li>Don’t fall into the “everybody” trap </li></ul></ul>Intermediate University 26-40 Male P8 Intermediate Some college 55+ Male P7 Expert College 18-24 Female P6 Intermediate University 55+ Female P5 Intermediate University 26-40 Female P4 Intermediate University 18-24 Male P3 Intermediate University 41-55 Male P2 Intermediate University 25-40 Male P1 Site Experience Education Age Gender

20.
3. Recruit Participants <ul><ul><li>Use research companies to recruit </li></ul></ul><ul><ul><li>Invite through contests or surveys </li></ul></ul><ul><ul><li>Community boards </li></ul></ul><ul><ul><li>Try to schedule all participants within a narrow window of time </li></ul></ul>

21.
4. Select and Organize Tasks <ul><li>Usability test tasks should be derived from: </li></ul><ul><li>Tasks that probe potential usability problems </li></ul><ul><li>Tasks suggested by the concerns and experience of the design team </li></ul><ul><li>Tasks that users will do with the end product </li></ul><ul><li>Tasks should flow in the natural order in which users will do them. </li></ul><ul><li>Tasks that are important to the evaluation should come early, as some participants may not finish all tasks. </li></ul>

22.
5. Create Task Scenarios <ul><li>Should describe tasks in a way that takes some of the artificiality out of the test. A good scenario: </li></ul><ul><li>Is short </li></ul><ul><li>Is in the user’s words, not the product’s </li></ul><ul><li>Is unambiguous – so all participants will understand it </li></ul><ul><li>Gives participants enough information to do the task </li></ul><ul><li>Is directly linked to your tasks and concerns </li></ul>

23.
5. Create Task Scenarios (example) <ul><li>You’re planning to build a new garage in the spring and you want to find out if you’ll need a permit and, if you do, how much the permit will cost. From the City home page find the information you need. Do you need a permit to build a garage? Yes | No | Don’t know If yes, how much will it cost? _______________ </li></ul>

24.
6. Decide Measures <ul><li>Quantitative: </li></ul><ul><ul><li>Time to finish a task </li></ul></ul><ul><ul><li>Time spent recovering from errors </li></ul></ul><ul><ul><li>Number of wrong menu choices </li></ul></ul><ul><ul><li>Number of errors </li></ul></ul><ul><ul><li>Observations of frustration, confusion, or satisfaction </li></ul></ul><ul><li>Subjective: </li></ul><ul><ul><li>Measures may be either quantitative or qualitative </li></ul></ul>

25.
6. Measures (example) 3.5 0 50% 50% Rate Fail Part Pass Youth (18 - 25) 4.0 0 100% 0 Rate Fail Part Pass Seniors (55+) 2.5 0 50% 50% Rate Fail Part Pass Target Audience (26 – 54) 3.1 Average Task Rating 1 Average Errors 4.9 Average Clicks 2:46 Average Time 0 Fail 63% Partial 38% Pass

26.
7. Prepare Other Materials <ul><li>Legal form – informed consent for the test / nondisclosure agreement / waivers for the use questionnaires </li></ul><ul><li>Questionnaires – pretest / post-task / post-test </li></ul><ul><li>Training scripts – to ensure that all participants have the same level of knowledge before they begin the tasks </li></ul>

27.
8. Pilot and Revise <ul><ul><li>Will help you: </li></ul></ul><ul><ul><li>Revise test materials and procedure </li></ul></ul><ul><ul><li>Flush out “functions” that need to be enabled on prototypes </li></ul></ul><ul><ul><li>Confirm length of test </li></ul></ul>

28.
User Testing - Conducting <ul><ul><li>Environment should be representative </li></ul></ul><ul><ul><li>Ideally use the same tester for every participant </li></ul></ul><ul><ul><li>Observation, not guidance </li></ul></ul><ul><ul><li>Record notes quickly after test </li></ul></ul><ul><ul><li>Stopwatch, video camera, click tracker are all considerations </li></ul></ul>

29.
<ul><ul><li>Can be informal or formal </li></ul></ul><ul><ul><li>Should include recommendations/solutions </li></ul></ul>User Testing - Reporting While none of the test participants completely failed in this task, only three of eight were able to find both the permit application form and the fee information. Five of the 8 either failed to find any fee information, or found incorrect information. This task reveals an instance of poor content grouping. If a person is planning to build a garage they should be able to get all permit-related information in one location. Illustration 13 demonstrates a possible approach to content grouping.

30.
Value – Mitigate Risks 50–70% of IT projects fail to deliver expected results. According to a Standish Group study 4 of the top 10 reasons IT projects fail are directly related to poor user design. #1. Incomplete Requirements – 13.1% #2. Lack of user involvement – 12.4% #4. Unrealistic expectations – 9.9% #6. Changing requirements – 8.7% TOTAL = 44.1%

31.
Value – The Benefits <ul><li>Reduced development time </li></ul><ul><ul><li>Iteration on simple mockups </li></ul></ul><ul><ul><li>More complete picture before development begin </li></ul></ul><ul><li>Usage savings </li></ul><ul><ul><li>Fewer user errors </li></ul></ul><ul><ul><li>Less training, support and documentation is required </li></ul></ul><ul><ul><li>Higher adoption </li></ul></ul><ul><li>Improve the quality of life </li></ul><ul><ul><li>Users are more satisfied </li></ul></ul>

32.
Maximize Your Business Case

33.
Answers and Qustions <ul><li>Norman Mendoza, President </li></ul><ul><li>Redengine Inc. </li></ul><ul><li>[email_address] Skype or Messenger </li></ul><ul><li>Toll Free 1.877.837.5087 </li></ul>