The idea
A table lets the reader look up a number. A chart does something stronger: it makes a comparison for the reader, instantly, before any number is read. The eye compares positions, lengths and slopes, and it trusts what it sees more than the labels beside it.
So choosing a chart is choosing the comparison you are asking the reader to make. A chart whose visual comparison matches the real comparison is honest. One whose picture says something the data does not is misleading, even if every number on it is correct.
Figure 1
Start from the question, then pick the chart
-
linehow does it change over time? -
bar from zerohow do groups compare? -
histogramhow is one column spread? -
scatterdo two columns move together?
- Change over time asks the eye to follow a path, so use a line. Harbor & Pine's monthly revenue is a line: it rises into November and December and drops in February.
- Comparing groups asks the eye to compare lengths, so use bars that start at zero. Desktop against mobile conversion is a bar chart, and the bars are only honest when the baseline is zero.
- The shape of one column, like order value, is a histogram: bars of counts per band. A bar chart of the average would hide the long tail you saw in chapter 1.
- The relationship between two columns, like spend and revenue, is a scatter: one dot per row, with the pattern visible.
Why it exists
A dashboard or a slide is usually read in seconds by someone who will not open the data. Their decision comes from the picture. That makes the chart, not the table under it, the thing that actually communicates. If a team's marketing deck says "desktop converts several times better than mobile" and the supporting chart agrees, the budget moves, even if the true difference is 60%.
The same logic runs the other way. A true, important gap deserves a chart that shows it at its real size. A 60% difference in conversion is already a reason to look into mobile, and an honest chart makes that case without needing to shout.
An analyst who only checks the numbers is checking the wrong thing. The question to ask of any chart is: what will a reader conclude by looking, and is that what the data supports?
How it works under the hood
Bars must start at zero
A bar encodes a value as a length. Length is only proportional to the value if the bar begins at zero. Cut the axis and you remove a fixed amount from every bar, which changes the ratios between them.
Harbor & Pine's desktop conversion is 3.87% and mobile is 2.41%. Draw the axis from 2%, and the bars are 1.87 and 0.41 points tall.
Figure 2
What the deck's bars show when the axis starts at 2%
- The deck's chart starts its y axis at 2%, so it draws only what is above 2%. Desktop converts at 3.87%, so its bar is 1.87 points tall.
- Mobile converts at 2.41%, so its bar is only 0.41 points tall. The desktop bar is drawn 4.6 times as tall.
- The real ratio is 3.87 divided by 2.41, or 1.6 times. The chart is accurate at every point and still makes a 60% gap look like 360%.
The same two numbers, drawn from zero, look like what they are.
Figure 3
The same two bars, starting at zero (conversion rate, %)
- Starting at zero, bar length is proportional to the number. Desktop is clearly higher, and a reader sees a gap of the right size.
- Desktop's bar is 1.6 times mobile's, exactly the real ratio. The gap is real and worth knowing, and it no longer needs a dramatic picture to be taken seriously.
Lines are different. A line encodes position and slope, not length, so a line chart does not need a zero baseline, and starting at zero can flatten a real trend into nothing. Use zero for bars, whatever fits the data for lines, and label the axis either way.
Many series: small multiples
Six lines on one chart force the reader to trace each one through a tangle. When the question is "how does each channel behave?", six small charts with the same axes beat one crowded chart, because the eye compares shapes side by side. This is the idea of small multiples. Fix the scales the same across panels, or the comparison breaks again.
Noise: smoothing with a rolling average
Daily revenue jumps with weekdays, weekends and promotions, and the wiggle can hide the trend. A
7-day rolling average, daily.rolling(7).mean() in pandas, replaces each day by the mean of that day
and the six before it, so every point covers one of each weekday and the weekly cycle cancels out.
Show the raw data faintly behind it, and say a rolling average was applied. Smoothing never adds
information. It trades detail for readability, and it lags the real series by a few days.
Parts of a whole
A pie chart asks the reader to compare angles and areas, which people do badly. When the slices are close, the difference is invisible. A sorted bar chart of the shares, or a table of percentages, makes the ranking obvious. Keep a pie for two or three parts where the point is a clear majority.
Review any chart with four questions
Before a chart leaves your hands, ask: what comparison does the eye make first? Does the axis start where the encoding needs it to? Could a reader come away with a conclusion the data does not support? Would the answer survive if the chart were shown to the people it is about? A chart that fails any one of them gets fixed, even when the numbers behind it were right. Fixing the chart often starts with fixing what it plots: the metric, the period or the baseline.
A dashboard answers a decision
A dashboard with every metric the data allows answers nothing. Start from the decision the reader makes, such as whether to move budget between channels, and show exactly the comparisons that decision needs, in the order they need them.
Common misconceptions
"The chart uses the real numbers, so it cannot be misleading"
Accurate numbers can still give a false picture. The cut-off axis above uses exact conversion rates and makes a 60% gap look like 360%. Honesty is about the comparison the picture invites, not only the data behind it. Read the axis first, then the bars.
"A line chart with the y axis starting at zero is always the honest choice"
For bars, yes. For lines, a zero baseline can flatten a meaningful change: a conversion rate that moves from 2.8% to 3.4% looks like nothing on a 0 to 100 axis. Fit the axis to the data, label it, and keep the same range across charts that will be compared.
"Smoothing a chart is cheating"
Smoothing is fine when it is disclosed and the raw data is still available. A 7-day average of daily revenue is a standard tool because it removes the weekly rhythm and leaves the trend. It is misleading only when presented as the raw data, or when the window is so wide it erases a real event.
Check yourself
One question. Answering it ticks this lesson off on the map; it never locks a level.
Not quite. 1.6 times is the true ratio, but the chart does not show it. The drawn length is the number minus the baseline.Try another answer.
Right. The drawn heights are 1.87 and 0.41, and 1.87 / 0.41 is about 4.6. The chart turns a 60% gap into a 360% one.
Not quite. The 2% baseline is subtracted from each bar before comparing; it is not a multiplier.Try another answer.
Not quite. Sharing an axis does not make bar lengths proportional to the values. That only holds when the axis starts at zero.Try another answer.
Lesson done: it is ticked on the map.