Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Intro to UX Methods (KCDC 2013)

1,191 views

Published on

The Intro to UX Methods talk as delivered at KCD

Published in: Technology
  • Be the first to comment

Intro to UX Methods (KCDC 2013)

  1. 1. KCDC 2013Introduction toUser Experience MethodsIntroduction toUser Experience Methods1  Danielle Gobert Cooley@dgcooley03 May 2013 #KCDC2013
  2. 2. KCDC 20132  The image cannot be displayed. Your computer may not have enough memory to open the image, or the image may have been corrupted. Restart your computer, and then open the file again. If the red x still appears, you may have to delete the image and then insert it again.03  May  2013                                      @dgcooley                                        #KCDC2013    
  3. 3. KCDC 2013Danielle Gobert Cooley03  May  2013                                      @dgcooley                                        #KCDC2013    3  danielle@dgcooley.comTheimagecannotbe@dgcooley14 years as a UX SpecialistBE, Biomedical and Electrical Engineering – Vanderbilt UniversityMS, Human Factors in Information Design – Bentley UniversitySelected  Clients          http://linkedin.com/in/dgcooley
  4. 4. KCDC 2013Important Things toKnow About UX Methods4  03  May  2013                                      @dgcooley                                        #KCDC2013    
  5. 5. KCDC 2013Please Remember5  The purpose of these methods is toinform your design.They are not validation methods.03  May  2013                                      @dgcooley                                        #KCDC2013    
  6. 6. KCDC 2013Let Me Repeat That6  The purpose of these methods is toinform your design.They are not validation methods.03 May 2013 @dgcooley #KCDC2013
  7. 7. KCDC 2013You Are Not Your User7  YOUNOTYOU03  May  2013                                      @dgcooley                                        #KCDC2013    
  8. 8. KCDC 2013Why Do It? To Avoid Ending Up Here8  03  May  2013                                      @dgcooley                                        #KCDC2013    
  9. 9. KCDC 2013One More Thing…9  The purpose of these methods is toinform your design.They are not validation methods.03  May  2013                                      @dgcooley                                        #KCDC2013    
  10. 10. KCDC 2013Usability Study10  03  May  2013                                      @dgcooley                                        #KCDC2013    
  11. 11. KCDC 2013Ques=ons  It  Answers*  •  How easy or difficult is it to use the product?•  How efficiently do people use the product?•  Do the users understand the product’s terminology?•  Do the controls make sense?•  Can people find the information they are seeking?11  * Depends in part on prototype fidelity … more on that in a few moments.03  May  2013                                      @dgcooley                                        #KCDC2013    
  12. 12. KCDC 2013How It’s Done1.  Recruit representative endusers.2.  Observe impartially as theyattempt to perform taskswith a prototype.3.  Typically, participants areasked to think aloud asthey use the prototype toperform the tasks. Thisprovides insight into WHYcertain interface elementsare confusing and whatmight work better.12  Tips…– Recruiting the right users iskey!– Avoid bias everywhere – intask phrasing, your and yourobservers’ body language, andin verbal questions asked.– Recordings are great, buthuge time sucks.– Quantitative studies oftenaren’t worth it.03  May  2013                                      @dgcooley                                        #KCDC2013    
  13. 13. KCDC 2013A Note About Prototype Fidelity13  03  May  2013                                      @dgcooley                                        #KCDC2013    
  14. 14. KCDC 2013Advantages•  Controlled setting means easier logistics.•  Recording and observing is easier, too.•  For the rare quantitative study, lab-basedtesting makes it easier to use such toolsas Morae or Ovo.•  Lab-based testing has fewer variables tocontrol, which can be a factor for morerigid studies.14  03  May  2013                                      @dgcooley                                        #KCDC2013    
  15. 15. KCDC 2013Disadvantages•  Lab setting provides no context of use.•  Labs can be expensive to rent or build–  (but they don’t have to be)•  Participants are sometimes timid in a lab setting15  03  May  2013                                      @dgcooley                                        #KCDC2013    
  16. 16. KCDC 2013Field Study16  03  May  2013                                      @dgcooley                                        #KCDC2013    
  17. 17. KCDC 2013Questions It Answers•  How do environmental circumstances affect theusability of the product?•  How have people worked around issues with theproduct?17  03  May  2013                                      @dgcooley                                        #KCDC2013    
  18. 18. KCDC 2013How It’s Done1.  Recruit representativeend users.2.  Observe impartially in theenvironment in which theproduct will be used asthey attempt to performtasks with a prototype.3.  Collect artifacts.18  03  May  2013                                      @dgcooley                                        #KCDC2013    
  19. 19. KCDC 2013Advantages•  Gathers contextual data–  Ambient light, noise–  Distractions•  Participants usually lessintimidated•  Much more convenient forparticipants, so recruitingcan be easier19  Contextual Inquiry?Though the terms are oftenused interchangeably,Contextual Inquiry is actually atype of field study that followsa very specific format.03  May  2013                                      @dgcooley                                        #KCDC2013    
  20. 20. KCDC 2013Disadvantages•  Logistics are more difficult for researchers.•  Observation is more challenging.•  Recording is more challenging.•  Security issues sometimes prohibit photographs orother recording.20  03  May  2013                                      @dgcooley                                        #KCDC2013    
  21. 21. KCDC 2013Card Sort21  03  May  2013                                      @dgcooley                                        #KCDC2013    
  22. 22. KCDC 2013Questions It Answers•  How would the users organize the product’s content andfeatures?•  Do the users largely agree on how the content shouldbe organized?•  Do the users agree with the categorizations proposedby the project team?22  03  May  2013                                      @dgcooley                                        #KCDC2013    
  23. 23. KCDC 2013How It’s Done1.  Recruit representativeend users.2.  Identify content items tobe categorized3.  Participants sort thecontent items intogroupings that makesense to them.23  Two types …– In an OPEN card sort,participants create thecategories.– In a CLOSED card sort,the researcher establishesthe categories.03  May  2013                                      @dgcooley                                        #KCDC2013    
  24. 24. KCDC 2013Advantages•  Incredibly inexpensive•  Done very quickly with remoteevaluation tools.•  Asynchronous, so scheduling is not anissue. Participants take part at theirconvenience.24  03  May  2013                                      @dgcooley                                        #KCDC2013    
  25. 25. KCDC 2013Disadvantages•  More complicated with large sets of cards.•  Really, there’s almost no reason NOT to do a card sort,unless you don’t plan to use the results.25  03  May  2013                                      @dgcooley                                        #KCDC2013    
  26. 26. KCDC 2013Tree Test26  03  May  2013                                      @dgcooley                                        #KCDC2013    
  27. 27. KCDC 2013Questions It Answers•  Can users find content in the proposed navigation?•  Do the proposed group labels correctly reflect thecontent within them?27  03  May  2013                                      @dgcooley                                        #KCDC2013    
  28. 28. KCDC 2013How It’s Done1.  Recruit representativeend users.2.  Set up study with IA tobe evaluated.3.  Give participants specificcontent elements to findin that architecture.28  03  May  2013                                      @dgcooley                                        #KCDC2013    
  29. 29. KCDC 2013Advantages•  Incredibly inexpensive•  Done very quickly with remoteevaluation tools.•  Asynchronous, so scheduling is not anissue. Participants take part at theirconvenience.29  Yep. Just like cardsorting!03  May  2013                                      @dgcooley                                        #KCDC2013    
  30. 30. KCDC 2013Disadvantages•  The full IA and nav structuremust be created in order toexecute a tree test, sothere is significantinvestment in the“prototype,” if you will.30  Tree Test vs. Card Sort– An OPEN Card Sortgenerates an informationarchitecture.– A CLOSED Card sort usuallyevaluates high-level labeling.– A Tree Test evaluatesfindability in an existinginformation architecture.OK. This one IS avalidation method.03  May  2013                                      @dgcooley                                        #KCDC2013    
  31. 31. KCDC 2013Survey31  03  May  2013                                      @dgcooley                                        #KCDC2013    
  32. 32. KCDC 2013Questions It Answers•  What is the users’ opinion about various aspects ofthe product?•  How do users believe they use or will use theproduct?32  03  May  2013                                      @dgcooley                                        #KCDC2013    
  33. 33. KCDC 2013How It’s Done1.  Recruit participants2.  Write survey3.  Relax while the data rolls right in.33  03  May  2013                                      @dgcooley                                        #KCDC2013    
  34. 34. KCDC 2013Advantages•  Cheap•  Fast•  Remote•  Easy data collection•  Large number of participants34  03  May  2013                                      @dgcooley                                        #KCDC2013    
  35. 35. KCDC 2013Disadvantages•  Data are self-reported.–  What people do is not the same as what people SAY they do.•  Good question curation is surprisingly challenging.35  03  May  2013                                      @dgcooley                                        #KCDC2013    
  36. 36. KCDC 2013Expert Review36  03  May  2013                                      @dgcooley                                        #KCDC2013    
  37. 37. KCDC 2013Questions It Answers•  Does the product comply with conventions and bestpractices?•  Has the expert seen issues in the past with any of thedesign elements or interaction techniques used in theproduct?37  03  May  2013                                      @dgcooley                                        #KCDC2013    
  38. 38. KCDC 2013How It’s Done•  An experienced UXSpecialist analyzes theproduct, looking forcommon mistakes orinterface elements orinteractions that are notconsistent with bestpractices.38  Heuristic Evaluation?Though this term is thrownaround a lot, a HeuristicEvaluation is really aspecialized type of ExpertReview.03  May  2013                                      @dgcooley                                        #KCDC2013    
  39. 39. KCDC 2013Advantages•  Considerably less expensive than lab or field studies•  Often relatively fast – again, as compared to lab orfield studies.39  03  May  2013                                      @dgcooley                                        #KCDC2013    
  40. 40. KCDC 2013Disadvantages•  No actual end-user perspective.•  Experts vary. J40  03  May  2013                                      @dgcooley                                        #KCDC2013    
  41. 41. KCDC 2013Other Techniques41  03  May  2013                                      @dgcooley                                        #KCDC2013    
  42. 42. KCDC 2013In No Particular Order…•  Journaling Studies – Users keep a journal of theirinteractions (good and bad) with the product.•  A/B Testing – Two different versions of a product areplaced online and success rates analyzed.•  Analytics – Web site or product metrics are analyzedto determine user success or failure.•  Personas – Descriptive profiles of representative endusers. This is actually an output of field research.42  03  May  2013                                      @dgcooley                                        #KCDC2013    
  43. 43. KCDC 2013Recap & Additional Resources•  User Experience is important. Really.•  These are NOT validation techniques!•  There are a lot of methods to choose from, andone will yield an answer to your questions.43  03  May  2013                                      @dgcooley                                        #KCDC2013    

×