Usability testing 101
By Christopher Ellis (Digital Product Designer)
At Mentally Friendly, testing is at our core.
It taught me how to let go of any creative ego, which has little space to breath when your work is put through its paces in real world scenarios — it keeps everyone honest and ensures our ideas are being validated throughout the process.
It’s amazing because it:
- Brings up roadblocks
- Removes team bias
- Allows pivoting easily
- Moves the team from thinking to knowing
All in the shortest possible timespan.
What is usability testing?
A usability test consists of gathering unbiased participants and asking them to perform specific tasks on an interface we created.
An interface can range to a paper prototype to test a navigation structure, or a checkout form with live data scraping from the clients server.
It is to ensure that something works, to find out how self explanatory things are and if a person of average ability or experience can use it.
What it isn’t
A focus group
Why is it important?
When solving complex problems it is always good to get validation early so you can course correct if need be.
On exisiting products it can identify bottleneck points and on a new product it allows the product team to gain fresh eyes who have not been on the same journey we have.
What do we test?
We focus on testing functionality, rather than design. It is not a method to crowdfunded design ideas.
When do we test?
There is no time like the present — aim for less participants and more frequency.
Testing can occur when you:
- Already have an exisiting product
- You have a new idea
- You are just starting to build one
It is not something to cram into the end of a project so you can tick the box that you did it. It is meant to be part of an ongoing iterative process, with the underlying goal of improving the product.
Types of testing
Generally speaking this is the “hallway testing” recruitment method. We are testing the usability of the interface — the main focus of this article.
This is where you recruit industry experts, testing initial reactions to a new concept.
Who do we test on?
For usability there is usually no needs for a target audience, if someone with an average digital skill set can’t perform the task, the UX needs to be improved.
For both avoid choosing someone with a design or UX background as they immediately turn from being test subjects into being “expert reviewers”
What do we look at?
We Create a series of testing tasks scenarios — real life mini ‘challenges’ for the user to try and complete using a website or app.
Make it crystal clear on what needs to be done and don’t lead the subject.
Instead of asking “Can you find the settings page?” perhaps phrase it “You just got a new phone number and wanted to update it in the system, how would you do that?”
We really want to know:
- Can they complete the tasks unassisted?
- Are there any blocks preventing the user from completing the tasks?
- Are they completing the task as we intended? If not how are they navigating to complete the challenge.
How to create a scenarios
Have a goal in mind (find the best price) → anticipate user steps (find and use a special offer) → take them through obstacles/cross roads (deal applicable to a portion of a shopping cart)
- What is the objective of the website? What are the overarching goals that we want the user to complete?
- Since the last sprint, what are the major updates that have been added to the UX?
- Are there any ‘new concepts’ on the website that might not be obvious to the average user?
Have there been any considerable design challenges during this sprint?
Our Tools for Testing
The Spy Room™
Our Observation room, colloquially know in the studio as The Spy Room™ has cinema styled seating, 5 viewing monitors and the air conditioning to match.. oh and a two way mirror.
This is where the team can witness the interactions in an unobtrusive way and allows the team to take notes and discuss outcomes in real time.
It also relieves pressure on the tester to take notes as they should be focused on running the test as they may miss important insights.
It even record the user’s face and voice, so they can explain what they’re doing when they encounter a bug or some other problem.
We found lookback is great for reviewing sessions and also sharing to stakeholders who can not attend.
- Keep overarching goals at the core of the process
- Test functionality, not design
- Prioritise frequency of testing over a number of participants
- Test the product, not the user
- Try to make them feel as comfortable as possible
- Avoid leading people
- Stimulate thinking out loud
- Write down insights throughout the test
- Have people watching to take notes
- Any test is better than no test