User Research, Paper Prototyping Process and Pitfalls (UX103)


Published on

User Research, Paper Prototyping Process and Pitfalls

Published in: Design, Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

User Research, Paper Prototyping Process and Pitfalls (UX103)

  1. 1. UX 103Paper Prototyping Process and PitfallsCobbled Together by Peter SimonWednesday, May 22, 13
  2. 2. Paper prototyping, thefastest way to test aninterface. This is a creativeco-creation activity, not ausability study.Wednesday, May 22, 13
  3. 3. SetupWhat 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. 4. Setup ItemsFeedback DocInterface SketchesModerators GuideGoogle doc format for co-interviewer to take notes.Get a head start on analysis with a well structured docPaper, Pencils, Scissors,The Works.Whatever you do, don’t run out of things to play withQuestions to ask, and structureto follow.Should be clear enough that someone else can take overWednesday, May 22, 13
  5. 5. The ExerciseWhat to (not) doWednesday, May 22, 13
  6. 6. The ProcessExplain theProcessPreInterview?Present theSketches!Good for getting peopleon the same page,segmentation etc...Ta Da!Tip:Prime your participant toparticipate by telling themwhat will be expectedwhen. Process surprisesare bad.Why are we here?Explain WhyYou’re HereAskQuestionsDo they understand theapp based on a firstglance?Wednesday, May 22, 13
  7. 7. The Process cont.Clarifyfeedback fornotetakerRepeat asNecessaryHow wasthat? (ExitInterview)Keep your questions andinstigations formulaicWe good?“Could you pleasesummarize your feedbackand process on what wejust did?”They call it paperprototyping for a reasonRe ArrangetheInterfaceWednesday, May 22, 13
  8. 8. A B CAlways Be CommunicatingRemember, someone is taking notes. Ask yourparticipant to think out loud.Wednesday, May 22, 13
  9. 9. Avoid Leading QuestionsLeading questions are questions that suggests theparticular answer or contains the information theexaminer 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. 10. Questions Should Start ConversationsThe secret to good small talk is the question, don’t askfor 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. 11. The Ideal ParticipantIs RelaxedConsider providing beerA wise man once said:“Always user test on the old, the young, or the drunk.”Wednesday, May 22, 13
  12. 12. AnalysisLayout SuggestionsNow make sense of your sessions.Point of ViewWednesday, May 22, 13
  13. 13. User Profiles - Weigh Results AppropriatelyThe IntuitiveExplorerThe FastOperatorSelf DoubtersPeople who blast through interfaces,not necessarily reading. Digital nativesMethodical thinkers who areconcerned with getting things right.They take time to click.People who don’t trust their intuitionand wait for confirmation.Wednesday, May 22, 13
  14. 14. Socialize ResultsWho 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. 15. Oh and,Remember the immortalwords of Douglas Adams...Wednesday, May 22, 13
  16. 16. Don’tPanicWednesday, May 22, 13