Usability testing: Difference between revisions
m (Created page with "{{stub}} {{interaction-design|Introduction}} <pageby nominor="false" comments="false"/> == Introduction == == Method == == Links == * [http://www.usabilityfirst.com/usabili...") |
mNo edit summary |
||
| Line 5: | Line 5: | ||
== Introduction == | == Introduction == | ||
User tests measure whether users can get a task done, e.g. finding information, signing up, buying something. Such tests are conducted with a smaller set of representative users, i.e. for an e-learning platform testing, one would select students and teachers. | |||
Typically, participants will have a solve a few tasks in a session, e.g. 6 tasks in an hour. | |||
According to [http://www.usabilityfirst.com/usability-methods/usability-testing/ usabilityfirst.com], {{quotation|tasks should represent the most common user goals (e.g. recovering a lost password) and/or the most important conversion goals from the website or application owner’s perspective. [..] On a website or web application, a conversion is any action taken by a user that satisfies the website owner’s business goals. Common examples include signing up for an email newsletter, making a purchase, or viewing an important web page.}} (retrieved March 13 2011). | |||
User actions are recorded in various ways, e.g. an expert may observe user action and enter summary data (such as "missed") into an application. In more sophisticated setups, users are videotaped from two angles, screen action is recorded, etc. | |||
== Method == | == Method == | ||
* Sit next to the participant and read out a task | |||
* Do not help the participant, just observe and give some non-committal feedback like "go on" "thank you". | |||
* One also can ask the user to "think aloud" what he is thinking/doing. | |||
* If you don't work with a real usability lab setup (video-taping, observers, etc.) then write down important events, i.e. critical incidents and successes. | |||
== Links == | == Links == | ||
* [http://www.usabilityfirst.com/usability-methods/usability-testing/ Usability Testing] | * [http://www.usabilityfirst.com/usability-methods/usability-testing/ Usability Testing]. A short introduction at usabilityfirst.com | ||
Revision as of 13:59, 13 March 2011
<pageby nominor="false" comments="false"/>
Introduction
User tests measure whether users can get a task done, e.g. finding information, signing up, buying something. Such tests are conducted with a smaller set of representative users, i.e. for an e-learning platform testing, one would select students and teachers.
Typically, participants will have a solve a few tasks in a session, e.g. 6 tasks in an hour.
According to usabilityfirst.com, “tasks should represent the most common user goals (e.g. recovering a lost password) and/or the most important conversion goals from the website or application owner’s perspective. [..] On a website or web application, a conversion is any action taken by a user that satisfies the website owner’s business goals. Common examples include signing up for an email newsletter, making a purchase, or viewing an important web page.” (retrieved March 13 2011).
User actions are recorded in various ways, e.g. an expert may observe user action and enter summary data (such as "missed") into an application. In more sophisticated setups, users are videotaped from two angles, screen action is recorded, etc.
Method
- Sit next to the participant and read out a task
- Do not help the participant, just observe and give some non-committal feedback like "go on" "thank you".
- One also can ask the user to "think aloud" what he is thinking/doing.
- If you don't work with a real usability lab setup (video-taping, observers, etc.) then write down important events, i.e. critical incidents and successes.
Links
- Usability Testing. A short introduction at usabilityfirst.com