Create a job map for error tracking
In #216479 (closed), the Monitor:Health group started the process of consolidating previous research, identifying existing JTBD and defining next steps for the JTBD in each category.
For error tracking, we've already a lot of research:
- Error Tracking Problem Validation
- Error Tracking Opportunity Canvas
- Error Tracking User Interview notes
- Error Tracking UXR Insights
- Error Tracking User Interview Affinity Map
- Error Tracking User Journey
- Validate Error Tracking Maturity Level with Users
From these interviews, we've identified a primary and secondary JTBD:
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.
Next steps for this category
This issue will be for creating the job map for error tracking. When all four categories have been mapped, we can conduct the validation survey as part of ux-research#859 (closed)