• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Usability Test Overview
 

Usability Test Overview

on

  • 381 views

 

Statistics

Views

Total Views
381
Views on SlideShare
368
Embed Views
13

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 13

https://bblearn.uidaho.edu 13

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Usability Test Overview Usability Test Overview Presentation Transcript

    • Assignment 6: Writing to Present Findings from a Usability Test*
    • Overview Or, what the heck are tools and apps?
    • What is it?  You will be doing an “individual walkthrough” of TWO digital tools or apps that may be useful for technical writers.  You may also use to tools or apps that are useful in your field.
    • But Ari … what do you mean by a tool or app? I’m glad you asked! Tools: Digital tools, often referred to as Web 2.0 technology. They are often web-based. Apps: Apps are free or purchased technology that perform a certain function. These are often downloaded but may also be web-based
    • What to Choose  Two digital tools or apps that can be compared.  Often, these are similar in scope or function.  I bet you want examples, huh?
    • Examples! Loads of them.
    • Examples: Presentations & Word Processing  Google Docs  Prezi  Powerpoint  Zoho  Microsoft  Pages  Empressr Word
    • Examples: Infographics and Data Visualization       Piktochart Easel.ly Create.ly Publisher Illustrator Photoshop    Wordle Google Timeline Bubbl.us
    • Examples: Web Design & Blogs  Wix  Weebly  WordPress  Blogger
    • Examples: Social Media & Bookmarking  Facebook  Twitter  Google Plus  Pinterest  Mashable  Redd.it  LinkedIn
    • Examples: Cloud Storage  Dropbox  Box.net  iCloud  JustCloud  ZipCloud
    • And MORE!  ArcGIS vs. free online mapping tools  Google Maps vs. Yahoo Maps  MatLab  Any other digital tools you may use.  Skype vs. Facebook chat vs. Facetime etc
    • How to Get Started Don’t know where to start? Follow these steps.
    • Usability Test: Step 1  Choose your tools. It’s easiest if you don’t have expert-level knowledge of these tools.  Decide on a set of tasks you will do using each product.  For example, if you are comparing Facebook and Twitter, your tasks might be signing up, logging in, posting a status, replying to a status, etc.
    • Usability Test: Step 2     Do each task for each app. Take detailed notes as you do the tasks – this will make writing your paper so much easier! Test the affordances (those things that work well) and constraints (those things that don’t work well of the limitations of the tool). Pay attention to any problems you encounter when trying to use the product. Be sure to note them!
    • Usability Test: Step 3  Write up your findings in a White Paper format. About 1000 words.  Audience:  Potential users of the tools or apps you test. Imagine that you have been asked to write a white paper about your test for Technology Today, an internet site dedicated to offering information about the latest technology.
    • White Paper Format How is it supposed to look?
    • In general, it should follow this outline: 1. 2. 3. 4. 5. Title Page Introduction section Methods section Results section Recommendation section
    • Format: Title Page  Title Page: Yes, there needs to be a title page.  Tips: Be specific and apply design features to make the title page interesting to potential readers.
    • Format: Introduction Section  Rhetorically, the introduction creates a permanent record of what was tested, why, and for whom.  Be specific in describing the products and typical users of these products.
    • Format: Methods Section  Describe the specific tasks you did when using each product. Consider using a list here.  State when you did the test, where, and anything else that helps a reader understand the testing methods you used such as type of computer (laptop, desktop, tablet?).  Be very specific!
    • Format: Results Section (Part 1)  Make a decision about how best to organize your results.  Use subheadings in this section to help readers navigate and revisit information.  Use elements of excellent design.
    • Format: Results Section (Part 2)  Present the findings of the test by explaining the affordances and constraints of the tasks you completed.  You may want to use graphics such as screen shots to illustrate claims you are making.
    • Format: Results Section (Part 3)  If you experienced problems when working with a product that proved to be inconvenient, such as an app crashing your browser, report those problems by describing what happened.  Be specific, describing the who/what/where/when information.
    • Format: Results Section (Part 4)  You may also want to determine the scope and severity of a problem and/or constraint and provide readers with a means of understanding these by using a rating scale such as:     Unusable: the user cannot or will not perform the task. Severe: the user’s attempt to perform the task is severely hampered. Moderate: the user can perform the task with moderate effort to overcome the problem. Irritant: the problem is cosmetic, or does not present significant difficulty in the user’s effort to perform the task.
    • Format: Results Section (Part 5)  Further, determine what part of the product the error affects. It may affect only one part of the product (local problems), several parts, but not all, of the product (semi-local or semi-global problems), or the entire product (global problem).
    • Format: Recommendation  Make recommendations to potential users of the product.  Consider if it is useful to explain which product might be best for a novice vs. a product for a more experienced user.
    • DONE! Questions? Please ask. 