{"id":1608,"date":"2021-11-07T09:00:00","date_gmt":"2021-11-07T08:00:00","guid":{"rendered":"https:\/\/netprove.nl\/blog\/\/"},"modified":"2025-10-01T10:36:42","modified_gmt":"2025-10-01T08:36:42","slug":"the-most-common-mistakes-when-designing-dashboards","status":"publish","type":"post","link":"https:\/\/netprove.nl\/en\/blog\/the-most-common-mistakes-when-designing-dashboards\/","title":{"rendered":"The most common mistakes when designing dashboards"},"content":{"rendered":"

A while ago, we wrote an article<\/a> On the benefits of using a dashboard. Many organisations deploy the use of dashboards to create visualised overviews of their KPIs (Key Performance Indicators). But, how do you design a dashboard that shows results as efficiently as possible?<\/p>\n\n\n\n

The contents of a dashboard<\/strong><\/h3>\n\n\n\n

A dashboard should allow you to see and interpret how a variable is doing at a glance. Instead of a block of text, it shows the analysed information in graphs or figures. This means that dashboards should save the user time in understanding results by showing the most relevant information.1<\/sup> The aim is to see in which areas the organisation is doing well, and which areas need more attention.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Yet it is often the case that using dashboards is made much more difficult for users than it should be, which can cause problems. Below are the most common mistakes made when setting up a dashboard and how to fix them.<\/p>\n\n\n\n

Want to put as much information as possible on one page<\/strong><\/h3>\n\n\n\n

It is natural that once you work with dashboards, you want to get everything out of them. This often means that you tend to show all elements that have been measured (within the organisation) at once. The reason for this would be to immediately put down a complete picture for the organisation. Unfortunately, it is often forgotten that not all parties within the organisation benefit from seeing the same data. This abundance of data can lead to misleading interpretations of the required results.2<\/sup><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Using too many colours<\/strong><\/h3>\n\n\n\n

This applies to all visualisations. Organisations often tend to use lots of colours to make the environment look as beautiful and attractive as possible. In contrast, this can create more confusion and be perceived as overwhelming.<\/p>\n\n\n\n

So choose a limited number of standard colours and use them consistently. Once you use red to show a negative measurement result, you obviously don't use that same colour to show a positive measurement result at another point. There is also valuable information on the internet on this subject. Such as colours used for a specific purpose<\/a> in a dashboard and colour combinations <\/a>which have been proven to go well together.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Selecting arbitrary charts<\/strong><\/h3>\n\n\n\n

Graphs can quickly be misused. It is crucial that the correct chart is used when conveying information.3<\/sup> Using an incorrect graph can result in unreadable information or information that is not interpreted correctly. Both consequences can contribute negatively to drawing the right conclusions. If an element is shown in a line graph, it is seen as a trend of time. Thus, valuable information can be displayed incorrectly and wrong decisions can be made.<\/p>\n\n\n\n

Delve into the different types of charts and find out which chart best suits certain type of information. Is it a trend through time? Is it about proportions? Or do you want to compare elements? Make sure you know exactly what result of an element you want to demonstrate and base your choice of graph on that.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Not studying dashboard users<\/strong><\/h3>\n\n\n\n

Some designers assume that every user has the same analytical qualities. As a result, users may face more challenges than necessary. Users may not know where the relevant information is and may find it too confusing as a result.<\/p>\n\n\n\n

Check users' familiarity with (among other things) dashboard programmes and their knowledge of charts and statistics.4<\/sup> The ultimate goal of the dashboard is to create an environment for users that is time-saving, not time-consuming by having to learn new skills.<\/p>\n\n\n\n

The added value of a dashboard lies in creating an easy environment for users, who can find the desired information in a few blinks of an eye. Creativity is not always as important in such an environment. If it is a simple, but well-functioning dashboard, your users will benefit more than if it looks attractive but is difficult to use.<\/p>\n\n\n\n

Sources<\/h2>\n\n\n\n
    \n
  1. Justinmind. (s.d.). Dashboard design: best practices and examples. Consulted from https:\/\/www.justinmind.com\/blog\/dashboard-design-best-practices-ux-ui\/<\/li>\n\n\n\n
  2. Alhamadi, M. (2020). Challenges, strategies and adaptations on interactive dashboards. Proceedings of the 28th ACM Conference on User Modeling, Adaptation and Personalization<\/em>. doi: 10.1145\/3340631.3398678<\/li>\n\n\n\n
  3. Durcevic, S. (2020, September 9). 20 dashboard design principles & best practices to enhance your data analysis. Consulted from https:\/\/www.datapine.com\/blog\/dashboard-design-principles-and-best-practices\/<\/li>\n\n\n\n
  4. Ouwehand, G. (s.d.). In 5 steps to the perfect dashboard. Retrieved from https:\/\/www.axians.nl\/business-analytics\/blog\/in-5-stappen-naar-het-perfecte-dashboard\/<\/li>\n<\/ol>","protected":false},"excerpt":{"rendered":"

    Een tijdje geleden schreven wij een artikel over de voordelen van het gebruiken van een dashboard. Veel organisaties zetten het gebruik van dashboards in voor het cre\u00ebren van gevisualiseerde overzichten van hun KPI’s (Key Performance Indicators). Maar, hoe ontwerp je een dashboard dat zo effici\u00ebnt mogelijk de resultaten laat zien? De inhoud van een dashboard... Read more \"<\/a><\/p>","protected":false},"author":2,"featured_media":1621,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[77],"tags":[81,79,80,78,82],"class_list":["post-1608","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dashboards","tag-grafieken","tag-informatie","tag-kleuren","tag-ontwerp","tag-ux"],"acf":[],"_links":{"self":[{"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/posts\/1608","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/comments?post=1608"}],"version-history":[{"count":1,"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/posts\/1608\/revisions"}],"predecessor-version":[{"id":4715,"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/posts\/1608\/revisions\/4715"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/media\/1621"}],"wp:attachment":[{"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/media?parent=1608"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/categories?post=1608"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/netprove.nl\/en\/wp-json\/wp\/v2\/tags?post=1608"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}