User interview analysis | participant 2

[nasimbiglari]

Overview

As a team we have decided that we want to alternate responsibilities in the interview procedure so everyone on the team would get a chance to get hands on experience on all aspects of interview process. An interview was conducted by two members of the research team, the researchers who were not involved with the interview process are tasked to listen, analyze and share findings with team.

Action Items

• [x] Listen to the interview.
• [x] In preparation of the affinity mapping exercise, generate sticky notes with the themes, ideas, and understandings that you have derived from the interview in Figjam.
• [x] Finish organizing the sticky notes with the team.
• [x] After the sticky notes organization, funnel the insights into the following elements in order to better prepare for the insight reports: user pain points, user needs, organizational needs (if applicable), themes, key insights, and if applicable other themes that are of research interest for a later point time.
• [x] Put together the insights in your box in Interview figjam.
• [x] Inform the leads

Generate sticky notes guidelines

Please, read the following guidelines for the sticky note generation exercise. In this way, we increase our understanding during the sorting.

• [ ] Put -Q- on the sticky note if you write down a direct quote from the interview including the regarding time stamp through the following format: -min: 2.28-.
• [ ] If you have a larger code and you want to leave out a part or certain words, please indicate that you have done so by replacing that piece of text with the following -[...]-. In that way, we at least know that there is a piece of information missing from the regarding quote.
• [ ] Put -I- if you write down an insight that you derived from the interview.

Resources/Instructions

Interview uploads Interview Figjam Nielsen Norman Group article on Affinity mapping

[JeannyRen]

Hey @navarroliuanthony, once you feel better: Please provide an update:

1. Progress: “What is the current status of this ticket? What have you completed and what is left to do?”
2. Blockers: “Difficulties or errors encountered.”
3. Availability: “How much time will you have this week to work on this issue?”
4. ETA: “When do you expect this issue to be completed?”

If you need help, be sure to either: 1) ask for help at your next meeting, 2) put a “Status: Help Wanted” label on your issue or 3) put up a request for assistance on the #design-systems slack channel.

[kelenelee]

will be adding this to my backlog according to slack message from @allthatyazz . glancing at the figma file, it looks like it's just step 3 left that needs to be completed, however, step 2 isn't giving me quite enough data to complete step 3. I would have to watch the video myself.

About the interviews, I would like to see the interview analysis moving forward with the priority of working on PMs interviews first. We have PM 2, 5, 7 and 9. Some work has been done with PM#2 and PM#5, so it makes sense to try to complete those first. @navarroliuanthony could you please check the work on PM#2 to confirm the stage of the analysis? It seems that only step 3 has remained. @kelenelee you have done a great job with sorting the PM#5 notes- do you think you can pull off step 3 for that participant by yourself so Eric can focus his time on the usability research plan?