Gitlab hero border pattern left svg Gitlab hero border pattern right svg

System Usability Scale responder outreach

  1. You are here:
  2. Handbook
  3. Product Handbook
  4. UX Department
  5. UX Department Performance Indicators
  6. System Usability Scale
  7. System Usability Scale responder outreach

Every quarter, we include a question in the SUS survey that asks whether respondents would be interested in discussing their responses with a GitLab team member. This is a great opportunity for Product Designers and Product Managers to learn more about the usability challenges for their specific product area.

Overall process

  1. The UX Researcher running the SUS survey shares a Google sheet that contains scores and verbatims from respondents who have agreed to a follow-up conversation.
  2. The UX Researcher creates an outreach issue to manage the responder outreach.
  3. First, Product Leaders go through the Google sheet and sign up for outreach and/or tag in their Product Managers.
  4. Product Managers review the sheet and confirm who they want to speak to. If a Design counterpart exists, tag them Product Design counterparts to decide who will be leading the interview. Otherwise the PM will lead it. The interview leader will be responsible for reaching out to the user and scheduling the interview. Once contacted, they mark the respondent as 'Contacted' in the sheet.
  5. If multiple GitLab team members are interested in speaking to the same respondent, coordinate with the team member that contacted the respondent to align on questions to be asked. We do not want the same respondent be contacted multiple times and by multiple GitLab team members.
  6. After the interview, mark the respondent as 'Complete' in the sheet.
  7. Add any notes and links to video recordings to the UX Research shared Google Drive.

Process for reaching out to respondents

  1. Calendly is the best method for scheduling calls with respondents. Set up your free Calendly account if you haven't done so. Add details to the invite description describing yourself and the conversation purpose. Also add your personal Zoom link, either via connecting your Zoom account or pasting in your personal Zoom URL.
  2. You'll need to add an extra question to the invite form in order to ask for permission to record (example below). See example of a Calendly invite you can use as a reference.
  3. Draft an email that you'll send to respondents. Example copy is below.
  4. BE ON TIME TO YOUR CALL. Make sure everyone on the call introduces themselves.
  5. If respondents have agreed to recording, still ask them once again if it's OK if you record before turning it on.
  6. See our training materials on facilitating user interviews

Example email copy:

Hello, My name is X and I'm the Product Designer for X at GitLab. Thank you for giving us the opportunity to follow up on your response to our recent survey.

I would be very interested in speaking further about some of the points you raised in your survey response. Would you be willing to do a 30-minute video conference call to give us some more detailed feedback on your experience using GitLab? You'd be able to schedule the call at a time convenient to you.

Schedule a time for the call using this link: https://calendly.com/yourname/30min

Thank you for your feedback and let me know if you have any questions.

Best, Your name

Copy for the permission to record question in Calendly invite:

We would like to record (1) the conversation you have with our team member and (2) anything you choose to share on your screen with us during the call. We would like to share the recording of the call with other GitLab team members. The recording is stored securely and would never be shared with anyone outside of the GitLab team. Please indicate below whether you give your permission for us to record the conversation and share with our team.

I agree, I give my permission for my voice and screen to be recorded.

I disagree, I do not want my voice or screen to be recorded.

After the call

  1. If multiple GitLab team members are on the call, it can be beneficial to debrief immediately afterwards.
  2. Collect all notes that were taken and the link to the Zoom recording (if applicable) and add them to our SUS Follow-ups folder in the UX Research team Google Drive.
  3. If you told the user you'd follow up on anything or promised to send them further information, make sure you do so, ideally within two business days.
  4. Add the label 'SUS::Impacting' to any epics/issues that result from or align with feedback from the SUS outreach calls.
Edit this page View source