menu

Product Design

Are you a product designer working in tech? This community is for you.

Channels
Team

User Interviews

August 28, 2017 at 2:12pm

Hey guys! I’m a product designer at Managed by Q and am trying to learn what is the best way to approach interviewing users as a designer. Our product team conducts at least 4 - 5 user interviews every week. We are using interviews to test future designs with InVision prototypes, validate new features, and obtain feedback about the product. I'm new to conducting and interviewing users, and I’m curious to know how other product teams approach user interviews. Some of the things I'd love to learn more about include:

  • Does your team conduct user interviews? If so how frequently and for what purpose?
  • What are some of the tools you use to conduct and document user feedback?
  • What are some of the design tools you use to present and test designs?
  • Who leads the interviews and what is your role (as a designer) in the interview?
  • What do you do to prepare for the interviews?

Also wondering what books, talks, or resources out there have been helpful.

Show previous messages

April 9, 2018 at 3:15pm

@claudio I think Michael Margolis has good and quick insights you could check to get you started:

https://library.gv.com/the-gv-research-sprint-start-recruiting-participants-day-1-8fa0bc1c8e71 from the Sprint book.

https://www.youtube.com/watch?v=U9ZG19XTbd4

like-fill
1
  • reply
  • like

April 15, 2018 at 3:18pm

Thank you @andreiafcosta, will check out the links! Michael is great—several weeks ago our teams had several calls with him for some feedback on our research process, and they were very helpful. Doing good research is hard!

like-fill
2
  • reply
  • like

June 11, 2018 at 10:28pm

my intel an my facebook page nots work I have tv an phone with u just my intel an my facebook page nots work yet

  • reply
  • like

June 12, 2018 at 4:31am

@claudio, my favorite method for remaining adaptable in a user interview is to write out an extensive script with a large number of questions divided into sections. Early questions are meant to sort out which sections are more applicable to the user I'm speaking to. For instance, I might have one section on purchasing, another on installation, then configuration, usage, maintenance/support, etc. That way the challenge is refining down to the most relevant questions for the user at hand, not making up new questions on the fly. Users' time is valuable, so being over-prepared is definitely better than being under-prepared.

like-fill
1
  • reply
  • like

June 25, 2018 at 5:49pm

Thanks for the info.

  • reply
  • like

July 10, 2018 at 4:38am

怎么给那些东西发东西

  • reply
  • like

February 9, 2019 at 10:54pm

Hello

  • reply
  • like

March 16, 2019 at 11:44pm