You might have heard multiple times, that beautiful dashboards are attractive, memorable and people want to spend time with them. But more often, it is enough for your dashboard just to look professional.
We do want to make beautiful dashboards because beauty is attractive, looks tidy, reliable and helps to create impact with our visualizations. But beauty is also just a package – the value of a dashboard is in the way it helps to read the data intuitively. Forgetting all other things except beauty might lead to poor readability and a confusing experience overall, in other words makes users more frustrated than happy.
“Considering the audience” is one of the most important pieces of advice in storytelling and data visualisation. It is generally suggested to think about their needs, goals, and ability to understand the items displayed in the visual.
This allows our message to reach them more easily and resonate with them better, but the idea of “considering the audience” itself is quite vague. In this article, I will turn the vague suggestion “consider the audience” into something more checklist-like, which you could go through and consider the audience “considered”.
What if your client or stakeholder asks to make the dashboard you prepared to be more eye-catching, beautiful, or just cool? In such cases, we have one job – a very subtle one – to enhance UI without sacrificing UX, dataviz or information designs, maybe even enhancing them altogether.
You can find maybe 1000 articles with “most important”, “essential” or “golden” rules of data visualization and their set will be unique every time. Here, I will try to extract principles for data visualization from the underlying reasons why data visualization is even a thing.