Design Research For Everyday Projects - UX London

  • Published on
    17-Aug-2014

  • View
    19.801

  • Download
    25

Embed Size (px)

DESCRIPTION

slides from my workshop on Design Research for Everyday Projects

Transcript

<ul><li> design research for everyday projects UX London 09 leisa reichelt disambiguity.com @leisa </li> <li> this is not really about user centred design </li> <li> to solve a problem you must first understand it - kim goodwin </li> <li> its about good design </li> <li> who is this workshop for? </li> <li> everyday projects? the design research projects you hear about most often are enormous, time consuming and expensive. most projects we work on cant bear that. research can/should be customised to suit the project requirements </li> <li> what well cover PART ONE: Designing Design Research PART TWO: Conducting Design Research PART THREE: Analysing Design Research LOTS of hands on exercises. Lots of your questions &amp; shared experiences Focus on QUALITATIVE Research (esp. interview format) Focus more on practical what you can actually do than best practice </li> <li> part 1: designing design research </li> <li> what is design research? activities that seek insight into user behaviour, goals and needs that might be supported by the design of products/services </li> <li> why do design research? we tend to project our own rationalisations and beliefs onto the actions and beliefs of others - don norman, the design of everyday things </li> <li> why do design research? design research helps you uncover, understand and design for real user needs </li> <li> real user needs = design for good usability but also = insight for inspiration/validation </li> <li> when to do design research? </li> <li> generative research prototype evaluative research </li> <li> design research toolkit Qualitative Stakeholder Interviews Co-design/Participatory Design Subject Matter Expert (SME) Interviews Group/Social Research Competitive Reviews Longitudinal Research - diary study Literature Reviews -twitter - flickr Depth Interviews (Customer&amp;User) Focus Groups Direct Observation (Ethnography) Quantitative Contextual Inquiry Surveys Usability Testing Remote Testing Tools Snap Interviews Stats/Analytics </li> <li> quantitative Vs qualitative </li> <li> mathematics and natural sciences Quantitative statistically sound, scientific large random samples questionnaires, surveys, tests Quantitative research is the systematic scientific investigation of quantitative properties and phenomena and their relationships. The objective of quantitative research is to develop and employ mathematical models, theories and/or hypotheses pertaining to natural phenomena. The process of measurement is central to quantitative research because it provides the fundamental connection between empirical observation and mathematical expression of quantitative relationships. http://en.wikipedia.org/wiki/Quantitative_research </li> <li> social sciences insight gathering, exploratory small sample sizes Qualitative participatory, observational, interviews, analysis of documents &amp; materials. Qualitative research ...aim(s) to gather an in-depth understanding of human behavior and the reasons that govern human behavior. Qualitative research relies on reasons behind various aspects of behavior. Simply put, it investigates the why and how of decision making, not just what, where, and when. http://en.wikipedia.org/wiki/Qualitative_research </li> <li> To design an easy-to-use interface, pay attention to what users do, not what they say. Self-reported claims are unreliable, as are user speculations about future behaviour. - jakob nielson </li> <li> choose qualitative for insight but ideally, combine quantitative and qualitative inputs quantitative can be great for problem identification &amp; solution validation </li> <li> how to choose? </li> <li> stock standard / garden variety plan 45-60 minute interviews 6-8 participants. but... </li> <li> understanding the problem: what are you trying to learn? - the problem is not always what it first appears to be - define your research questions - what might be the best ways to answer those questions? </li> <li> understanding the problem: what is the context for the problem? - care not to narrow the context early - are their multiple relevant contexts? - WHERE can we learn about the peoples behaviour in relation to this problem? - research as close to context as possible. </li> <li> remember: the power of artifacts - memory aid / detail - cross check for accuracy </li> <li> ...dont be afraid of getting a bit creative </li> <li> ...ethical research </li> <li> EXERCISE! Part 1 Your client is a grocery store. They want you to do some research and make recommendations about how they can provide a better online grocery shopping experience for their customers. You have unlimited time &amp; budget for your research. What research activities would you suggest? </li> <li> design research toolkit Qualitative Stakeholder Interviews Co-design/Participatory Design Subject Matter Expert (SME) Interviews Group/Social Research Competitive Reviews Longitudinal Research - diary study Literature Reviews -twitter - flickr Depth Interviews (Customer&amp;User) Focus Groups Direct Observation (Ethnography) Quantitative Contextual Inquiry Surveys Usability Testing Remote Testing Tools Snap Interviews Stats/Analytics </li> <li> squeeze to fit START: design the research project youd love to do if time/money/resources were no barrier THEN: work out what is achievable. Be creative! </li> <li> ways to squeeze - fewer participants - fewer activities - shorter sessions - less proximate to context (use artifacts) - use technology (phone, web video, twitter) - less complex research activities - more readily accessible participants Even the smallest amount of data beats none. (yes, Im quoting Jakob again - Guesses vs Data as the basis for Design Recommendations) </li> <li> lets take a break! </li> <li> part 2: conducting design research </li> <li> recruitment </li> <li> who to recruit? persona hypotheses Think about: - the different user roles - factors most likely to affect behaviour Dont over complicate it! </li> <li> how many? as few as possible. if given the choice to more research studies with few participants. why? - diminishing returns - speed to action (design) </li> <li> (yes, Im quoting Jakob again - Why you only need to test with 5 users) In earlier research, Tom Landauer and I [Jakob Nielsen] showed that the number of usability problems found in a usability test with n users is: N(1-(1-L)n) where N is the total number of usability problems in the design and L is the proportion of usability problems discovered while testing a single user. The typical value of L is 31%, averaged across a large number of projects we studied. Plotting the curve for L=31% gives the following result: </li> <li> The most striking truth of the curve is that zero users give zero insights. http://www.useit.com/alertbox/20000319.html </li> <li> how to find them? DIY vs Using Professionals - how much time/money do you have? - how easily accessible are participants? is using friends/family network really bad? </li> <li> Incentives. Pay them. </li> <li> CAUTION: researching young people &amp; kiddies </li> <li> logistics - where to research - timing your research - factoring in no shows (&amp; floaters) - consent forms (privacy, their rights &amp; incentive acknowledgement) </li> <li> discussion guides -writing a discussion guide </li> <li> discussion guide &gt; define your research questions &gt; start as wide as possible, narrow slowly &gt; keep it contextual, not speculative &gt; show, dont tell (observation = good) (show me how you do that?) &gt; uncover mental models (if you clicked there, what do you think would happen?) &gt; ask OPEN questions (ask questions to get them talking NOT yes/no answers) &gt; take care not to lead (you can have leading questions AND leading structures) &gt; dont outsource design to your participant! (remember, youre the designer!) </li> <li> EXERCISE! Part 2a write a discussion guide for a depth interview for your grocery store client (who wants to design a better online grocery shopping experience) </li> <li> interview technique getting the most from your research participants (quite possibly the most important part!) </li> <li> capturing data </li> <li> what to capture on sticky notes &gt; *anything* interesting/relevant said in the course of your interview, in as close to direct quotes as possible. &gt; your design ideas &gt; questions for the future &gt; capturing on the fly is a *real* skill. I still live transcribe to a text file then extract affinity notes from the transcription. </li> <li> interview technique introductions &amp; getting started - introduce yourself (and any colleagues) - what are we doing here? - what time will we finish - forms &amp; incentives - ask permission to record </li> <li> interview technique its not a test! - allay their nerves - distance yourself from the design - we only care about *their* opinion, not people they know or most people - theres no right answer or smart answer - their opinion counts - will really help shape the design of the product/service </li> <li> interview technique building rapport *everyone* has something that makes them either very interesting or passionate. find it. talk about it. the investment in building rapport is repaid by the quality/quantity of insight given. </li> <li> interview technique - Active Listening - nodding, smiling &amp; paraphrasing - Focus - dont let yourself get distracted - Look for physical clues - additional information, and do they match the words? - Dont Rush - take time to get your thoughts together &amp; prepare your next question - Keep it open - Who, What Where, When, Why, How and my favourite Tell me about... - Follow the flow - dont stick to your script, mix up the order if it flows better for that participant. </li> <li> interview technique Have a great closing question. Some of my favourites are: - Do you know someone you might recommend this to? Who/Why - How would you rate it out of 10 - What would you tell the designers Try to summarise the parting sentiment (notes that it is not more or less important than the initial sentiment) </li> <li> interview technique say thank you. always remember the participant is HELPING YOU. be appreciative. </li> <li> if youre feeling nervous, remember... research participants are like dang...</li></ul>