• Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. What is Usability?Its simple, all you need is a design, place it where user will use it normally, and observes the person, learn from how his behaviors in interaction and how well the design performed?
  • 2. Usability study or test is not an easy job…• We should be doing the test/study throughout the whole design and development cycle.• Even its on the paper / prototype process, getting feedback is very useful.• We should not ask how they feel about the design / site, instead watch and listening to how they use the site.
  • 3. Why usability test / study?• Increase website ROI, with usability test 1) Performance: How much time, and how many steps, are required for people to complete basic tasks? (For example, find something to buy, create a new account, and order the item.)
  • 4. 2) Accuracy How many mistakes did people make? (And were they fatal or recoverable with the right information?)
  • 5. 3) RecallHow much does the person remember afterwards or after periods of non-use?
  • 6. 4) StickinessHow much time he/she spends
  • 7. 5) Emotional Response How does the person feel about the tasks completed? Is the person confident, stressed? Would the user recommend this system to a friend?
  • 8. How to run a usability study / test?
  • 9. Usability TestPlanning the study: Developing schedules and tasks, finding participantsIndividual Test sessions: what each participant doesObservers: your roleThe usability report: the outcome of the studyTools:helps in observation and analysis
  • 10. 1 ) Planning:• Decide which part are we going to test and in what format? From prototype to finished product.• Recruit participants based on the personas we defined. (of course we give them some benefits for the testing…)• Locations of their testing, we need to define where the user will be tested, its good to test in our office, so designers can observe what their behaviors are. Or if they are lack of time, we can go down to their work place ( this help us to learn about their work environment which is helpful for building personas )• We need to define the task and questionnaires for testers.• Review session is good for each test.
  • 11. 2) Individual test session• Task should be what tester do in real life, they are based on the usage scenarios that we develop as part of the persona development. At this moment we need observe carefully and see how well the product meet their need.• The session can be from half to an hour as normal life scenarios.• After the test was done, we should start to review, questions about if the product match their concept and need.
  • 12. 3) Observers• Members of the team should watch closely on the tester’s behavior on the product.• Software / notes should be used to capture the testers’ sound / face / body language… which is very helpful for analysis phase.
  • 13. The usability report:• By combining all the notes and sketch that designers observed.• Highlight and or combined into a videotape. In addition to product-specific categories, usability reports cover these topics: layout and visual design, conformance with platform UI guidelines, terminology, how well the product matches the users conceptual model of the task, ways you can improve transaction rates.
  • 14. ToolsMorae captures the exact screen that the participant sees. Observers see that witha picture-in-picture image of the participants face. An observer takes note that aretime stamped and included with the video for analysis.WebEx is also helpful because it allows for screen sharing and voice communication.