PilotStudy-Group:!Xobile
From CS 160 Fall 2008
Contents |
Group Members
- Pilot Study (Mu-Qing Jing)
- Pilot Study (Geoffrey Lee)
- Pilot Study (Perry Lee)
- Pilot Study (Shaharyar Muzaffar)
- Pilot Study (Bing Wang)
Documents
Consent Form (Pilot Usability Study)
Demo Script/Procedure
- Introduction
- Introduce yourself to help relax the subject.
- Explain the game, detailing the overall premise and goal of it.
- Explain the purpose of this study (e.g., to identify any usability issues that may necessitate a design change).
- Show the participant the consent form, giving them time to read it. Re-iterate that he/she can quit at any time.
- After the participant has signed the consent form, ask him/her for his/her demographic information:
- age
- sex
- education level and major(s) if appropriate
- frequency of playing games, and if he/she plays games, which types of games does he/she play?
- level of financial knowledge, how knowledgeable does he/she thinks he/she is?
- has he/she planned for retirement?
- if yes, how has he/she planned for retirement?
- if not, when does he/she plan to start planning?
- Explain how the pilot study will be conducted.
- Note that he/she will be given three in-game tasks.
- Explain that you will be unable to provide help and the reasoning behind it.
- Explain how to "think aloud" and the reasoning behind it.
- To demonstrate how the game works, give a short demo of the system.
- During the demo, show tool tips to the participant.
- Task 1 [Easy]: Buying (creating) an account: Ask the participant to buy an account.
- Task 2 [Medium]: Rearranging the position of an account: Ask the participant to move an account to a different position.
- Task 3 [Difficult]: Moving money from one account to another: Ask the participant to transfer $X from one account to another.
- Outro
- Ask the user which task he/she found the most difficult; which task was the easiest -- for both questions, ask the reasoning behind the participant's selection.
- What would he/she recommend improving (interface-wise) and why?
- Thank the user.
Test Measures
- The amount of time it took for a participant to finish a task
- The number of logged "positive" events (e.g., user says "cool" upon seeing something they like) for a task
- The number of logged "negative" events (errors) for a task
- The number of times a participant hesitated because he/she was unsure how to proceed (per task)