Decide what data goes into each dashboard based on who will use the dashboard and why they will use the dashboard.
https://aws.amazon.com/builders-library/building-dashboards-for-operational-visibility/
A very common tendency when designing dashboards is to overestimate or underestimate the domain knowledge of the target user.
It’s easy to build a dashboard that makes total sense to its creator.
However, this dashboard might not provide value to users.
We use the technique of working backwards from the customer (in this case, the dashboard users) to eliminate this risk.
Define KPI's - Key performance Index - need to be identified from dashboard user.
Before diving headfirst into dashboard design, sit with your end-users in order to gather requirements and define KPIs. Without doing that, you can design the most beautiful dashboard in the world, but it won’t change the way users make decisions in the long run.
Python note: Boto/Boto3 is the Amazon Web Services (AWS) SDK for Python.
It enables Python developers to create, configure, and manage AWS services,
4 Key factors about dashboard design
- Relationship: connection between two or more variables
- Comparison: compare two or more variables side by side
- Composition: breaking data into separate components
- Distribution: range and grouping of values within data
Data Pipeline -
No comments:
Post a Comment