"A candlestick chart provides an effective overview of the highs and lows within a given period of time. It wonʼt describe every last detail of what happened between the highs and lows, or precisely when they occurred, but it does reveal a trend, something that would be near impossible in a table." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"A sin of omission – leaving something out – is a strong one and not always recognized; itʼs hard to ask for something you donʼt know is missing. When looking into the data, even before it is graphed and charted, there is potential for abuse. Simply not having all the data or the correct data before telling your story can cause problems and unhappy endings." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"An indication that the data is not statistically sound is when it is almost too precise." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"Another way to obscure the truth is to hide it with relative numbers. […] Relative scales are always given as percentages or proportions. An increase or decrease of a given percentage only tells us part of the story, however. We are missing the anchoring of absolute values." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"Be aware that bar charts provide ample opportunities for chart junk. The space within the bars is enticingly empty and it is tempting to put images or textures in the background. Some designers even swap out the standard bars for graphics." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"Colour is a very powerful way to draw attention to specific portions of the design. Colour evokes feelings and emotions, making it an essential component in branding." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"Dealing with a circular visualization and trying to compare its radial portions is always problematic. When designing with data, the story should always be told as clearly as possible. To do so, it is often best to avoid round charts and graphs." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"Good graphic design is not a panacea for bad copy, poor layout or misleading statistics. If any one of these facets are feebly executed it reflects poorly on the work overall, and this includes bad graphs and charts." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"It is tempting to make charts more engaging by introducing fancy graphics or three dimensions so they leap off the page, but doing so obscures the real data and misleads people, intentionally or not." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"One way a chart can lie is through overemphasis of the size and scale of items, particularly when the dimension of depth isnʼt considered." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"Part of the problem with using gauges and dials as alerts is that they become part of the background. If 99% of the time the needle sits in the green, the gauge isnʼt worth looking at; then that one per cent of the time when it is in the red, the gauge will go unnoticed." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"So what is the difference between a chart or graph and a visualization? […] a chart or graph is a clean and simple atomic piece; bar charts contain a short story about the data being presented. A visualization, on the other hand, seems to contain much more ʻchart junkʼ, with many sometimes complex graphics or several layers of charts and graphs. A visualization seems to be the super-set for all sorts of data-driven design." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"Sometimes itʼs better to have fewer choices and focus on the charts that best convey the story. A doughnut chart is not one of these. By removing the centre of a pie chart, it further hinders the ability to judge the weight of each segment. Moving from a healthy wedge to two arcs makes it harder for people to comprehend what value is represented. We know that a full pie chart is one hundred per cent and that any wedge is a fraction of that; if we are presented with only an arc, is it equivalent to the wedge, or is it less because it is missing a portion?" (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"The amount of information rendered in a single financial graph is easily equivalent to thousands of words of text or a page-sized table of raw values. A graph illustrates so many characteristics of data in a much smaller space than any other means. Charts also allow us to tell a story in a quick and easy way that words cannot." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"The biggest difference between line graphs and sparklines is that a sparkline is compact with no grid lines. It isnʼt meant to give precise values; rather, it should be considered just like any other word in the sentence. Its general shape acts as another term and lends additional meaning in its context. The driving forces behind these compact sparklines are speed and convenience." (Brian Suda, "A Practical Guide to Designing with Data", 2010)
"Using colour, itʼs possible to increase the density of
information even further. A single colour can be used to represent two
variables simultaneously. The difficulty, however, is that there is a limited
amount of information that can be packed into colour without confusion."
(Brian Suda, "A Practical Guide to Designing with Data", 2010)
No comments:
Post a Comment