Short answer: the pie (and its donut cousin) shows one simple part-to-whole split — and it’s overused for jobs a bar chart does better, because people read lengths far more accurately than angles. Reserve it for a single whole with two to four clearly-different slices where “share of total” is the literal message: package-format share, on- vs off-premise split. More slices, similar sizes, or any ranking question — use a bar chart. The donut just adds a centre label; otherwise the distinction is cosmetic.

PIE / DONUT — A SIMPLE PART-TO-WHOLE, FEW SLICES100%volumeCan · 50%Keg · 30%Bottle · 20%More than ~4 slices?Use a bar chart instead —length beats angle for comparison.
A donut works for a clean three-way split with a centre total; past four slices, switch to bars.

Part of The Brewer’s Chart Field Guide. This is the short, cautionary entry — because the pie is the most overused chart in business.

When to reach for it (and when not to)

A pie is honest only when all of these hold: the parts genuinely sum to one meaningful whole, there are very few slices (two to four), and the slices differ enough that angle comparison is easy. The moment you want to rank, compare across two pies, or show more than a handful of categories, a bar chart wins. The donut variant simply frees the centre for a total or KPI — handy on a dashboard tile, otherwise the same chart.

Use case 1 — Package-format share

Can / keg / bottle as a share of total volume — three clearly different slices, a real whole. A legitimate pie, and a donut lets you put total volume in the hole.

Use case 2 — On- vs off-premise split

A two-slice donut on an executive tile, with the total in the centre, communicates the channel split at a glance. Two slices is where pies are genuinely fine.

Use case 3 — A single survey or sentiment split

“Sober-curious vs regular” or a simple yes/no/maybe from a consumer survey — few categories, one whole. Past four answers, switch to bars.

Where this breaks

Many or similar slices — angles you can’t compare; use bars. Comparing two pies — almost impossible; use grouped or 100% stacked bars instead. 3D / exploded pies — actively distort area and mislead; never. Tiny slices — get lost; group into “other” or change chart.

The bottom line

The pie and donut earn a place only for a simple part-to-whole with very few, clearly-different slices where “share” is the literal message — package mix, channel split. For everything else, especially ranking and comparison, a bar chart is more honest because we read length better than angle. Use pies sparingly and you’ll never mislead with one. Next, composition with many parts and a hierarchy: the treemap.

Frequently asked questions

When is a pie chart appropriate for beer data? Rarely, and only for a simple part-to-whole split with very few slices (two to four) where the proportions are very different and the total genuinely is 100% of something. A single package-format share, or on- versus off-premise split, can work. For ranking, comparison, or more than a handful of categories, a bar chart is clearer because people read length better than angle.

Pie chart or donut chart — does it matter? Barely. A donut is a pie with the centre removed, which frees space for a total or KPI label in the middle — useful on a dashboard tile. Neither fixes the core weakness that angles and areas are hard to compare. Choose a donut when you want the centre label; otherwise the distinction is cosmetic.

Why do data people dislike pie charts? Because humans judge angles and areas far less accurately than lengths, so a pie makes comparison harder than a bar chart for almost no benefit. Pies with many slices, similar-sized slices, or 3D effects are genuinely misleading. The dislike is about overuse for jobs a bar chart does better, not the shape being evil.