This document provides guidance for testing paper prototypes using a Wizard of Oz approach, where users interact with a system operated secretly by a human. It recommends introducing the test and getting permission to record before providing scenarios for tasks like finding an open tire shop. Testers should encourage thinking aloud and not provide directions, observing initial emotions and how users complete good and bad tasks to evaluate the prototype's usability.

1. Testing Paper Prototypes

2. Wizard of Oz Approach
• Users interact with a system they
presume to be autonomous
• In reality, the system is operated
by a human being (who should
remain unseen)

4. Conducting the test
Before the test
• General icebreaking
(introducing yourself, the
application)
• Encourage the user to talk
aloud and not worry
• If need be, ask the user
whether it’s okay to record
their process
• Ask some background
questions
During the test
• Initial emotions
• Hand out scenarios/tasks
• Encourage the user to think
aloud!
• Don’t give the user any
directions on how to use
the app

5. Tasks
Good
• “Your car tire broke on a
Sunday. Find an open tire
repair shop near your
location and access their
website to see their
pricing.”
Bad
• “Use the map interface to
find tire repair shops. Upon
finding one, tap on it and
click on the website URL, so
that you’ll be redirected to
their website.”

6. Be creative!

7. DEMO