Q1 OKR: Validate Error Tracking Maturity Level with Users
What’s this issue all about?
As part of gitlab-com/www-gitlab-com#6201 (closed), we are meant to validate Error Tracking's move from minimal to viable with five users.
Who is the target user of the feature?
What questions are you trying to answer?
From gitlab-design#854 (closed) - since Error Tracking has moved from minimal to viable, we should verify if it fits the following criteria with users:
- Definition: Can be used by users/customers to solve a real JTBD. It does not have major (blocking) usability issues but may have minor usability issues.
- How it's scored: Receives a "C" or higher for primary and secondary JTBDs.
We've defined the JTBD for this effort as follows:
Primary JTBD:
When I'm proactively reviewing the list of errors thrown by my code, I want to be able to escalate investigation of the most serious errors, so I can make sure they are addressed before they impact customers.
Secondary JTBD:
When I'm proactively reviewing the list of errors thrown by my code, I want clean up the list of errors, so that I'm only seeing the errors that are important to me.
The assumption is that we'll be testing the primary JTBD as part of this research effort.
What hypotheses and/or assumptions do you have?
What decisions will you make based on the research findings?
Whether or not error tracking's move from minimal to viable is supported by users.
What's the latest milestone that the research will still be useful to you?
Due by end of Q1: April 30th, 2020
Sample test project for users to interact with