Intro to User Research
Upcoming SlideShare
Loading in...5
×
 

Intro to User Research

on

  • 1,559 views

 

Statistics

Views

Total Views
1,559
Views on SlideShare
1,550
Embed Views
9

Actions

Likes
9
Downloads
60
Comments
0

6 Embeds 9

http://us-w1.rockmelt.com 2
http://paper.li 2
http://www.linkedin.com 2
http://a0.twimg.com 1
https://twitter.com 1
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Intro to User Research Intro to User Research Presentation Transcript

  • Friday, October 21, 2011
  • MATT TONAK COMMUNITY MANAGERFriday, October 21, 2011
  • THE NERDERY HOURS WORKED SINCE 2003 PROJECTS DOGS IN OUR OFFICE BIKE COMMUTERS 821,217 4334 HOURS WORKED, LAST 12 MONTHS EIGHT 6 AVERAGE JANUARY TEMPERATURE º PEOPLE WHO WORK AT THE NERDERY TWO HUNDRED SIXTY-ONE FOUR WE HELP OUR PARTNERS GET BIG IDEAS OUT OF THEIR HEADS AND ONTO THEIR CLIENTS’ WEBSITES HTTP://WWW.NERDERY.COM TWITTER: @THE_NERDERYFriday, October 21, 2011
  • HOW TO PARTICIPATE Using the questions panels in the GoToMeeting app On Twitter @The_Nerdery Send us an email at primers@nerdery.comFriday, October 21, 2011
  • INTRO TO USER RESEARCH INTERACTIVE PRIMER SERIESFriday, October 21, 2011
  • ZACK USER EXPERIENCE DESIGNERFriday, October 21, 2011
  • MIKE DIRECTOR OF USER EXPERIENCEFriday, October 21, 2011
  • WHAT IS UX? User Goals Application Business GoalsFriday, October 21, 2011
  • WHAT IS UX? Aligning user behavior and motivations with business objectives through interaction design User Goals Business Goals ApplicationFriday, October 21, 2011
  • WHAT IS UX?Friday, October 21, 2011
  • WHAT IS UX? UX is not part of the process...Friday, October 21, 2011
  • WHAT IS UX? UX is not part of the process... ...it is the process.Friday, October 21, 2011
  • A WORD ABOUT PROCESSFriday, October 21, 2011
  • ^ A WORD ABOUT PROCESSFriday, October 21, 2011
  • ^ (OR SEVERAL) A WORD ABOUT PROCESSFriday, October 21, 2011
  • DESIGN PHILOSOPHIESFriday, October 21, 2011
  • DESIGN PHILOSOPHIES There is no “one-size-fits-all”Friday, October 21, 2011
  • DESIGN PHILOSOPHIES There is no “one-size-fits-all” Self DesignFriday, October 21, 2011
  • DESIGN PHILOSOPHIES There is no “one-size-fits-all” Self Design Genius DesignFriday, October 21, 2011
  • DESIGN PHILOSOPHIES There is no “one-size-fits-all” Self Design Genius Design User-Centered DesignFriday, October 21, 2011
  • DESIGN SOLVES PROBLEMSFriday, October 21, 2011
  • DESIGN SOLVES PROBLEMS ...now let’s cook some dinnerFriday, October 21, 2011
  • SELF DESIGN SOLVING YOUR OWN PROBLEMFriday, October 21, 2011
  • SELF DESIGN SOLVING YOUR OWN PROBLEM I know what I want for dinner. Self Design is cooking for yourself.Friday, October 21, 2011
  • SELF DESIGN SOLVING YOUR OWN PROBLEM I know what I want for dinner. Self Design is cooking for yourself. Pretty simple.Friday, October 21, 2011
  • GENIUS DESIGN SOLVING A PROBLEM YOU’VE SOLVED BEFOREFriday, October 21, 2011
  • GENIUS DESIGN SOLVING A PROBLEM YOU’VE SOLVED BEFORE If I’ve made dinner for Mike (or people like him) many times before, I rely on my domain specific experience to cook dinner for Mike.Friday, October 21, 2011
  • GENIUS DESIGN SOLVING A PROBLEM YOU’VE SOLVED BEFORE If I’ve made dinner for Mike (or people like him) many times before, I rely on my domain specific experience to cook dinner for Mike. I don’t actually cook for Mike. #justsayin’Friday, October 21, 2011
  • GENIUS DESIGN THERE’S A CATCHFriday, October 21, 2011
  • GENIUS DESIGN THERE’S A CATCH Genius Design presupposes that you originally did your research to define the problem.Friday, October 21, 2011
  • USER-CENTERED DESIGN AKA: UX DESIGNFriday, October 21, 2011
  • USER-CENTERED DESIGN AKA: UX DESIGN A UX PROCESS STARTS WITH UNDERSTANDING THE PROBLEMFriday, October 21, 2011
  • USER-CENTERED DESIGN FOCUSES ON BEHAVIOR, USE & CONTEXT.Friday, October 21, 2011
  • USER-CENTERED DESIGN FOCUSES ON BEHAVIOR, USE & CONTEXT. BUILDING EMPATHY.Friday, October 21, 2011
  • USER-CENTERED DESIGN HOW DO WE DO THAT?Friday, October 21, 2011
  • USER-CENTERED DESIGN HOW DO WE DO THAT? USER RESEARCHFriday, October 21, 2011
  • USER RESEARCH IS NOT MARKETING RESEARCHFriday, October 21, 2011
  • USER RESEARCH IS NOT MARKETING RESEARCH ...but there is some overlapFriday, October 21, 2011
  • USER RESEARCH IS NOT MARKETING RESEARCH ...but there is some overlapFriday, October 21, 2011
  • USER RESEARCH We do this IS NOT MARKETING RESEARCH ...but there is some overlapFriday, October 21, 2011
  • USER RESEARCH We do this IS NOT MARKETING RESEARCH ...but there is some overlapFriday, October 21, 2011
  • USER RESEARCH We do this IS NOT We DON’T do this MARKETING RESEARCH ...but there is some overlapFriday, October 21, 2011
  • USER RESEARCH MARKETING RESEARCHFriday, October 21, 2011
  • USER RESEARCH MARKETING RESEARCH Preferences Opinions Likes DesiresFriday, October 21, 2011
  • USER RESEARCH MARKETING RESEARCH Behavior Preferences Needs Opinions Goals Likes Tasks Desires Mental & Physical ContextFriday, October 21, 2011
  • RESEARCH SPECTRUM Indi Young - Mental Models: Rosenfeld Media http://www.flickr.com/photos/rosenfeldmedia/2159500714/in/set-72157603511616271/Friday, October 21, 2011
  • RESEARCH SPECTRUM Indi Young - Mental Models: Rosenfeld Media http://www.flickr.com/photos/rosenfeldmedia/2159500714/in/set-72157603511616271/Friday, October 21, 2011
  • RESEARCH SPECTRUM overlap Indi Young - Mental Models: Rosenfeld Media http://www.flickr.com/photos/rosenfeldmedia/2159500714/in/set-72157603511616271/Friday, October 21, 2011
  • WHY DO USER RESEARCH?Friday, October 21, 2011
  • WHY DO USER RESEARCH? Remember when we said that design solves problems?Friday, October 21, 2011
  • WHY DO USER RESEARCH? Remember when we said that design solves problems? Remember when we said that a UX process starts with defining the problem?Friday, October 21, 2011
  • WHY DO USER RESEARCH? Remember when we said that a UX process starts with defining the problem?Friday, October 21, 2011
  • WHY DO USER RESEARCH?Friday, October 21, 2011
  • WHY DO USER RESEARCH?Friday, October 21, 2011
  • WHY DO USER RESEARCH? Research tells us what the problem is.Friday, October 21, 2011
  • WHY DO USER RESEARCH? Research tells us what the problem is. Research tells us why it’s a problem.Friday, October 21, 2011
  • WHY DO USER RESEARCH? Research tells us what the problem is. Research tells us why it’s a problem. Research shows us how to fix it.Friday, October 21, 2011
  • BENEFITS OF USER RESEARCHFriday, October 21, 2011
  • BENEFITS OF USER RESEARCH Throughly defines the problem.Friday, October 21, 2011
  • BENEFITS OF USER RESEARCH Throughly defines the problem. Informs design decisions.Friday, October 21, 2011
  • BENEFITS OF USER RESEARCH Throughly defines the problem. Informs design decisions. Provides direction & priority.Friday, October 21, 2011
  • BENEFITS OF USER RESEARCH Throughly defines the problem. SHOWS US THE “WHAT” Informs design decisions. Provides direction & priority.Friday, October 21, 2011
  • BENEFITS OF USER RESEARCH Throughly defines the problem. SHOWS US THE “WHAT” Informs design decisions. TEACHES US THE “WHY” Provides direction & priority.Friday, October 21, 2011
  • BENEFITS OF USER RESEARCH Throughly defines the problem. SHOWS US THE “WHAT” Informs design decisions. TEACHES US THE “WHY” Provides direction & priority. GUIDES US TO THE “HOW”Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: “WHAT” “WHY” “HOW”Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: “WHAT” “We need a website redesign” “WHY” “HOW”Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “WHY” “HOW”Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t “WHY” working for us” “HOW”Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t There are usability “WHY” working for us” flaws in the design “HOW”Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t There are usability “WHY” working for us” flaws in the design “We should update “HOW” the look & feel”Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t There are usability “WHY” working for us” flaws in the design “We should update We need to design clearer “HOW” the look & feel” call to action buttons.Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t There are usability “WHY” working for us” flaws in the design “We should update We need to design clearer “HOW” the look & feel” call to action buttons.Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t There are usability “WHY” working for us” flaws in the design “We should update We need to design clearer “HOW” the look & feel” call to action buttons.Friday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t There are usability “WHY” working for us” flaws in the design “We should update We need to design clearer “HOW” the look & feel” call to action buttons. Vague & UndefinedFriday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t There are usability “WHY” working for us” flaws in the design “We should update We need to design clearer “HOW” the look & feel” call to action buttons. Vague & UndefinedFriday, October 21, 2011
  • EXAMPLE PROJECT NEEDS Stated: What Research Tells Us: The website doesn’t meet “WHAT” “We need a website redesign” users’ expectations “The current site isn’t There are usability “WHY” working for us” flaws in the design “We should update We need to design clearer “HOW” the look & feel” call to action buttons. Vague & Undefined Clear & ActionableFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUALITATIVE vs. QUANTITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUALITATIVE X vs. QUANTITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUALITATIVE X vs. QUANTITATIVE Just rememberFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUALITATIVE X vs. QUANTITATIVE Just remember We need both!Friday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE Objective X vs. QUALITATIVE Subjective “Measurable” “Non-measurable” Numerical Data NOT Numerical Statistics ConceptsFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVE Page Views Bounce Rate Time On Site Yes/No True/FalseFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVE Page Views Expectations Bounce Rate Reactions Time On Site Confusion Yes/No Comprehension True/False BehaviorFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUALITATIVE QUANTITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE informs QUALITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE informs QUALITATIVEFriday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE informs QUALITATIVE “WHAT”Friday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE informs QUALITATIVE “WHAT”Friday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE informs QUALITATIVE “WHAT” “WHY”Friday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVE “WHAT” informs “WHY”Friday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVE “WHAT” informs “WHY” i.e. Sign-up page bounce rate it high.Friday, October 21, 2011
  • BEWARE OF THE DATA TYPE QUANTITATIVE QUALITATIVE “WHAT” informs “WHY” i.e. Sign-up page bounce rate it high. i.e. Call to action text is confusing.Friday, October 21, 2011
  • WHEN SHOULD YOU DO USER RESEARCH? Timeframe Beginning of the project During Design Production Project Completion - re-enforce direction - inform direction & scope - gauge progress/success Benefit - validate design decisions - throughly defines the problem - guides product direction - acquire design feedback at - provides insights for next steps - discover areas for improvement significantly lower cost - Contextual Inquiry - Usability Testing - Usability Testing Example - Field Study/Ethnography - Card Sorting - Site Search Analytics Method/Use - User Interviews - Personas - Web Analytics - Surveys - Mental Models - A/B Testing/Multivariate TestingFriday, October 21, 2011
  • Friday, October 21, 2011
  • BONUS ROUNDFriday, October 21, 2011
  • BONUS ROUND ONGOING RESEARCHFriday, October 21, 2011
  • BONUS ROUND ONGOING RESEARCH How:Friday, October 21, 2011
  • BONUS ROUND ONGOING RESEARCH How: - Create a solid and sustainable research plan for a continuous feedback loop from your customers/usersFriday, October 21, 2011
  • BONUS ROUND ONGOING RESEARCH How: - Create a solid and sustainable research plan for a continuous feedback loop from your customers/users Why:Friday, October 21, 2011
  • BONUS ROUND ONGOING RESEARCH How: - Create a solid and sustainable research plan for a continuous feedback loop from your customers/users Why: - Your audience changes and evolves over timeFriday, October 21, 2011
  • BONUS ROUND ONGOING RESEARCH How: - Create a solid and sustainable research plan for a continuous feedback loop from your customers/users Why: - Your audience changes and evolves over time - Your product/service/website will attract new audience segmentsFriday, October 21, 2011
  • BONUS ROUND ONGOING RESEARCH How: - Create a solid and sustainable research plan for a continuous feedback loop from your customers/users Why: - Your audience changes and evolves over time - Your product/service/website will attract new audience segments -Other products/services/websites introduce new expectations for interacting with your informationFriday, October 21, 2011
  • WHEN SHOULD YOU DO USER RESEARCH? Timeframe Beginning of the project During Design Production Project Completion - re-enforce direction - inform direction & scope - gauge progress/success Benefit - validate design decisions - throughly defines the problem - guides product direction - acquire design feedback at - provides insights for next steps - discover areas for improvement significantly lower cost - Contextual Inquiry - Usability Testing - Usability Testing Example - Field Study/Ethnography - Card Sorting - Site Search Analytics Method/Use - User Interviews - Personas - Web Analytics - Surveys - Mental Models - A/B Testing/Multivariate TestingFriday, October 21, 2011
  • WHEN SHOULD YOU DO USER RESEARCH? Timeframe Beginning of the project During Design Production Project Completion - re-enforce direction - inform direction & scope - gauge progress/success Benefit - validate design decisions - throughly defines the problem - guides product direction - acquire design feedback at - provides insights for next steps - discover areas for improvement significantly lower cost - Contextual Inquiry - Usability Testing - Usability Testing Example - Field Study/Ethnography - Card Sorting - Site Search Analytics Method/Use - User Interviews - Personas - Web Analytics - Surveys - Mental Models - A/B Testing/Multivariate TestingFriday, October 21, 2011
  • WHEN SHOULD YOU DO USER RESEARCH? Timeframe Beginning of the project During Design Production Project Completion Let’s talk about a few in more detail - re-enforce direction - inform direction & scope - gauge progress/success Benefit - validate design decisions - throughly defines the problem - guides product direction - acquire design feedback at - provides insights for next steps - discover areas for improvement significantly lower cost - Contextual Inquiry - Usability Testing - Usability Testing Example - Field Study/Ethnography - Card Sorting - Site Search Analytics Method/Use - User Interviews - Personas - Web Analytics - Surveys - Mental Models - A/B Testing/Multivariate TestingFriday, October 21, 2011
  • CONTEXTUAL INQUIRYFriday, October 21, 2011
  • WHAT IS CONTEXTUAL INQUIRY? Fancy Definition:Friday, October 21, 2011
  • WHAT IS CONTEXTUAL INQUIRY? Fancy Definition: a field data-gathering technique that studies a few carefully selected individuals in depth to arrive at a fuller understanding of the work practice across all customers.Friday, October 21, 2011
  • WHAT IS CONTEXTUAL INQUIRY? Fancy Definition: a field data-gathering technique that studies a few carefully selected individuals in depth to arrive at a fuller understanding of the work practice across all customers. - Hugh Beyer and Karen Holtzblatt - Contextual Design: Defining Customer-Centered SystemsFriday, October 21, 2011
  • WHAT IS CONTEXTUAL INQUIRY? Fancy Definition: a field data-gathering technique that studies a few carefully selected individuals in depth to arrive at a fuller understanding of the work practice across all customers. - Hugh Beyer and Karen Holtzblatt - Contextual Design: Defining Customer-Centered Systems Non-Nerd Version:Friday, October 21, 2011
  • WHAT IS CONTEXTUAL INQUIRY? Fancy Definition: a field data-gathering technique that studies a few carefully selected individuals in depth to arrive at a fuller understanding of the work practice across all customers. - Hugh Beyer and Karen Holtzblatt - Contextual Design: Defining Customer-Centered Systems Non-Nerd Version: go watch people work in their own context.Friday, October 21, 2011
  • WHAT IS CONTEXTUAL INQUIRY? Fancy Definition: a field data-gathering technique that studies a few carefully selected individuals in depth to arrive at a fuller understanding of the work practice across all customers. - Hugh Beyer and Karen Holtzblatt - Contextual Design: Defining Customer-Centered Systems Non-Nerd Version: go watch people work in their own context. - UsFriday, October 21, 2011
  • THE “HOW-TO” OF CONTEXTUAL INQUIRY 1. Recruiting Contact & schedule the people you will observe. THIS IS THE MOST IMPORTANT STEP. 2. Research Plan Establish a clear focus for what you’re seeking to understand & what you hope to learn. 3. Observe Watch users completing relevant goals & tasks in their own context. 4. Analyze Review what you learned. What patterns emerged? 5. Report Create appropriate documentation to communicate what you found to the team.Friday, October 21, 2011
  • WHAT’S THE BENEFIT OF CONTEXTUAL INQUIRY? Are there current frustrations or problems with the existing design? What about with their Issues physical environment or other systems and processes? Can the new design support those? What are the high level priorities of the people using the current design? Goals What are they trying to accomplish? Tasks What are the steps people are taking to accomplish those goals? Environment What is their physical location like? How does it impact the design or how they use it? What other hardware or software are they using to do their work? Can (or should) they be Applications integrated? Can the new design eliminate the need of these factors?Friday, October 21, 2011
  • WHAT’S THE BENEFIT OF CONTEXTUAL INQUIRY? Work-Arounds Are people creating ways to work around a poor design now? Triggers What causes someone to begin down a path of completing a goal? Are there several ways in which people are accomplishing the same goal or task? Should the Variation(s) design support one? Both? Partners Who does the person work with to accomplish a goal or task? “Crutches” Do people have “cheat-sheets” or other materials to help them accomplish goals and tasks?Friday, October 21, 2011
  • RECOMMENDATIONS FOR CONTEXTUAL INQUIRY Recruiting Be sure to observe an appropriate, representative sample of your target audience. Aim for 3-5 participants separately. Timeline Allow 1-2 weeks for recruiting effort. (Varies depending on the project & participant availability) Allow 1-2 weeks for conducting the research. (Assuming 5 participants) Allow AT LEAST 1 week for analysis Allow 1 week to create a report. Approximately 4-8 weeks totalFriday, October 21, 2011
  • USABILITY TESTINGFriday, October 21, 2011
  • WHAT IS USABILITY TESTING? Definition:Friday, October 21, 2011
  • WHAT IS USABILITY TESTING? Definition: a form of gathering feedback from actual users of a design by having them attempt to complete intended goals and tasks with said design.Friday, October 21, 2011
  • THE “HOW-TO” OF USABILITY TESTING Determine who you will conduct usability testing with, write a screener to ensure you recruit 1. Recruiting your target audience from the responses & schedule the participants. Again, a CRITICAL step. Where will the tests take place? What will the research cover? As before, Establish a clear 2. Research Plan focus for what you hope to learn. 3. Conduct Tests Conduct the test (ideally with an experience moderator) & observe, while taking notes. 4. Analyze Discuss test results with any participating team members & review recordings if available. 5. Report Create appropriate documentation that conveys the findings from the research.Friday, October 21, 2011
  • WHAT’S THE BENEFIT OF USABILITY TESTING? Expectations Is the solution designed meeting expectations of those intended to use it? Task Completion Can the users complete the available tasks of the design? Level of difficulty If so, how difficult was it for them to complete the task(s)? Why? Path Taken What were the steps involved in completing a given task? Impression Did the user(s) understand the overall message and intent that the design meant to convey?Friday, October 21, 2011
  • VARIATIONS OF USABILITY TESTING In-Person, Moderated Sessions are conducted at a physical location with a live, in-person moderator leading the session(s) with participants. Research is conducted via “live recruiting” from an existing website. Remote, Moderated Participants are immediately connected with a moderator from a remote location. Sessions are conducted using an online service that allows users to Remote, Un-moderated participate at their convenience, without a moderator. Usability testing done with minimal recruiting effort and logistical Guerilla planning. Common locations are coffee shops, bars, offices, etc.Friday, October 21, 2011
  • VARIATIONS OF USABILITY TESTING Good In-Person, Moderated Sessions are conducted at a physical location with a live, in-person moderator leading the session(s) with participants. Research is conducted via “live recruiting” from an existing website. Remote, Moderated Participants are immediately connected with a moderator from a remote location. Sessions are conducted using an online service that allows users to Remote, Un-moderated participate at their convenience, without a moderator. Usability testing done with minimal recruiting effort and logistical Guerilla planning. Common locations are coffee shops, bars, offices, etc.Friday, October 21, 2011
  • VARIATIONS OF USABILITY TESTING Better In-Person, Moderated Sessions are conducted at a physical location with a live, in-person moderator leading the session(s) with participants. Research is conducted via “live recruiting” from an existing website. Remote, Moderated Participants are immediately connected with a moderator from a remote location. Sessions are conducted using an online service that allows users to Remote, Un-moderated participate at their convenience, without a moderator. Usability testing done with minimal recruiting effort and logistical Guerilla planning. Common locations are coffee shops, bars, offices, etc.Friday, October 21, 2011
  • VARIATIONS OF USABILITY TESTING Best In-Person, Moderated Sessions are conducted at a physical location with a live, in-person moderator leading the session(s) with participants. Research is conducted via “live recruiting” from an existing website. Remote, Moderated Participants are immediately connected with a moderator from a remote location. Sessions are conducted using an online service that allows users to Remote, Un-moderated participate at their convenience, without a moderator. Usability testing done with minimal recruiting effort and logistical Guerilla planning. Common locations are coffee shops, bars, offices, etc.Friday, October 21, 2011
  • RECOMMENDATIONS FOR USABILITY TESTING Do your own recruiting if possible. If this is not possible, work closely with a recruiting agency Recruiting to ensure the participants being recruited match your target audience. (especially for the particular research you’re doing) Aim for 5-10 participants. (dependent on the study) Timeline Allow 1-2 weeks for recruiting effort. (Varies depending on the recruiting method) Allow 1 week for conducting the tests. (Assuming 5 participants) Allow 3 days to 1 week for analysis. Allow 3 days to 1 week to create a report. Approximately 3-6 weeks totalFriday, October 21, 2011
  • PUTTING IT ALL TOGETHERFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGNFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN “We need to redesign our web application to increase customer engagement”Friday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN “We need to redesign our web application to increase customer engagement” GO!Friday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGNFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN Let’s get started:Friday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN Let’s get started: THE “WHAT”Friday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN Let’s get started: THE “WHAT” Targeted SurveysFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN Let’s get started: THE “WHAT” Targeted Surveys Web AnalyticsFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGNFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN THE “WHY”Friday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN THE “WHY” User InterviewsFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN THE “WHY” User Interviews Contextual InquiryFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGNFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN THE “HOW”Friday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN THE “HOW” Usability TestingFriday, October 21, 2011
  • FICTIONAL PROJECT: WEB APP REDESIGN Project Overview: “WHAT” “WHY” “HOW” Prototype [design & development} iteration(s) Targeted Web User Contextual Usability Surveys Analytics Interviews Inquiry Testing TimeFriday, October 21, 2011
  • WHAT ELSE?Friday, October 21, 2011
  • NERDERY RESEARCH METHODS Usability Testing Field Study/Ethnography Surveys Site Search Analytics Card Sorting Web Analytics Stakeholder Interviews A/B Testing : Multivariate Testing User Interviews Mental Models Contextual Inquiry PersonasFriday, October 21, 2011
  • NERDERY RESEARCH METHODS “WHAT” Usability Testing Field Study/Ethnography Surveys Site Search Analytics Card Sorting Web Analytics Stakeholder Interviews A/B Testing : Multivariate Testing User Interviews Mental Models Contextual Inquiry PersonasFriday, October 21, 2011
  • NERDERY RESEARCH METHODS “WHY” Usability Testing Field Study/Ethnography Surveys Site Search Analytics Card Sorting Web Analytics Stakeholder Interviews A/B Testing : Multivariate Testing User Interviews Mental Models Contextual Inquiry PersonasFriday, October 21, 2011
  • NERDERY RESEARCH METHODS “HOW” Usability Testing Field Study/Ethnography Surveys Site Search Analytics Card Sorting Web Analytics Stakeholder Interviews A/B Testing : Multivariate Testing User Interviews Mental Models Contextual Inquiry PersonasFriday, October 21, 2011
  • QUESTIONS? Using the questions panels in the GoToMeeting app On Twitter @The_Nerdery Send us an email at primers@nerdery.com More answers online at http://nerdery.comFriday, October 21, 2011