Investigate - Job-to-be-done differences between Operations and Environments Dashboard
I'm not sure where this will end up so let's use this specific issue to discuss that. I have the sense that there is a bunch of user job-to-be-done overlap between the Operations and Environments Dashboard.
Overview
The operations dashboard docs state:
The Operations Dashboard provides a summary of each project’s operational health, including pipeline and alert status.
The environments dashboard docs state:
The Environments Dashboard provides a cross-project environment-based view that lets you see the big picture of what is going on in each environment. From a single location, you can track the progress as changes flow from development to staging, and then to production (or through any series of custom environment flows you can set up). With an at-a-glance view of multiple projects, you can instantly see which pipelines are green and which are red allowing you to diagnose if there is a block at a particular point, or if there’s a more systemic problem you need to investigate.
We should validate the following (either quickly amongst ourselves based on our intent or via research with users based on their behavior):
- For users tasked with performing operations (management of the app in production) do they want an environment based view?
- For users tasked with performing CI/CD oversight (management of CI/CD pipeline health) do they want a view of alerts?
- Are these two jobs to be done the primary ones we should be supporting?
- Are there significant overlaps between the two jobs to be done?
Related Docs
- Opportunity Canvas, WIP: https://docs.google.com/document/d/1USulCKWEqK53Lx_Soe6GZsOO-MBimATG6R6D9d1q1DY/edit?usp=sharing