Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Bringing the team along for the ride: Lessons from including whole teams in user research

UXAustralia
March 15, 2019

Bringing the team along for the ride: Lessons from including whole teams in user research

UXAustralia

March 15, 2019
Tweet

More Decks by UXAustralia

Other Decks in Design

Transcript

  1. bringing the team along for the ride @nicolarushton art by

    Take Lizjenga https://dribbble.com/shots/2644716-Bike-Party aka using collaborative research to enable a user-centred team
  2. The team around me aren’t really user-centred. they don't feel

    empathy for the users. I can't get my team to really get my research, no matter how creatively I present it. My client/team/boss doesn't understand why research is valuable. I have to push not to skip it. I’m not 100% sure everyone else actually cares about the problem we’re solving. I feel kinda lonely at work… @nicolarushton
  3. aka using collaborative research to enable a teams’ user-thinking-ness bringing

    the team along for the ride @nicolarushton especially engineers!
  4. a process to making user research uber-collaborative 1. Setting learning

    goals as a team 2. Having team members be note-takers in user interviews " 3. Synthesising insights as a team 4. Doing research regularly @nicolarushton
  5. low barrier to entry low time commitment from team members

    max impact on team members ŧ ŧ ŧ @nicolarushton (less than 4 hours a week)
  6. if we’re wrong that our users could feel safe staying

    in a stranger’s spare room, this idea will fail. If we’re wrong that mobile users usually search for a place to stay by location first, this feature design will fail. very high level granular, feature-level @nicolarushton 1. Setting learning goals as a team
  7. very likely to kill the idea if wrong less likely

    to kill the idea if wrong very unsure if we’re right about it pretty sure we’re right about it ☠ 1 2 @nicolarushton 1. Setting learning goals as a team
  8. If we’re wrong that 
 our mobile users usually search

    for a place to stay by location first 
 this feature design will fail. rephrased as a question might become… how do our mobile users search for a place to stay? 2 @nicolarushton 1. Setting learning goals as a team
  9. focus and clarity…. and also buy-in everyone’s voices have been

    heard cliffhanger @nicolarushton 1. Setting learning goals as a team
  10. framing: require it. a little education one person at a

    time, minimising team time spent away from other work @nicolarushton 2. Having team members be note-takers in user interviews "
  11. one note taker only, in the room with you they

    type into a google doc they type verbatim, as much of what the participant says as possible you write the notes onto post-its later for synthesis i care a lot about note taking @nicolarushton 2. Having team members be note-takers in user interviews "
  12. video dial-ins are boring they have a job to do,

    so they’re very engaged being in the room listening to a participant is so empathy-building no extra work for researcher @nicolarushton 2. Having team members be note-takers in user interviews "
  13. what if people are coming up with totally incorrect insights

    though? @nicolarushton 3. Synthesising insights as a team
  14. 4. Doing research regularly free to make mistakes = free

    to experiment @nicolarushton not falling in love with one user’s problems
  15. immaculate research that doesn’t change how the team thinks lo-fi

    research that makes the team way more user- centred which results in a better product shipping? @nicolarushton 4. Doing research regularly
  16. the user experience is better when everyone in the team

    thinks about users art by Justin Tran
 https://dribbble.com/shots/5405532-How-do-you-design-an-effective-growth-team