12 June 2021 (pre-meeting notes)

• Not a meeting

Technical Requirements

• Firmware gave me a file with all the telemetry outputs :P

  • Single source of truth for everything that telemetry is measuring – super nice lol

• I’ll be revising the technical requirements doc based on that file by Monday’s meeting

Interview Overview!

• Goal is to get these done over this month, try to end by July 10 at the latest

I have a list of 5.5 people to interview – I’ll reach out to them over the next two weeks to arrange 1 hour interviews depending on how the interview guides are going, and how prepared we are.

MSXIV (current): these are all leads

• Hardware – James Lin

• Firmware – Ryan Dancy, Mitchell Osler

• Strategy – Emma Wai

MSXII (past)

• Aaron Tan

• Taiping (may not be reachable…hence 0.5)

Who’s using telemetry?

• Even though we’re only interviewing leads, EVERYONE on hardware, firmware, and strategy are expected to be able to use the telemetry dashboard

• The leads will know the use cases the best, and will be the people onboarding members to teach them how to deal with telemetry

• Ideally you’d want to interview “regular” team members, but a) we don’t have names b) none of them will know much.

How will the actual interviews work?

• One person acts as the “main interviewer” – they will be asking most of the questions and directing the interview

• The rest of the people listen in on the interview (cameras off) and act as notetakers

  • They are also expected to step in with any questions that they have, and help prompt the interviewer if they’re having trouble

• It would be Very Cool if y’all were able to act as the “main interviewer” at least once

  • really good experience and helps differentiate you as a UX applicant, since most people never get the chance to do research with actual users

  • HOWEVER, the interview guide must be well prepared/fully fleshed out (or I won’t let you do it :P)

Interview Guides

• I will screenshare one of the interview guides I created for co-op during Monday’s meeting (June 14).

A really structured way to create interview guides: https://www.nngroup.com/articles/interview-guide/

Example interview guide: https://media.nngroup.com/media/editor/2021/02/05/example_interview_guide.pdf

• Notice that the sample has 5 main research questions/themes. These are your guiding questions that you are seeking to answer. They are BIG and ambiguous.

• This weekend (June 12/13), try to come up with 5 big questions EACH that you want answered

  • 5*4 = 20 questions total

  • 10 for MSXIV dash (Rishii and Joy), 10 for MSXII dash (Cheryl and Catherine)

  • As a team, we will discuss what questions we want to prioritize (ie if all of us came up with the same question, we likely want to include that question)

• Next week, flesh out the sub-questions for the big questions/themes we agree on

  • I will try to provide guidance on this if needed, or prompts to help you brainstorm

  • I will also be re-splitting up the interview guides, because I feel that we may need different ones for each subteam using telemetry – let’s discuss Monday

If you want a more comprehensive guide on user research in general (not just interview guides) go through the articles here https://uxrfieldguide.com/

• Very good introduction on how to conduct user research well

• Good overview of biases to avoid

...

7 June 2021

• Go over Technical Requirements doc with Avery

• Begin user recruitment – get names from Avery, start reaching out to people

• Catherine Burns pick one of the tasks below, and slack me if you have any questions!

...

...