Guidelines
Suggest edit

Use a line chart when totals are not the message

For ordered-time trend reading on part-to-whole time series, use a line chart instead of stacked columns when totals are not important to improve readability and mitigate hard-to-decipher stacked segments for readers scanning change over time.

  • purpose:select
  • basis:heuristic
  • time:ordered-time
  • chart:line:use
  • chart:bar:avoid
  • operator:part-whole
  • quality:readability
  • lever:chart-family

advice

Switch to a line chart

Replace stacked columns with a line chart when the total of the parts is not important on time data. For example, plot the component series as lines across dates instead of stacking them into columns when the reader only needs the over-time change.

reason

Why the line chart reads faster

Stacked columns make readers decode several segment positions that do not share a baseline, while a line chart lets them follow change over time directly.

Mechanism: The line chart removes the need to read both total height and shifting internal segment baselines, so the time pattern is quicker to decipher.

Evidence: The post says stacked column charts for dates should only be considered when the total is crucial, and that a line chart is a better choice when the total is not important because readers can decipher it more quickly (Muth, 2018).

context

Use when totals are unnecessary

  • User Goal: Show how component values change over time.
  • Task: Read change across dates rather than the combined total.
  • Data: Time series split into parts that sum to a total.
  • Chart Setting: A stacked column chart for dates is being considered.
  • Audience: Readers need a quick read of the temporal pattern.
  • Success Criterion: The trend is understandable without relying on total column height.

exceptions

Do not use when totals must stay visible

Break it when: The total of all parts is crucial and the chart needs to show totals and shares together. Why: That is the case where stacked columns can justify their extra reading effort.

costs

What you give up

Sacrifice: You give up the explicit total height that stacked columns show. Risk: Readers may no longer read the display as a part-to-whole chart. Mitigation: Make this switch only when the total is not part of the message.

mistakes

Common failure mode

Mistake: Keeping stacked columns even though the takeaway is only about how the parts change over time. Why it fails: Readers spend effort decoding stacked segments that do not help answer the question.

check

Test the chart choice

Failure Sign: The total height is present, but the takeaway never mentions it. Quick Check: Sketch the same data as stacked columns and as a line chart; if the line chart preserves the message without the total, choose the line chart. Stronger Test: State the takeaway without mentioning the total; if the statement still holds, the stacked total is unnecessary.

fix

Revise the design

  • Replace the stacked columns with a line chart for the component series.
  • Remove emphasis on total height if it does not support the message.
  • Keep the focus on the over-time changes that the reader actually needs.

References

Muth, L. C. (2018). What to consider when creating stacked column charts. https://www.datawrapper.de/blog/stacked-column-charts