We’ve made a list of the most common dashboard pitfalls BI developers use so that you can avoid the same errors!
1. Overly involved dashboard
- Do not make the dashboard overly complicated.
- A single dashboard does not have to answer all the questions the business user might ever want to know of the data.
- While the idea of a single dashboard might be attractive in principle, the effort the business user might have to put into understanding how to use it can make it unwieldy. It may, therefore, make more sense to give a series of more structured dashboards broken out by subject area.
2. Too many or too large visualizations on a single dashboard
- Keep the dashboard limited to 3-4 main charts, so the business user is not scrolling to view components.
3. Unclear language or unnecessary abbreviations
- Natural language should be used as much as possible. Abbreviations should only be used if there is no alternative.
- Average rather than Avg. Amount rather than Amt.
4. Too many different types of information on one visualization
- Do not overload a single visualization with too much information (e.g., including, sales, demographic information, comparisons, etc.).
- This can overwhelm the business user. Instead, consider tooltips or separate charts.
5. Not using the appropriate visualization
- Do not to use a complicated visualization just because it is available. A visualization should only be used if meets the business requirements. For example, using a pie chart may not make sense with many dimension members. The same data is far more easily understood as a tree map.
6. Having insufficiently labelled data
- It should be possible to know the values being displayed on the dashboard without the use of tooltips or other interactions.