The goal of this page is to create, share and iterate on the Jobs to be Done (JTBD) and their corresponding job statements for the Monitor stage. Our goal is to utilize the JTBD framework to better understand our buyers' and users' needs.
Utilize JTBD and job statements to:
During an active incident, I want to reduce the time to resolution, so I can get the things back up and running as quickly as possible.
|During an active incident, I want to have quick access to communications channels, so that I can communicate with other incident responders or stakeholders.||Issue|
|During an active incident, I want to be able to collaborate with my teammate, so that we can work together to resolve the incident.||Issue|
|During an active incident, I want to publicize important updates, so that stakeholders can stay informed.||Issue|
|During an active incident, I want to see all the relevant data, so that I have the information that might help me quickly resolve the incident.||Issue|
|During an active incident, I want to automatically apply fixes to known problems, so that I don't have to manually fix things.||Issue|
When an alert is triggered, I want to be able to triage it quickly, so I can decide if it's worth investigating further or not.
|After deciding an alert is worth further investigation, I want to be able to easily escalate the alert to an incident, so I can collaborate with my team on its quick resolution.||Issue|
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.
|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.||Issue|