Communicating findings

Ravi adds a short Monday session on November 9 because, as he puts it, an analysis nobody understands has not happened. The occasion is Lena's quarterly review with the regional managers, for which Mateo must present what the team found about returns this autumn. He has a strong finding, the boot sizing problem from lesson 7, and a confusing one: the overall web return rate rose from the third quarter of 2025 to the third quarter of 2026, yet it fell in almost every product category. This session is about turning results like these into a message people can act on.

Start with the audience and the decision

Before writing a single sentence, ask who will read the findings and what they will decide. Regional managers have twenty minutes, think in stores and categories rather than tables, and decide where to send merchandising and customer service effort next quarter. Finance wants exact figures that reconcile with its own reports. Executives want the answer and the size of the money at stake. The same analysis becomes three different pieces of communication, and Mateo's first draft, a ten-slide tour of every query he wrote, serves none of them.

Lead with the answer

Business readers want the conclusion first, then the support. A useful structure is: the answer in one sentence, two or three supporting points with evidence, then the recommendation and any caveats. This is sometimes called the pyramid principle. Mateo rewrites his opening from "This analysis examined web returns from July to September across all categories" to "Web returns cost about 39,000 dollars more this quarter than last year, mainly because customers bought more footwear, which is returned more often; within most categories, return rates actually improved." The second version tells the reader what happened before they decide whether to read on.

Give every number a comparison

A number alone means little. "Return rate 6.4 in 100" is only useful next to something: last year, the target, other regions, or other categories. Each headline figure in Mateo's summary carries a comparison and a time frame, and each comparison is fair, using the same calendar period, the same definition and, where seasonality matters, the same weeks of the year. Lesson 2's August and September example showed how unequal periods can mislead.

Units and precision matter too. Monetary figures are rounded to what the decision needs: "about 39,000 dollars" in the summary, exact cents only in Finance's table. Rates are written consistently, and since Birchline's house style writes rates in words rather than symbols, Mateo writes "6.4 in every 100 orders" or "6.4 per 100 orders". Large counts get thousands separators. Dates name the year.

Choose the chart for the question

Each chart should answer one question, stated in its title. "Footwear returns jumped after October 6" is a better title than "Returns by category by day", because it tells the reader what to see.

A few rules prevent most misleading charts. Bar charts start at zero, because the length of a bar is read as the size of the value. Line charts may start elsewhere, but the axis should be clearly labeled. Avoid two different measures on two y-axes, which invites readers to see relationships that depend only on the scales chosen. Sort bar charts by value unless the categories have a natural order such as months. Use color sparingly and meaningfully, one accent color for the thing that matters and gray for the rest, and do not rely on red and green alone, since many readers cannot tell them apart; add labels or patterns.

The mix effect: when the whole disagrees with the parts

Mateo's confusing result is a classic. The overall web return rate rose, but the rate fell in most categories. Both statements are true at once, because the mix of what customers bought changed: footwear, which is returned far more often than other categories, made up a larger share of web sales in 2026. This pattern, where a trend in the combined data reverses the trend within every group, is known as Simpson's paradox. Reporting only the overall rate would wrongly suggest service or quality got worse everywhere.

# Web sales and returns by category, third quarter (thousands of dollars)
data = {
    #             2025 sales, 2025 returns, 2026 sales, 2026 returns
    "Footwear": (300, 42.0, 700, 91.0),
    "Apparel":  (900, 54.0, 850, 46.8),
    "Camping":  (800, 24.0, 750, 21.0),
}
print("category   2025 rate  2026 rate")
for cat, (s25, r25, s26, r26) in data.items():
    print(f"{cat:9}  {r25 / s25:9.3f}  {r26 / s26:9.3f}")

tot = [sum(v[i] for v in data.values()) for i in range(4)]
print(f"{'Overall':9}  {tot[1] / tot[0]:9.3f}  {tot[3] / tot[2]:9.3f}")
print(f"Footwear share of sales: {data['Footwear'][0] / tot[0]:.2f} -> {data['Footwear'][2] / tot[2]:.2f}")
print(f"Extra returns in dollars: {(tot[3] - tot[1]) * 1000:,.0f}")

category   2025 rate  2026 rate
Footwear       0.140      0.130
Apparel        0.060      0.055
Camping        0.030      0.028
Overall        0.060      0.069
Footwear share of sales: 0.15 -> 0.30
Extra returns in dollars: 38,800

The output shows exactly the pattern in Birchline's data: footwear fell from 0.140 to 0.130, apparel from 0.060 to 0.055, camping from 0.030 to 0.028, yet the overall rate rose from 0.060 to 0.069, because footwear's share of web sales grew from 0.15 to 0.30. Mateo's summary says both things, in that order, with one chart of rates by category and one of the sales mix. The recommendation follows naturally: focus on footwear sizing, where most returns now come from, rather than on general return processes.

Correlation, causation and uncertainty

Analysts are often asked "why", and data more easily shows "what" and "together with what". Stores that ran the autumn promotion had higher sales, but they were also the stores chosen because they were already busy. Saying "the promotion raised sales" from that comparison confuses correlation with causation. Stronger evidence comes from a fair comparison: similar stores with and without the promotion, or a test where stores are assigned at random. When only correlation is available, say so plainly: "stores that ran the promotion sold more; we cannot yet tell how much of that was the promotion."

Uncertainty belongs in the message too. A forecast from lesson 6 has a prediction interval, and the summary should give the range, not only the middle: "holiday sales are forecast at 4.1 million dollars, likely between 3.8 and 4.4 million." A difference between two small groups may be noise; with only a few hundred orders in a store, a change in return rate of one or two orders per hundred can easily happen by chance. If a result would change a decision, check whether it holds over a longer period or a larger group before presenting it as fact.

Writing the findings memo

Birchline's analytics team uses a short template for written findings, and Mateo's quarterly memo follows it.

The caveat about September orders is important and easy to forget. Some September orders are still within their return window, so the third-quarter return rate will rise slightly as late returns arrive. Mateo states the size of the effect, about one return per 1,000 orders based on last year's late returns, so nobody is surprised when the figure moves.

Making results reusable and accessible

Findings should outlive the meeting. The dashboard keeps the key charts current; a scheduled email delivery from Data Studio sends a PDF of the summary page to regional managers every Monday at 07:00; the notebook and SQL live in the team's repository so another analyst can reproduce the numbers. For accessibility, charts have descriptive titles, the text includes the key numbers so screen-reader users and people reading on a phone get the message without the chart, and color is never the only way information is shown.

Presenting in the meeting

Written findings and spoken ones differ. In the quarterly review, Mateo has ten minutes, so he plans three slides, each with one message in its title: returns cost more because the mix shifted to footwear; within categories, return rates improved; one boot model's size chart caused a spike that is now fixed. He rehearses saying each message in a single sentence before showing the chart, then pointing to the part of the chart that proves it. Questions he expects, such as "how do we know it is not a quality problem?", get a short prepared answer and a backup chart rather than an improvised query during the meeting.

He also prepares for disagreement. A regional manager is likely to say her stores' returns feel higher than ever; the evidence answers that her stores' rate fell, while their footwear sales doubled. Ravi's advice is to acknowledge the experience and then show the number that explains it, because people accept data more readily when it accounts for what they have seen. After the meeting, Mateo sends the memo and the dashboard link, so the discussion continues from the same facts.