Secure & Defend: Consider One security dashboard
Problem Statement
Soon we will have 3 dashboards for Security teams to use. Since the beginning, we've taken a bottom-up approach to security dashboards starting with the project level and moving to the instance. This approach worked for a short time but now we are seeing the adverse side effects of managing and designing for 3 different dashboards. For our users, we are creating broken experiences and are not addressing their needs based on which dashboard they are on.
For reference; the analytics dashboard takes a drill-down (top-down) approach to information.
For the user
How might we approach security dashboards from the top down?
How might we create an experience that allows for easy access to all security information by everyone who is accountable and responsible for this work in their GitLab instance?
For us
How might we reduce tech and design debt for dashboard work?
How might we reduce experience inconsistencies and design debt?
Reach
Security teams, analysts, engineers, managers, directors
Engineering teams, analysts, engineers, managers, directors
Product teams, managers, directors
10.0 = Impacts the vast majority (~80% or greater) of our users, prospects, or customers.