Timeline for Confusion with Empathy Maps
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2022 at 19:10 | comment | added | Jivin Jawanda | It is always important to emphasize at the start that you are looking for their honest feedback. I usually say something like "please don’t worry that you’re going to hurt our feelings. We’re doing this to improve our product, so we need to hear your honest reactions." If one's feedback is overly positive and not saying anything constructive, then it might not be worth including that data. In a usability test, you can ask them to think out loud which gives you the best look into their internal dialogue. We are all subject to bias, so follow up questions can help clarify their actions. | |
| May 29, 2022 at 9:27 | comment | added | ThisisUX | This is a bit weird (I suppose because the fact that I am a newbie). It would make more sense if you are in a testing interview (so with your prototype for example) because the "thinking" or "does" thing is more an approach and it could be biased by your own interpretation and what the interviewe would think he/she has to say in order to "please" you or giving a "wrong" image, etc. Could this be the case where you have to think about another "approach" to empathize with your users? 🤔 | |
| S May 28, 2022 at 21:44 | review | First answers | |||
| May 29, 2022 at 16:05 | |||||
| S May 28, 2022 at 21:44 | history | answered | Jivin Jawanda | CC BY-SA 4.0 |