Use pie charts only for relative part-whole reading
For part-whole reading, use relative-value interpretation on pie charts to improve fidelity and mitigate mistaken absolute-value lookup for novice readers.
- purpose:refine
- basis:empirical
- chart:pie-donut
- operator:part-whole
- lever:encoding
- quality:fidelity
- literacy:novice
advice
Read slices as shares
Use pie chart slices for proportions and share comparisons, not for absolute values. For example, use a pie chart to identify the smallest share or compare whether one share is larger than another, but do not use a slice to read a raw count.
reason
Why relative reading fits the chart
A pie chart shows how each part relates to the whole. It does not directly show absolute values as independently readable magnitudes.
Mechanism: Slice size supports reading proportion, rank, and part-whole comparison. Absolute-value lookup over-asks what the slice encoding visually represents.
Evidence: In the VLAT blueprint, pie charts were marked as supporting only relative-value tasks, and the retained pie-chart items asked for relative share retrieval, smallest share, and relative comparison rather than absolute-value reading (Lee et al., 2017).
context
Use when the message is about shares
- User Goal: Compare parts of a whole.
- Task: Relative-value retrieval, extremum finding, or share comparison.
- Chart Setting: A pie chart with categorical parts.
- Audience: Novice or non-expert readers.
- Success Criterion: Readers answer in terms of proportion, ratio, or which share is larger or smaller.
exceptions
Do not use when the message requires raw counts
Break it when: The reader needs exact absolute values from each category. Why: The slices encode only relative value in the whole.
costs
Tradeoffs of keeping the chart in relative terms
Sacrifice: You give up direct absolute-value lookup from the chart.
Risk: Readers may still treat a slice as if it supports a precise raw number.
Mitigation: Keep surrounding prompts and interpretations in share, ratio, or percentage terms.
mistakes
Common failure mode
Mistake: Asking a pie chart to answer a raw-value question. Why it fails: The chart encodes share of the whole, not a directly readable absolute amount.
check
How to test the chart
Failure Sign: The surrounding question or annotation asks for a raw count from a slice.
Quick Check: Scan the chart text for count-oriented wording instead of share-oriented wording.
Stronger Test: If the intended answer must be a precise absolute value rather than a proportion or ordering of shares, the pie chart is being used for the wrong readout.
fix
What to change
- Rewrite the task or annotation in proportion, ratio, or share terms.
- Remove exact absolute-value claims from slice-based readouts.
- Replace the pie chart when exact value lookup is the main requirement.