Five lessons, about 55 minutes. Not a statistics course — just the handful of ideas that stop you from being confidently wrong in front of Chidi.
Chidi reads one number more than any other: "average basket size." It is also the single easiest number to accidentally misrepresent, in four specific ways worth knowing by name.
| Outliers pull it | One ₦180,000 wholesale order among two hundred normal ₦4,000 baskets drags the average up enough to make every branch look busier than it is. The median wouldn't move. |
| It hides a bimodal split | An "average" basket size of ₦8,000 can mean everyone spends around ₦8,000 — or it can mean half the customers spend ₦2,000 and half spend ₦14,000, with almost nobody near the average itself. |
| It changes meaning across group sizes | Averaging nine branch averages together is not the same as averaging every individual transaction — a branch with fewer, bigger baskets gets equal weight to one with many small ones. |
| It erases the trend inside the period | A month's average can look flat while masking a real decline in the second half that a single number never shows. |
"What's the average?" is rarely the real question. "What's typical, and how much does it vary?" usually is — and that needs at least two numbers, not one.
Two branches can post the exact same average daily revenue and be running completely different businesses — one steady day after day, the other swinging wildly between a great Saturday and a dead Tuesday. The average alone can't tell them apart; the spread can.
| Branch A | Daily revenue: ₦410k, ₦395k, ₦420k, ₦405k, ₦415k — average ₦409k, tightly clustered. Predictable staffing and stock needs. |
| Branch B | Daily revenue: ₦180k, ₦650k, ₦210k, ₦590k, ₦415k — same average ₦409k, wildly inconsistent. Same average, completely different operational problem. |
You don't need a formal standard deviation calculation to make this point to Chidi — the range (highest minus lowest) or simply eyeballing daily values against the average usually says enough. The habit that matters is remembering to look, not the specific formula.
Branches that run more promotions also tend to have higher footfall. It would be easy — and wrong — to conclude promotions drive footfall. The confounder here is obvious once you look for it: bigger, busier branches both run more promotions (they can afford to) and naturally get more footfall (they're in busier locations). The promotion isn't causing the footfall; branch size is driving both.
"Branches running promotions have higher footfall" is a true, defensible correlation. "Promotions increase footfall" is a causal claim the data alone doesn't support. Say the first sentence, not the second, until you've actually ruled out the obvious confounder.
"Yaba's numbers were down 20% this week" sounds alarming. Whether it should worry Chidi depends enormously on how much a branch's week-to-week numbers normally bounce around — which is a sample-size question in disguise.
If Yaba's weekly revenue normally varies by ±25% just from ordinary randomness — different weather, different days of the week the month lands on, one big or small order — then a 20% dip is comfortably inside normal noise and probably means nothing. If Yaba's weekly revenue is normally rock-steady within ±3%, a 20% dip is a real signal worth investigating immediately.
"Is this a real change, or just noise?" is answerable with one look at the branch's normal week-to-week variation — you rarely need a formal significance test to make a sound call.
A single week's result, on its own, is a sample of one. Before treating any single week's swing as meaningful, compare it against several previous weeks of the same branch — not against a different branch, and not against a gut feeling of "that seems like a lot."
Sahara Mart trialled a new receipt layout with a loyalty-points reminder at three branches for two weeks, against six branches running the old layout. The trial branches showed 4% higher loyalty sign-ups. Is the new receipt the reason?
The honest answer to Chidi is rarely a clean "yes, roll it out" or "no, scrap it." It's closer to: "the early signal is positive and worth continuing to test, but two weeks at three branches isn't enough to be confident it'll hold at scale — recommend extending the trial before a full rollout."
You'll need the worksheet pack's number tables for this one — it's a paper-and-calculator drill, not a written-only exercise.
Three claims, each pulled from an actual Sahara Mart branch-manager WhatsApp message, each sounding entirely reasonable on first read.
For each, write what's actually wrong with the claim as stated, what additional number or comparison you'd want before believing it, and the honest, appropriately-hedged version of the sentence you'd actually send to Chidi.
Not whether you can compute a p-value — none of these claims need one. It's testing whether the five habits from this module (average vs. spread, correlation vs. causation, normal variation vs. real signal) fire automatically the moment you read a confident-sounding claim, the way they'd need to in a real Monday-morning WhatsApp thread.
Module 6 turns to Power BI — building the dashboard that puts these same numbers in front of Chidi in a form that doesn't invite the overclaiming this module just spent 55 minutes guarding against.