Organising UX Research
•
0 likes•10 views
UX research culminates in data collection and analysis — the more organized it is, the easier it will be to make sense of this information. Debrief sessions where you can reflect on and discuss findings, insights, and observations with your research team or stakeholders
Recommended
More Related Content
Similar to Organising UX Research
Similar to Organising UX Research (20)
More from Chibueze Etoniru
Recently uploaded
Recently uploaded (20)
Organising UX Research
- 4. Be sure to take consistent notes Organise as you go When logging research data, make sure you use a consistent form of note-taking to avoid such confusion. You can ensure consistency by using a uniform rating scale, unit of measurement, formatting style, color codes, etc. Many novice UX researchers struggle with data, especially when it is collected and recorded haphazardly. When conducting UX research, do yourself a favor and organize your data as and when you collect it. This will make the analysis phase a lot easier and quicker for you.
- 5. Do a thematic analysis When you’re collecting data, make sure you tag them with relevant keywords or themes. This process, called thematic analysis, makes large volumes of data easily scannable and also reveals any patterns or trends that exist. For example, you can thematically tag positive and negative feedback from users. e.g #positive or #negative or #quotes Doing so can also help you search your data by keyword and view all categories and notes tagged under it, making it easier for you to locate specific data quickly and precisely. This even works better when your using a user research tool e.g Aurelius
- 8. Conducting debrief sessions Debrief sessions where you can reflect on and discuss findings, insights, and observations with your research team or stakeholders
- 9. Reasons for debrief sessions & when to debrief A debrief after a research session is the time to reflect on it with your team, encourage deep learning, and make complex connections. These sessions are usually held right after the tests, while observers' memories are still fresh. A debrief is a short meeting with your team or clients where you discuss and reflect on research that just took place. This can be as formal as a moderated activity or as informal as a conversation over a team dinner. Get the team to interact with each other and encourage collaboratio Immediately reflect on what happened during the sessio Help team members process and understand key information to continue to work on a projec Get the team a chance to offer their feedback on the study and suggest ideas for improvemen Separate research insights into immediately actionable vs. bigger issues
- 10. Best practices for debrief sessions Set expectations -Explaintheformatofthediscussionandwhatkindof contributionsyouexpectfromtheteam.Explainwhatyouarelookingforineach section.Giveclearinstructionsandsettimeexpectations Don’t make decisions -DebriefingisnotthetimetomakedecisionsonaUXissue. It'syourchancetodiscussallpossibleinterpretationsoftheresearchyoujust observedandexplorethepossibilitiesandideasyourteamcancomeupwith Take notes -youcanusenotestoreferbacktoideasorpossibleissues,orshare withteammembers/stakeholdersthatareabsent Set aside ideas or disagreements -Ratherhaveadocumenttosavenewor differetnideasthatdon’tfitthediscussionpoint Debriefing with test participants -Asktheparticipantiftheyhaveanyquestions youcananswer,thenbrieflydescribewhatyouareworkingonandwhy.Thiscan promptparticipantstosharenewinsightswithyou
- 12. Why analysing data is important? Youcan'tjusttakerawdataandapplyittoyourproduct. Useanalysisforsortingoutthewheatfromthechaff—i.e., definingwhatdataisrelevantandwhatisn't. Regardlessofthedatatypeyouanalyze,Youshouldkeepinmindyourproduct'stargetaudience. Themaingoalistogainvaluablefindings,sortthemout,analyzethem,and,finally,generate insightsthatcanbeappliedtothedevelopmentprocess. OneofthebiggestmistakesUXpractitionersmaymakeisjumpingtohastyconclusionsbased onraw,statisticaldataandactingwithoutproperconsideration. Dataanalysisallowsseeingthebiggerpicture,makingmoremeaningfuldecisions,andthus, savingmoneyandtime.Insteadoffixatingonrandomnumbersorusers'quotes,UX researchersshouldseekananswertowhyusersbehaveorthinkinacertainway. Forexample,ifyouruserresearchrevealsthat80%ofuserstendtoignoreyourSubscribe button,trytofindoutwhythishappens.Maybe,insteadofredesigningthebutton,youmight havetochangeitsplacementorreconsiderthebenefitsyouofferusersthroughyour subscription.
- 15. Contradictory results Sometimes, different research methods can produce inconsistent or contradictory results. For example, the task success rate among users could be 100%, but they could still report that they're not satisfied with the app and would switch to another if they found a better alternative. What can be done to prevent such conflicting findings? Start with checking the methodology Respondents: Have the same respondents participated in both studies? Different people can respond differently, which can lead to contradicting results Tasks: Have participants had the same amount of time for a task? Was the task the same for all participants Environment: Have users been performing a task in the same environment, or was there something that could have distracted them or influenced their responses Data analysis: Is the statistical significance high enough? Is there a chance that data was overcorrected? If you find that none of your research methods have inaccuracies, you might have to consider conducting another study. Contradictory results are common, so don’t be discouraged
- 16. Make recommendations The final step of analysis implies providing actual recommendations based on the key insights and supporting data. Including recommendations in your research report represents a valuable takeaway for stakeholders and motivates them to act immediately to solve users' problems. You may also share a document with the list of gained insights and have an open team discussion in person or remotely. Instead of providing off-the-shelf solutions, you can brainstorm together and turn your insights into "how might we" questions. For example, the insight that "users abandon their shopping carts because they don't see a total amount unless they click the Pay button" can be turned into a design opportunity — "How might we help users review the total price including delivery costs and fees before they click the Pay button?” Insights and recommendations help your team define what to focus on and can be potentially turned into design solutions.