Let’s understand how does Usability testing differs from
User Testing, when are they involved and how do they add value in your design
sprints.
Nowadays, we can see these terms flying in any product
discussions. Usability testing is very often confused with user testing. Know
about them individually and see how do they add value/ at what phase they are involved
in the design process.
1. User Testing
My dear friend (ahem, I wish) Travis Kalanick, now Founder
and CEO of Uber App got stuck in a traffic in Paris on a rainy day and couldn’t
get a cab. He took the problem in hand and started going to friends’ / bus
stops / taxi stand / building exits, asking them if they would like to have an
app which could get them a cab in a click (and how). That’s user testing!!
User Testing is more like testing the utility of your idea
or app. It involves understanding how people do this thing as of today and will
(and how) they use an alternative to do that same job. Typical result of user
testing is user persona of your target user segment.
2. Usability Testing
Now there were enough friends’ and people telling Travis
that they’d love to get a cab right from their mobile app. So he got an early
design and ask them to try booking a cab ride. He observed and identified where
people were getting stuck in booking a ride. Fixed it. Showed them again.
That’s usability Testing!!
It helps you to understand if people can effectively use
your app or not, where are they getting stuck and what should you do so that
they don’t’ get stuck.
3. That’s the same
story behind every successful app
Tinder, AirBnB, Snapchat, you name it. The difference
between user testing and usability testing is really simple — User Testing is
about “Will this user use my product?” where usability testing is to figure out
“Can this user use this product?”. People often confuse these with each other.
Once you understand these terms better, you can use these methods at right time
and get better input for better user experience.
4. Let dig deeper
And see how and when user testing and usability testing add
value in creating good experience. To keep things simple, we can understand
differences in terms of the stage they are required, Expectation out of it,
Questions asked and methods/tools being used.
4.1 When should you
do:
User Testing:
Right after you have got the idea.
Usability Testing:
As soon as you have drawn those random hand drawn sketches on paper
4.2 What to expect
from:
User Testing: Do
people need the solution I am working on?
Usability Testing:
Can people easily use the app ( for a given set of task) I am working on?
4.3 How should you
run:
User Testing:
coffee shop discussion, in-person discussion at friends’
place, office, club, bar, Virtually at Skype, Google hangout, google forms,
Type form, Survey Monkey.
Usability Testing:
- You can create a rapid prototype on CanvasFlip within 5
minutes. You can use your hand drawn sketches.
- Add small task for users.
- Go to your users and ask them to do the task on the
prototype
- On CanvasFlip, you can also remotely record how users are
navigating through to complete the task (See More).
- Instantly observe conversion funnel and heatmap on
CanvasFlip to see where users are getting stuck in your flow and review videos
on how to improve.
4.4 What to ask
during:
User Testing:
- How do you currently do <problem you are solving>?
- Did you even think of a better way of doing this?
- Will you like to do this task <the way your solution
works>?
- Will you pay money (for transaction apps) / share content
for this solution?
Usability Testing:
- Can you try doing this <new way of solution>?
- How would you like to login to this solution?
- Can you get <a small task in your solution> done in
10 seconds?
TL;DR: User Testing is testing your users whereas, Usability
Testing is testing the interface.
Now you know how user testing differs from usability
testing, how do they add value and when.
All the best with your next user testing (or usability
testing)!!
No comments:
Post a Comment