Update Responder Outreach page with new issue label (005429b8) · Commits · GitLab.com / Content Sites / handbook

content/handbook/product/ux/performance-indicators/system-usability-scale/sus-outreach.md

+1 −1

Original line number	Diff line number	Diff line
		@@ -58,4 +58,4 @@ Every quarter, we include a question in the SUS survey that asks whether respond
		1. If multiple GitLab team members are on the call, it can be beneficial to debrief immediately afterwards.
		1. Collect all notes that were taken and the upload the Zoom recording (if applicable) to our [SUS Follow-up Project in Dovetail](https://gitlab.dovetailapp.com/projects/36nmGVKvkaT7SGMXtUeHVg/v/70xPTo5RzTRZnCNEVz1fWH).
		1. 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.
		1. Add the label 'SUS::Impacting' to any epics/issues that result from or align with feedback from the SUS outreach calls.
		1. Add the label 'SUS::Responder Outreach' to any epics/issues that result from or align with feedback from the SUS outreach calls.