UX Tea Break: Testing assumptions in user research
Vložit
- čas přidán 23. 01. 2020
- Subscribe to my channel: bit.ly/2NBKaOe
I answer the question, "Could you give a more detailed explanation of “assumptions” in user research and how to identify them?"
Have a UX-related question you want me to answer? Post it in the comments.
- My Udemy class: uxtraining.net/index-udemy.html
- My book, 'Think Like a UX Researcher': uxresearchbook.com
_______________________________________________________________________________________________
I can come to you and train your team in UX:
- BCS Foundation Certificate in User Experience bit.ly/2XQTaTA
- Introduction to User Experience bit.ly/2NAeHMd
- User Research Fundamentals bit.ly/2LBfh9Q
- Design ethnography: Take control of customer visits and interviews bit.ly/2RYfqFy
- Usability testing: Take control of testing your product with users bit.ly/30el89e
- How to design and implement web surveys bit.ly/2YBEQeF
- Improving your impact as a user researcher bit.ly/2XQU5U2
Contact me about UX training: bit.ly/2XqtXjk
_______________________________________________________________________________________________
Let's connect:
- Twitter: / userfocus
- Facebook: / userfocus
- LinkedIn: / davidtravis
--
Spanish captions provided by the LabX of Sperientia [studio+lab]® (México)
A story of your assumption tests being used in everyday life:
In reviewing and revising one of my many how-to guides in my playbook, this one being based around the lessons in your video here along with other articles, I was yet again deciding how to watermark my guides so that if shared, people will know that I was the one who put in the work to compile and write-up the digested lessons, takeaways, and connecting/expanding thoughts. However, I had concerns over how I credited myself for writing up this guide because depending on how I phrased it, people could potentially see it as plagarising or taking credit for others' ideas and that's definitely not something I want to be seen as.
It _finally_ dawned on me that this was actually your assumption test in action - I originally assumed that how I credited myself for the work was probably clear enough, but the counter-assumption would be that the readers didn't understand my work vs the owners of the source material so they saw it as stealing (assumption test 1). And, if I realised that's how they perceived it after I shared the document, then yes, I would have wanted to credit myself differently (assumption test 2). So, in using these tests, I eventually arrived at a solution that passes both.
Great example Geoff.
I have found this video very useful. Thank you for sharing your knowledge. Subscribed!
Thanks for your comment Tomi, glad its useful.
Thanks for the shout out David! Great video :)
Good insights... thanks.
Glad it was helpful.
I am confused, how should I make assumptions & hypotheses, given that I have already selected a feature, that I will be working on.
As per my understanding, i will be working on, solution backward or It's like reverse engineering the problem.
How do these things go hand in hand?
I don't know, if I am able to put my thoughts clearly!
I found the framework for organizing assumptions very useful. How do you go about ASKING about assumptions? Are there any prompts or ways of asking that you found particularly useful?
Run a workshop and ask the product team to create assumption personas. This is a good way to identify the team members' beliefs.
"Hello, I'm writing to you from Peru. I really liked your video. Could you give me some advice on how to create a deliverable to present the results on assumptions?"
There's nothing unique about presenting the results on assumptions, compared (say) to presenting the results of field research or a usability test. Just follow best practice: show only the key findings, present face-to-face, build in time for discussion. Save a more detailed report / slide deck to the shared drive.
the sound is not good I am quite disappointed
I just checked and the sound is fine when I play the video. I'm not sure what the problem is.