- Platform for Economic Inclusion
- Preference Editing Tools Design
- Fluid Infusion
- Design Handbook
- Social Justice Repair Kit
- BIG IDeA
Getting Started with User Testing
After reading the info on this page, check out User Testing Tips which provide a high-level summary of things you should think about when planning and executing user tests. User Testing Methods discusses techniques you can use to conduct a user test.
Selecting and Recruiting User Test Participants gives advice on this important part of the user testing process. The next step would be to create User Testing Scenarios and Tasks and then a User Testing Protocol for the facilitators to use when running a user test.
An example of how the process of setting up a user test might work is described in User Test Example - the Fluid Lightbox, and you can see all the user tests performed in the Fluid Project at Fluid User Testing.
User testing, also sometimes referred to as usability testing, is a technique for evaluating usability, working with an actual or potential user of a product or system.At a basic level, a user test usually involves a facilitator asking a user to complete a series of tasks (which may or may not be pre-determined) while observing the interaction, noting any problems the user encounters, errors made, and sometimes the amount of time it takes to complete a task. These findings are then fed back into the design and development cycle in order to improve the product or system.
User testing can be performed on products or systems at any stage of development, from the early stages of design to production systems. It can be helpful to start by performing user tests with paper prototypes and continuing to test more interactive prototypes as a product or system is iterated upon.
Many people think of user tests as requiring sophisticated usability labs with one-way mirrors and recording equipment, with highly detailed tests that take an hour or more to complete, and require even more time to transcribe and understand the results. While there are definitely times where this level of testing is useful, this approach often doesn't justify the return on investment for smaller projects. In fact, you can obtain extremely helpful results, and realize great improvements in your product or service, from usability tests done at a user's desk or in the conference room down the hall.
In "A Practical Guide to Usability Testing" (1990), J. Dumas and J. Redish explain, "While there can be wide variations in where and how you conduct a usability test, every usability test shares these five characteristics:
Creating User Testing Documentation
If you're creating own user testing pages in this wiki (e.g. under Fluid User Testing), you can copy the following templates:
Alternatively, if you are not creating pages about in this wiki but would like to use our templates, each template can also be converted to a Word document by going to the following pages and choosing "Page Operations" -> "Info" -> "Export as Word."