• I do like the literal "carrot" suggestion haha • Giving tasks/responsibilities to those joining in definitely helps and if you immediately debrief your findings after each research session, they've already invested time so they'll be more likely to stick around to talk about what they learned • the above was all just confirming what you said haha, but one aspect I think that could have been dialed up more in this video is in selling how _their_ problems will be solved by them being involved in the research. Maybe to devs and designers it's telling them how they'll be less rework they might have to do, and maybe that's enough of a carrot for them to want to jump in. For execs, maybe it's buttering them up by suggesting they're so smart, if they come to these I'm sure they'll discover new ways to increase revenue or decrease costs
Hello David, Thank you this interesting content and advice. How would you manage or weight ux researcher findings to other team members findings. How would you treat the different post-it colored notes ? Thank you
Most of the time I find that the non-UX researcher "findings" are really design ideas and not observations. Those I'll discard. But if it's a true observation (something seen or heard during the session) then I'll treat it at the same level as my own observations.
What does a researcher do after the research and analysis are done and the visual designer(s) starts working on the design, what can a UX researcher do meanwhile? I'm currently working as a UX researcher for a company and I'm in this situation.
The way you're describing your role makes it sound like a waterfall process. If you using Scrum then you should be doing user research in every sprint. Think of it as "rounds" of research rather than doing all of your research up front.
• I do like the literal "carrot" suggestion haha
• Giving tasks/responsibilities to those joining in definitely helps and if you immediately debrief your findings after each research session, they've already invested time so they'll be more likely to stick around to talk about what they learned
• the above was all just confirming what you said haha, but one aspect I think that could have been dialed up more in this video is in selling how _their_ problems will be solved by them being involved in the research. Maybe to devs and designers it's telling them how they'll be less rework they might have to do, and maybe that's enough of a carrot for them to want to jump in. For execs, maybe it's buttering them up by suggesting they're so smart, if they come to these I'm sure they'll discover new ways to increase revenue or decrease costs
Good point Geoff. I was taking that for granted.
Hello David, Thank you this interesting content and advice. How would you manage or weight ux researcher findings to other team members findings. How would you treat the different post-it colored notes ? Thank you
Most of the time I find that the non-UX researcher "findings" are really design ideas and not observations. Those I'll discard. But if it's a true observation (something seen or heard during the session) then I'll treat it at the same level as my own observations.
I really think it's unacceptable for engineers to ignore the product and its users. Otherwise, what's the point?
Totally agree Aaron.
What does a researcher do after the research and analysis are done and the visual designer(s) starts working on the design, what can a UX researcher do meanwhile? I'm currently working as a UX researcher for a company and I'm in this situation.
The way you're describing your role makes it sound like a waterfall process. If you using Scrum then you should be doing user research in every sprint. Think of it as "rounds" of research rather than doing all of your research up front.
@@DavidTravis Thank you for the reply David.