What is this chart for?

The slide is almost done. Someone pastes a colorful chart from the weekly export and says, “That should cover the metrics section.” Nobody can name the decision the chart supports. The title says “Revenue overview.” The colors are loud. The room nods because the chart looks like analytics happened. Then a director asks a simple question: “So what do we do differently on Monday?” Silence. The chart did not fail at being pretty. It failed at having a job.

This is Part 1 of Charts that make sense, a series for people who put charts into decks, Slack threads, and dashboard tabs. We start before chart types, axes, or color palettes. We start with purpose. If you skip purpose, every later choice is decoration with a legend.

What you’ll learn

• Why a chart is a job description, not wallpaper
• How explore, explain, and persuade differ in meetings
• A short purpose checklist before you open a chart tool
• A worked example that turns one table into three different chart jobs
• Common mistakes that make charts feel smart while saying nothing

A chart is a job, not a decoration

Finish this sentence out loud before you click Insert Chart: This chart helps someone decide whether to ___. If you cannot finish it, you are making atmosphere. Atmosphere can be fine for personal exploration. Atmosphere is a problem when it lands in a leadership deck as if it were a recommendation.

That habit matches Analytics foundations: question before output. A plot without a question is a screenshot of your curiosity. A plot with a question is a decision tool. Stephen Few’s practical writing on business graphs keeps returning to the same idea: graphs exist so people can see quantitative relationships that tables hide under effort. If the relationship is not clear, the graph has not done its work.

Alberto Cairo’s teaching on functional visualization makes a related point: charts are arguments about data, not free art. You can still care about craft. Craft is how the argument stays honest and readable. Craft is not “more gradients.”

Rule of thumb: If the chart vanished and nothing in the meeting would change, it was decoration.

Tools do not fix this. Sheets, Tableau, Power BI, and notebook plots all make it easy to produce a default chart in under a minute. Defaults are not evil. Defaults are unfinished. Your job is to finish the sentence the default never asked.

Think about the last deck you sat through. Count how many charts were “for completeness.” Completeness is not a job. Completeness is a fear of being asked a question you did not prepare. A shorter deck with three purposeful charts beats twelve slides of atmospheric graphics every time. Leadership rarely complains that you removed a chart that never changed a decision. They do notice when every slide demands attention and none of them answer the open question.

Purpose also protects your calendar. When a stakeholder asks for “a visual,” you can answer with a clarifying question instead of a two-hour detour: “Are we still exploring, or do you need a chart people can share as the explanation?” That one sentence saves rebuilds. It also trains the organization to treat charts as communication products with owners, not as automatic exports from every query.

Three jobs: explore, explain, persuade

Most workplace charts fall into three jobs. They can share the same data. They should not share the same design.

Explore: find what is going on

Explore can look messy on purpose. You are hunting, not presenting.

Exploration charts are for you, your pair, or a small working group that still expects surprises. You are allowed mess. You may keep extra series, rough filters, and notes in the margin. The success test is not beauty. The success test is learning: what pattern appeared that you did not expect?

Typical explore moves:

• Plot raw weekly values before you average them
• Split by region and notice one region drives the total
• Compare count and rate side by side so a small base does not trick you
• Zoom into a weird spike and check the extract date

Exploration often sits next to data quality work from the data quality series. A spike can be a real campaign. It can also be a late-loading batch. Exploring with a suspicious eye is not cynicism. It is professionalism.

Do not ship explore charts as final. The common failure is pasting your notebook hairball into a board pack because “that is what I was looking at.” What you were looking at is a lab bench. The board gets a clean lab report.

Explain: help people see the same story

Explain is cleaner: one claim, fewer series, a takeaway the room can share.

Explanation charts are for shared understanding. The audience should leave with the same picture of what happened, even if they still disagree about what to do. Titles get clearer. Series get fewer. Labels answer the first two questions people will ask. You remove the noise that only made sense while you were hunting.

Typical explain moves:

• Show the trend with one comparison line, not six overlapping brands
• Put the unit and time window in the subtitle so nobody has to guess
• Highlight the one category that changed the total
• Add a short note for known caveats (definition change, missing week, currency)

Explanation is where axis honesty and label craft matter most, because many people will only see this one view. If your SQL or Python handoff already produced a clean table (see the Python for analytics path, especially the plotting part), explanation is the communication layer on top of numbers you already trust.

Persuade: make a decision easier to take

Persuasion charts still have to be true. They are not free passes to truncate axes until your favorite option looks heroic. Persuasion means you have a recommendation and you design the view so the relevant comparison is unavoidable.

Typical persuade moves:

• Lead with the option ranking that matches the decision
• Show cost or risk next to upside so the pitch is not one-sided
• Use a before/after or with/without comparison when the action is a change
• Write a title that states the claim, then let the chart prove it

Persuasion fails in two opposite ways. One is soft: you present every series and hope the room invents the recommendation. The other is hard: you overstate by design (clipped baselines, dual axes that invent a fake relationship, color that screams emergency). Both waste trust. Trust is the only long-term currency analysts have.

A purpose checklist before you chart

Use this as a sticky note next to your monitor. It takes two minutes. It saves twenty minutes of rework after the first review comment.

If the decision is not open, you may not need a chart at all. Status that never drives action can live in a sentence: “Tickets are within normal range.” Charts earn their space when relationships are hard to see in text.

Same data, three jobs: worked example

Imagine a mid-size software company looking at support ticket volume by region for the last six weeks. Product wants more staffing. Finance wants proof. Ops wants a plan that will not create a new fire elsewhere. Here is the weekly total table after a clean extract.

Nothing exotic. Four regions, six weeks, rising total. Purpose still decides the chart.

Explore version

In exploration you might plot all four regions as lines, keep the daily extract open in another tab, and check whether South’s flatness is real or a reporting lag. You might also plot each region’s share of total, because a rising total with a stable South share is a different story from a rising South share. You might sketch a small multiples grid so scales stay comparable. You keep notes: “W4 East spike after release notes?” You are allowed to be messy.

Pseudo workflow (tool-agnostic):

# Explore notebook sketch (not a share slide)
# 1) plot each region over weeks
# 2) plot region share of total
# 3) flag weeks where any region moves >10% week over week
# 4) write questions in a cell, not a title:
#    - Is East growth support load or product adoption?
#    - Is South under-reported or truly smaller?
for region in ["East", "West", "North", "South"]:
    plot_line(week, tickets[region], label=region)
annotate_open_questions()
do_not_export_to_board_pack()

Explain version

For the weekly ops review you need shared understanding. One good explain chart is a stacked or grouped view of volume with a clear subtitle: “Weekly support tickets by region, W1 to W6.” Even better is a line for total plus a bar ranking of the latest week’s volume, if your tool can keep both honest. The title can be factual without being theatrical: “Ticket volume rose about 22% from W1 to W6; East and West still dominate.”

What you drop for explain: daily noise, unused brand colors, product-line breakdowns that nobody asked for this week. What you keep: units, time window, and the relative size of regions so “South is exploding” does not win the room by percent math alone.

Persuade version

Suppose the recommendation is: add capacity to East first, watch West, do not staff South based on percent growth alone. The persuade chart ranks latest-week volume (or a short average of recent weeks) and shows growth in a secondary encoding only after the absolute level is clear. The title states the claim: “Staff East first: it carries the largest volume and the largest recent increase.”

You might also show a small table under the chart with headcount already assigned, because persuasion without constraints is fantasy. Charts do not hire people. Managers do, with incomplete information. Your job is to reduce the incompleteness without inventing certainty.

How purpose changes design choices

Purpose is not a soft preface. It changes concrete choices:

• Chart type: ranking bars for a staffing decision, lines for a trend explanation, scatter only if the relationship is the point
• Aggregation: daily for explore, weekly for explain, latest window for persuade
• Annotation density: heavy notes in explore, few sharp callouts in explain, one claim-aligned callout in persuade
• Audience control: interactive filters for analysts, static PNG for a board PDF that cannot be clicked
• Uncertainty: show missing weeks and definition changes early; do not hide them to “keep the story clean”

If you later use matplotlib in a notebook (covered in Python for analytics), the code is not the hard part. The hard part is knowing whether you are exporting a scratch figure or a share figure. Two folders help: scratch/ and share/. That simple split prevents exploration mess from becoming “the official chart.”

Purpose also changes how you handle disagreement. In exploration, disagreement is fuel: two people can chase different cuts and compare notes. In explanation, disagreement about the picture is a problem to resolve with definitions and filters. In persuasion, disagreement about the action is expected, but disagreement about the facts on the slide should already be closed. If stakeholders still argue about what the number means, you are not ready to persuade. Go back to explain, or further back to data quality and metric definitions.

A practical meeting trick: label the slide corner with the job in tiny type for your own drafts (EXPLORE, EXPLAIN, PERSUADE). Remove the label before you send. The point is not branding. The point is that your hands slow down long enough to notice when you are about to paste a lab bench into a decision packet.

Common mistakes

• Default titles. “Chart 1” and “Sheet1” tell the room you did not finish the thought.
• One chart, three jobs. A single slide tries to explore, explain, and sell a reorg. Split them.
• Persuasion without a decision owner. Pretty ranking charts for audiences who cannot act become theater.
• Explaining with exploration clutter. Six series in six colors is not thorough. It is unresolved.
• Hiding caveats to keep the story smooth. Smooth stories break in the Q&A and take your credibility with them.
• Treating the chart as the analysis. The analysis is the chain from question to definition to number to claim. The chart is the last mile.
• Copying a template that was built for a different job. Last quarter’s “executive overview” may not fit this week’s staffing decision.

How to practice this week

1. Pick one chart you already sent in the last two weeks.
2. Label it explore, explain, or persuade. Be honest.
3. Write the decision sentence it was supposed to support. If you cannot, rewrite the chart or delete it.
4. Produce a second version for a different job using the same table. Notice what you remove.
5. Ask a colleague to state the takeaway in one sentence without you coaching. If their sentence mismatches yours, the chart is still exploring.

When you want more paths around charts, metrics, and SQL foundations, start from Learn. Next in this series we pick chart types for comparison, trend, composition, and distribution, with a short never-do-this list.

Quick recap

• A chart is a job: help someone decide, understand, or discover.
• Explore can be messy. Explain must be shared. Persuade must be true and decision-shaped.
• Same table can serve three jobs with three designs.
• Write the decision sentence before you open the chart tool.
• If the chart can vanish without changing the meeting, cut it.

Sources

• Stephen Few, Perceptual Edge (practical guidance on graphs for business): https://www.perceptualedge.com/
• Stephen Few, Show Me the Numbers (book site overview and resources): https://www.perceptualedge.com/library.php
• Alberto Cairo, teaching and books on functional visualization: https://www.albertocairo.com/
• Edward Tufte, principles on graphical excellence and integrity: https://www.edwardtufte.com/tufte/
• Financial Times, Visual Vocabulary (chart purpose by relationship type): https://github.com/ft-interactive/chart-doctor/tree/master/visual-vocabulary
• Analytics Made Simple, Analytics foundations series: https://analyticsmadesimple.com/series/analytics-foundations/
• Analytics Made Simple, Python for analytics (including plotting habits): https://analyticsmadesimple.com/series/python/

Merch on Etsy

Open store →

Mute Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, You're On Mute View on Etsy → You're On Mute White Ceramic Coffee Mug, Data Science Mug, Data Mug, Analytics Mug, Statistics Mug, Programming Mug, Gift Mug, Coffee Mug View on Etsy → Good Cheap Fast White Ceramic Coffee Mug, Data Science Mug, Data Mug, Analytics Mug, Statistics Mug, Programming Mug, Gift Mug, Coffee Mug View on Etsy → Naive Bayes Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Bayesian Mouse Pad View on Etsy →