DSS
Why
Why do we need to reimagine DSS?
We have different types of users using DSS for different purposes. Redesigning the DSS capabilities to allow everyday users and power users to find and use the data easily
Why do we need a UX upgrade?
Any specific feedback on the current version?
What
Identify the User
Since DSS is used by different types of people, we want to nail down the Primary User (uses the service every day) and Power User(uses the service less frequently but is expected to use data in decision making) for our product. There could be a range of personas too. The goal is to have clarity on who we are designing for and what their needs are.
Deliverable: User Personas
Participants: PRK, Omkar, Antriksh,
Product-wise Metric Pool (Internal Data Mart)
The product metric is a two-fold item
Internal Data Mart - We (product team) need some key metrics to be able to make better decisions while designing our products and measure the success of our initiatives
Transactional and Behavioral Data
DSS - State needs some key metrics to understand the performance, finances, etc
→ DSS will be a subset of Internal Data Mart
However, we (internally) do not have data readily accessible to us. We want to have an available data mart for us internally so that we can play around and fetch the data we need
Deliverable:
Limiting the scope by product
Clear Data Points for all Products (and why we need them)
Internal Data Mart (Data Tables)
Need to check with the Implementation Team (can do a scheduled snapshot of production and put it in our environment)
Participants: Product team, Engineering
Product Design Skeleton
#todo
Deliverable: Wireframes for DSS dashboard and components in the dashboard
Participants: Product, Design
Visualization
#todo
Open Dashboards
#todo
Work Items
Feature | Description | Success Metric | Notes |
|---|---|---|---|