We all love gauges because they are round, colorful, and mesmerizing. However, they are also the most misused object in the QlikView world. Although there is no need to demonize these visualizations, it is important to highlight when and how to use them. Here are a few features to take note of:
- These objects capture a lot of attention, so it is advisable to use them only to represent the most important figures in a dashboard.
- Gauges are not suitable for all KPIs. Before deploying these visualizations, it is better to consider whether they can adapt to the type of data that is being displayed. Really, sometimes they don't even make sense.
- Gauges are visible enough, so you can change the default colors (which are very intense) with tones that are lighter and easy on the eye.
- Their pixel-to-value ratio is very low. Gauges take a lot of space and usually convey only one or two ideas. For example, it might show 16 percent of employee turnover along with a yellow status. As a designer, you need to evaluate whether you are willing to sacrifice valuable screen space displaying a huge gauge instead of using it for a more useful object, such as a bar chart or a trend line.
- It is widely known that when a five-year-old kid learns a new word, he tries to use it anywhere and anytime until he drives everyone around him crazy. Well, this phenomenon occurs to QlikView designers as well; but instead of words, it happens with gauges. When you find a new gauge chart in a demo or a blog, there's a powerful urge to use it in all your applications. However, be careful not to force new visualizations into contexts where they don't fit. Please. Control. Yourself.
- Use a gauge style that matches your KPIs. Usually linear gauges work better for completion rates and comparisons, round gauges for ratios, and traffic light gauges to display a status.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.