One of our challenges as dashboard developers is effectively presenting all the necessary information to decision-makers while working within the constraints of limited 'real estate' on the dashboard. To tackle this challenge, I've compiled a list of 5 tips that will help you complete the task without the need for excessive buttons or constant screen switching.
Tip 1 – Focus
Ensure accurate characterization of metrics on the dashboard. Indicators included in the dashboard are vital for decision-making. To provide meaningful insights, metrics must be contextualized by comparison—whether that's over time, among categories, in terms of dominance, or others. Without such comparisons, a standalone number lacks relevance.
"For example, we have '32 pizza flavors' displayed on the sales dashboard. This metric is placed prominently on a large card, by itself. It's clear that this number shouldn't be there because it doesn't provide actionable insights or contribute to process improvement in any way.
Tip 2 – Choose the right graphs.
Avoid using graphs that consume significant space while offering minimal information. In most cases, you'll encounter area graphs like pie charts, maps, Gauges, donuts, and more.
For example, the treemap and the bar chart in the bottom pictures depict the same comparison scenario: ranking the number of people killed by police according to their race. However, the bar chart occupies significantly less space.
Tip 3 – Avoid Duplicating Information.
For example, the graph in the bottom picture conveys the exact same data as the text that was added to it. A graph with an accurate design and effective title can present the information in a way that doesn't require additional text explanation.
Tip 4 – Use tooltips.
Information that is not directly relevant to the overall context but provides essential details for a specific element should be included in the tooltip. This information serves as an additional layer of detail and is intended to address any 'additional questions that may arise.
Examples:
Tip 5 – Keep It Concise
Any text or number that can be made more concise without losing meaning should be shortened. This includes lengthy names, which can be abbreviated without sacrificing clarity. Long numbers should be reduced to 4 digits, and unit symbols should be converted into headers, and so on.
**Most of the examples that are in the article were taken from the gallery of Power bi community.