User Testing Round Template
- Allison Bloodworth
Replace the term "component" in the page links below to match the name of the component being tested. Instructional notes are in italics and preceded with the 
icon. Remove instructional notes and this note before publishing.
Status
This indicates if the testing has been done or needs to be done, and provides reference information if the testing has been completed. Use the statement that applies to the status, either Needed, Planned, or Completed. Remove this note before publishing.
User Testing Needed
Planned for Month Year.
Completed Month Year by Unlicensed user and Unlicensed user.
Summary
Remove the statement below, and provide a concise summary of the user testing results after testing is complted. If the testing is still planned, provide a concise summary of what is to be tested. After the summary has been added, move the tags from the "Goals" section to this Summary so it will be included on other pages as the brief description of content of this page. Remove this note before publishing.
High-level summary to be added after testing has been completed.
Notes
List notes or information specific to this round of user testing that might be helpful to others. Remove this note before publishing.
Goals
This test should discover:
List the goals of the user test. Remove this note before publishing.
- Goal 1
- Goal 2
- And so on...
Success Criteria
A successful design has been achieved when:
List out the success criteria of the user test. Remove this note before publishing.
- 50% of users...
- 80% of users...
- And so on...
Protocol
Method and test coordinator script.
Link to child pages which describe the protocol for the user test. Replace "Component" with the actual component name, and "round 1" with correct round of user testing. Remove this note before publishing.
Users
List notes or information specific to the users desired and/or selected for this round of user testing. Remove this note before publishing.
Interaction Design
Underlying design patterns and description of component behavior.
Link to the interaction design of the component for reference of desired component behavior. Replace "Component" with the actual component name. Remove this note before publishing.
Test Environment
Location and version of the environment that was used. Attach a screenshot of the environment at the time of testing if the environment will change over time.
Provide a link to the url of the prototype used for testing. Capture and attach a screenshot of the environment at the time of testing if the environment will change over time. Remove this note before publishing.
Results
Full notes and analysis of the user tests.
Link to the child page describing the detailed notes and analysis of this round of user testing. Replace "Component" with the actual component name, and "round 1" with correct round of user testing. Remove this note before publishing.