Discuss Secure approach to dashboards strategy and frameworks
Background:
Today we 2 security dashboards and are planning to add a third one soon (and a fourth!). For the most part, the dashboards present the same information to the user with slight variations based on where the dashboard is located (project, group, instance). We also don't define the use and use cases for each dashboard, relegating them to a catch-all for project security features and workflows. This current approach is slowly leading to overloading of our dashboards and could be confusing users as to the tasks they need to complete from these views.
Problem:
- Lack of prescribed workflow has led us to design dashboards that act as a catch-all for our security features.
- How might we leverage one security dashboard for users to use while providing the appropriate information to users in specific areas of the application?
- Lack of dashboard framework makes it difficult for multiple designers to contribute to the experience.
- How might we create and maintain a dashboard framework so that contributing to the experience is easier and doesn't cause regressions or rework?
Process:
- Collaborate on a comprehensive dashboard strategy
- Create: Journey maps, flows, JTBD, and diagrams as needed
- Refine: Strategy and artifacts used
- Document: Strategy in Secure UX Handbook
- Communicate: Strategy to Stage and Org.
- Collaborate on dashboard framework
- Work with @sbouchard1 on the unified dashboard initiative
- Create: Concepts for the security dashboard based on collaboration direction
- Refine: Concepts and mocks as required
- Document: Framework rules and guidelines as required
- Deliver: MVCs from refined mocks
- Communicate: Framework to Stage and Org.
Edited by Mark Florian