PROJECT

USER

TESTING

Task your user to do an action in the application, then watch and observe.

Do not help them, unless they are really really stuck!!!

— The Task Testing —

Lean UX is all about testing all the time at every stage of your design.

You don't know the impact of your design decision unless you test it.

Testing is how you will know your design works or not.

Think like a scientist and decide like a lawyer.

If your not user testing, your accumulating risks every time you make a design decision.

 

 

WHY

 

THE

All the time and as much as possible.

In the industry, it's best to test once a week or every other week. Always be testing (ABT)

YOUR DESIGN DOES NOT NEED TO BE PERFECT or complete at all, to test it. Don't wait until it's too late.

Do concept level testing with paper prototypes, tons of testing during wire-frame level and in the visual stage too.

If you add a bunch of new screens or change existing interactions, then you should test and Iterate.

 

 

WHEN

 

THE

THE

TESTING

 

 

CONDUCTOR

TEST CANDIDATE

NOTE TAKER

ONSITE

RECORDING

 

 

TOOLS TO RECORD A DESKTOP SCREEN

 

QUICK TIME - CAN RECORD DESKTOP

ZOOM - SCREEN SHARE AND RECORD

 

DESKTOP

NOTE TAKER

CONDUCTOR

TEST CANDIDATE

PHONE

 TOOLS TO RECORD A MOBILE SCREEN

 

Zoom can record on phone

Lookback app - but it's expensive

Screen recording on your iphone

CONDUCTOR

TEST CANDIDATE

NOTE TAKER

REMOTE

RECORDING

 

 

REMOTE SCREEN SHARING STEPS:

 

 

SEND LINK TO PROTOTYPE RIGHT IN THE BEGINNING OF THE SESSION.

HAVE THEM PRESS THE ZOOM SCREEN

SHARING.

HAVE THEM READ THE TASK SCREEN

AND START THE TASK.

HAVE THEM TALK OUT LOUD.

 

TEST
CANDIDATE

SCREEN SHARE - DESKTOP

NOTE TAKER

CONDUCTOR

DON'T TEST MOBILE REMOTELY

 

IT'S NOT 100% CONCLUSIVE AND IS
ONLY DONE TO VALIDATE CONTENT
ORDER NOT USABILITY.

SCREEN SHARE - MOBILE

CONDUCTOR

NOTE TAKER

PROJECT


HOW

 

THE

1st 

2nd

3rd

What are the scenarios you're going to task people to do in
your application?

Take a look at each scenario and look at the
screens you're going to show per scenario. Then write questions that tasks & guide the user through that specific work-flow/scenario.

Write a testing-guide or user-testing script

that goes through each scenario of your application and guides the user through the screens with questions relating to each screen and section that you are showing.

Adding your clipper card.

Checking clipper card balance.

Adding $20 to your clipper card balance.

Checking the status connection of your luggage.

Booking a flight.

 

How do you add your clipper card and see the balance:

Q. Is this all the information you need?

Q. Once you add it, how do you know what the account balance is?

Q. What would you expect to see if you balance is getting low?

Q. How would you like to get notified if your clipper card is low?

 

How do you check the status connection of your luggage:

Q. How do you know it's connected?

Q. What would you expect to see if it's not connected?

Q. Where would you go to re-connect it?

 

 

How do you know what the current balance of your clipper card is?

-

Once you know the balance, how would you add $20 to your balance?

-

How do you know where your luggage is? How do you know that you're connected to the luggage? How would you know if you luggage is not connected?

-

How would you book a flight? What information that you viewing is most important to know about? Once you book the flight, what kind of confirmations would you like to receive?

examples

examples

examples

DOWNLOAD

USER

TESTING

SCRIPT

 

DISCUSSION

NOTES

AND

OBSERVATION

AND

OBSERVATION

NOTE TAKER

CAN SET UP

A RECORDING

STATION