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

 

Lookback Participate application

CONDUCTOR

TEST CANDIDATE

NOTE TAKER

REMOTE

RECORDING

 

 

REMOTE SCREEN SHARING STEPS:

 

 

SHARE AN "ZOOM" LINK

PRESS RECORD

SHARE YOUR SCREEN

GIVE MOUSE CONTROL

TEST THE PROTOTYPE

 

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 with each scenario of your application and guides the user through the screens with questions relating to each screen and section that you are showing.

Also, think about what assumptions you're

making in the u.i. and capture the user interface assumptions.

Selecting/inputing animal preference.

Inputing water intake information.

Viewing neighborhood parking info.

Finding a local activity in SF.

How would you enter your animal preference?

Q. Are these all the breeds you're looking for?

Q. Is there any education or information that's missing?

Q. Are thing any additional information you want the app to know
    about you and your animal preference?

 

How do you input your water information?

Q. How do you know how much water you have drank?

Q. How would you like to input water intake info in the app?

Q. Is there any information you want to know about your water input?

 

Show me how you would find neighborhood parking info?

Q. How do you know what neighborhoods are unsafe?

Q. Do you need the map while viewing neighborhood information?

Q. Is there any information you want to know more about?

 

How would you find & schedule a local activity in SF?

Q. Is this the best way to find or filter activities in SF?

Q. Are are any missing filters or categories you want?

Q. Is there any additional information you were looking for
    when you found a activity to schedule?

Adopters will adopt an animal with only a small amount of animal info.

People will want to be reminded everyday about water intake.

People have time and know how to easily find and reach a parking sign info.

Tourist/1st time movers will share information about their experiences

examples

examples

examples

DOWNLOAD

USER

TESTING

SCRIPT

 

DISCUSSION

NOTES

AND

OBSERVATION

AND

OBSERVATION

NOTE TAKER

CAN SET UP

A RECORDING

STATION