This document outlines the paper prototyping process for testing interfaces. It recommends brainstorming test questions, gathering materials like paper and pencils, and explaining the process to participants before showing paper sketches of the interface. The moderator is advised to ask open-ended questions to start conversations, avoid leading questions, and clarify feedback for the note-taker. Multiple iterations may be needed. Results should be analyzed by user profiles and socialized in a shared document, with suggestions for improvements and next steps. Throughout, clear communication and avoiding surprises for participants is emphasized.

1. UX 103
Paper Prototyping Process and Pitfalls
Cobbled Together by Peter Simon
Wednesday, May 22, 13

2. Paper prototyping, the
fastest way to test an
interface. This is a creative
co-creation activity, not a
usability study.
Wednesday, May 22, 13

3. Setup
What are you testing?
Brainstorm a list of questions that you need to answer.
This helps you figure out what you’re doing.
Wednesday, May 22, 13

4. Setup Items
Feedback Doc
Interface Sketches
Moderators Guide
Google doc format for co-
interviewer to take notes.
Get a head start on analysis with a well structured doc
Paper, Pencils, Scissors,
The Works.
Whatever you do, don’t run out of things to play with
Questions to ask, and structure
to follow.
Should be clear enough that someone else can take over
Wednesday, May 22, 13

5. The Exercise
What to (not) do
Wednesday, May 22, 13

6. The Process
Explain the
Process
Pre
Interview?
Present the
Sketches!
Good for getting people
on the same page,
segmentation etc...
Ta Da!Tip:
Prime your participant to
participate by telling them
what will be expected
when. Process surprises
are bad.
Why are we here?
Explain Why
You’re Here
Ask
Questions
Do they understand the
app based on a first
glance?
Wednesday, May 22, 13

7. The Process cont.
Clarify
feedback for
notetaker
Repeat as
Necessary
How was
that? (Exit
Interview)
Keep your questions and
instigations formulaic
We good?“Could you please
summarize your feedback
and process on what we
just did?”
They call it paper
prototyping for a reason
Re Arrange
the
Interface
Wednesday, May 22, 13

8. A B C
Always Be Communicating
Remember, someone is taking notes. Ask your
participant to think out loud.
Wednesday, May 22, 13

9. Avoid Leading Questions
Leading questions are questions that suggests the
particular answer or contains the information the
examiner is looking to have confirmed.
“Do you think this should go here?”
“yes”
You just missed an opportunity for a juicy answer.
Wednesday, May 22, 13

10. Questions Should Start Conversations
The secret to good small talk is the question, don’t ask
for confirmation, ask for explanation, ask for the story.
“How might this communicate better?”
“Oh, well... {A} {B} {C}, maybe {D}...”
“Where did {D} come from?”
Wednesday, May 22, 13

11. The Ideal Participant
Is Relaxed
Consider providing beer
A wise man once said:
“Always user test on the old, the young, or the drunk.”
Wednesday, May 22, 13

12. Analysis
Layout Suggestions
Now make sense of your sessions.
Point of View
Wednesday, May 22, 13

13. User Profiles - Weigh Results Appropriately
The Intuitive
Explorer
The Fast
Operator
Self Doubters
People who blast through interfaces,
not necessarily reading. Digital natives
Methodical thinkers who are
concerned with getting things right.
They take time to click.
People who don’t trust their intuition
and wait for confirmation.
Wednesday, May 22, 13

14. Socialize Results
Who needs to see these results?
(Are your results wrong?)
Google Doc’s work best for now.
Task / Page Observations Suggestions Include in next build?
(Summary) (What Happened) (This Happened) (Proposed Rejected Accepted)
Wednesday, May 22, 13

15. Oh and,
Remember the immortal
words of Douglas Adams...
Wednesday, May 22, 13

16. Don’t
PanicWednesday, May 22, 13