{"id":2098,"date":"2017-05-13T03:47:59","date_gmt":"2017-05-13T03:47:59","guid":{"rendered":"https:\/\/blogs.scu.edu\/dataviz\/?p=2098"},"modified":"2017-05-13T04:00:33","modified_gmt":"2017-05-13T04:00:33","slug":"more-is-not-always-better","status":"publish","type":"post","link":"https:\/\/blogs.scu.edu\/dataviz\/2017\/05\/13\/more-is-not-always-better\/","title":{"rendered":"More is not always better"},"content":{"rendered":"<p style=\"text-align: left\">Let&#8217;s begin our discussion with an example. If you go\u00a0to a coffee house and see them serving 15 different varieties of coffees, there is a big chance that you will\u00a0be confused what to choose. Instead, when you go to a place having 2 variations in their coffee, you are likely to find your caffeine easily.\u00a0Research shows when there is too much choices, consumers are less likely to interpret them, and if they do they are not sure if\u00a0their selection is the &#8220;right&#8221; one.<\/p>\n<p style=\"text-align: left\">The service incident dashboard is one\u00a0such component that is usually over engineered and have too much information.\u00a0There is no doubt that it is one of the key tools used by the IT group\u00a0to make business decision, create release plan and estimate budget for the next business cycle. However, many such dashboard suffers from the &#8220;problem of plenty&#8221;. Let&#8217;s evaluate one such dashboard as shown below.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/doxwk67ta2990.cloudfront.net\/wp-content\/uploads\/2014\/11\/qlikview-poor-use-of-dashboard-software.png\" \/><\/p>\n<p>This dashboard breaks many rules of best practice dashboard design namely:<\/p>\n<ul>\n<li><strong>Unclear design:<\/strong>\u00a0Most of these dashboards are either presented to the manager, or displayed on the TV screen for the team, but its really difficult to read all the information properly. Too much details clutters the dashboard and the information are not easily comprehensible.<\/li>\n<li><strong>Inappropriate use of chart:<\/strong> To get the information from the stacked bar chart, we have to dissect the segments and spend time understanding everything. Use of pie chart to present too many section is not a good practice as it makes the chart exceptionally difficult to understand\u00a0and\u00a0determine the percentage of each item.<\/li>\n<li><strong>Bad use of legend:<\/strong>\u00a0This dashboard is heavily depended on the legends (for both pie charts and bar\/column charts) to communicate the information, which adds an additional cognitive barrier. User have to\u00a0look back and forth to read the charts. Also the legends are very long, which adds to the mess.<\/li>\n<li><strong>Inconsistent use of color:\u00a0<\/strong>\u00a0The selection of\u00a0colors for the charts is very distracting and not visually pleasing. But more importantly each color represents different information in\u00a0each widget, with the exception of the top-left widget and bottom-left widget. The &#8220;blue&#8221;, for instance, represents\u00a0different things on five different charts. This creates a huge barrier for the brain when trying to process the data quickly.<\/li>\n<li><strong>Poor data layout:\u00a0<\/strong>The layout is not consistent. The third row has three charts as compared to the first two which have two charts. The axis is also poorly labelled.<\/li>\n<\/ul>\n<p><span style=\"text-decoration: underline\">What should be done to fix this dashboard:<\/span><\/p>\n<ul>\n<li>It is important not to present too much data in one single dashboard, which brings us to the concept of identifying the right KPI for the business. Limited, but important information should be displayed that will make the dashboard less crowded.<\/li>\n<li>Creating\u00a0blank space between the charts\u00a0will make\u00a0the data easier to read.<\/li>\n<li>If the team is unable to set any KPI, then adding goals and targets to the visualizations, would also make it more actionable.<\/li>\n<li>Reducing the number of colors and keeping it consistent in all the charts will help to remove the cognitive barrier of color for viewers.<\/li>\n<li>Replacing the pie charts with either a\u00a0bar or column charts<\/li>\n<li>Using filters will also help users to see only the data they need. Currently the dashboard don&#8217;t have any filters associated.<\/li>\n<li>The font size should be bigger and the labels could be more crispier with smaller texts. This makes the dashboard more readable when presented to audience.<\/li>\n<\/ul>\n<p><span style=\"text-decoration: underline\"><strong>Conclusion<\/strong><\/span><strong>:<\/strong>\u00a0The dashboard we discussed tries too hard to provide a lot of information. As discussed in the beginning, when a consumer is provided with all metrics, none of them seem important. So even before designing the dashboard, it is imperative to understand what are the most important parameters that should go to the dashboard, in order to make it more effective.<\/p>\n<p>Source:\u00a0https:\/\/www.matillion.com\/insights\/why-great-dashboard-software-doesnt-always-equal-great-dashboards\/<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Let&#8217;s begin our discussion with an example. If you go\u00a0to a coffee house and see them serving 15 different varieties of coffees, there is a big chance that you will\u00a0be confused what to choose. Instead, when you go to a place having 2 variations in their coffee, you are likely to find your caffeine easily.\u00a0Research &hellip; <a href=\"https:\/\/blogs.scu.edu\/dataviz\/2017\/05\/13\/more-is-not-always-better\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">More is not always better<\/span><\/a><\/p>\n","protected":false},"author":2003,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"qubely_global_settings":"","qubely_interactions":"","kk_blocks_editor_width":"","_kiokenblocks_attr":"","_kiokenblocks_dimensions":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-2098","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"gutentor_comment":0,"qubely_featured_image_url":null,"qubely_author":{"display_name":"amarjit","author_link":"https:\/\/blogs.scu.edu\/dataviz\/author\/amarjit\/"},"qubely_comment":0,"qubely_category":"<a href=\"https:\/\/blogs.scu.edu\/dataviz\/category\/uncategorized\/\" rel=\"category tag\">Uncategorized<\/a>","qubely_excerpt":"Let&#8217;s begin our discussion with an example. If you go\u00a0to a coffee house and see them serving 15 different varieties of coffees, there is a big chance that you will\u00a0be confused what to choose. Instead, when you go to a place having 2 variations in their coffee, you are likely to find your caffeine easily.\u00a0Research&hellip;","post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/posts\/2098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/users\/2003"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/comments?post=2098"}],"version-history":[{"count":8,"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/posts\/2098\/revisions"}],"predecessor-version":[{"id":2224,"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/posts\/2098\/revisions\/2224"}],"wp:attachment":[{"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/media?parent=2098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/categories?post=2098"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.scu.edu\/dataviz\/wp-json\/wp\/v2\/tags?post=2098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}