Usability Study Tools
DRAFT - usability test orientation and template
The assessment of how readily users can accomplish system tasks provides invaluable feedback on whether the system is meeting its objectives. Usability testing does not have to be extensive or complicated in order to be effective. Thoughtful choice of tasks and users can provide useful insight without undue burden.
Tasks should align with the most important objectives and problem solving needs of the system implementation, it does not have to be inclusive of every possible user interaction. Fruitful tasks can be tested with minimal training or instruction and allow for users to possiblly lose their way. It can be useful to include tasks that knowingly introduce error, such as missing or invalid information, or require the user to navigate across more than one system component.
Users ideally represent the perspective and experience with similar systems, but it is not always essential to find actual end users. For basic system tasks especially (or example, registering a patient) subject matter expertise can be waived. It can be helpful to be mindful of user bias, and test with users with a range of experience with the system or similar systems, including novice users.
The following is a suggested template for organizing tasks and data collection.
Draft in progress notes
- Add suggestion to have user think out loud
Field | Definition and notes |
|---|---|
Task | This is what you would like users to be able to accomplish in the system. |
User instruction | The instruction lists details, such as specific test patient IDs, or specific data to add or modify. It may also include guilding steps, but these should be minimal to determine if the UX is intuitive enough without significant user support. |
Outcome | Breifly, w hether the user was able to complete the task, and if so, how long it took. This could also capture how many steps, whether the user needed guidance, or other indicator of how easily the task was accomplished. If the user could not complete the task, Sample outcome examples:
|
Process notes | Detail misconceptions, missteps, or other alternatives to the intended path to complete the task, including where the user could go no further (at all or without guidance). |
Conclusion | Final problem definition and/or recommendation to address issues. |
Example
Test scenario | Examples: Patient registration, patient visit flow, prescribe and dipense, patient status & history, continued care | |||
Roles | Examples: Clerk, nurse, doctor, specialist | |||
Task | User instruction | Outcome | Process notes | Conclusion |
Registration examples | ||||
Update patient contact information | Update the phone number of Test, Test IDA12345 to 555-555-555 | |||
Mark patient deceased | Record that NCD patient test, test has died of X | |||
Register a new patient (provide information) | Add new patient (provide data) | |||
Patient status and continued care examples | ||||
Determine if patient test, test is pregnant | ||||
Update the medication for patient test, test from X to Y | Change the medication for TB patient test, test from X to Y during a follow up visit | |||
See the history of patient viral load | Determine how long the HIV viral load for patient test, test has been undetectable | |||