Solution validation for incident timelines
What's this issue all about? (Background and context)
We've come up with initial designs for building out incident timelines. Is what we've come up with usable and appropriate for people triaging incidents?
What hypotheses and/or assumptions do you have?
Guessing that the ability to add a comment to a timeline is a bit too hidden currently.
What questions are you trying to answer?
- Does it make sense to have the timeline in a separate tab?
- Which activity feed items do people want to see in there? If it's a choice between all or none, which would people choose?
- How important is the slash command method of adding a comment to the timeline?
- Can people find the hover edit options on the timeline?
- Does that method work for editing?
- Is there any important functionality missing?
- Which timezone would people prefer to see their timelines in? Does that need to be customizable?
What research methodology do you intend to use?
Live usability test with at least 5 participants. Have sufficient volunteers from GitLab's SRE team so will focus on them, since they will also be dogfooding the feature.
What persona, persona segment, or customer type experiences the problem most acutely?
Devon, DevOps Engineer Sidney, System Admin
What business decisions will be made based on this information?
If/how to proceed with implementation of incident timelines
What, if any, relevant prior research already exists?
Who will be leading the research?
Amelia
What timescales do you have in mind for the research?
Trying to get the bulk of it done in 14.1
Relevant links (problem validation issue, design issue, script, prototype, notes, etc.)
Edited by Amelia Bauerly