NeuroNomixer
  • Home
  • Blog
  • Visual Guides
  • Authors
  • Contact
Sign InSign Up
HomeBlogAuthorsContactPrivacy Policy

© 2026 NeuroNomixer — Built with Next.js & Tailwind CSS

Visual Guides/When Averages Lie: Aggregation Traps
Data & Analysis

When Averages Lie: Aggregation Traps

Two of the quietest decisions in any analysis are the level you aggregate at and the number you divide by. Neither feels like a decision, and either one can flip your conclusion. Flip both, on live data, and learn to hear the click.

Compare pooled and by-severity views
Find the reversal point
Flip a winner with the denominator

Sign in to save progress

One dataset, many honest summaries

An average is not a fact about the world. It is a fact about the world plus two choices: which rows you pool together, and what you divide by. Change either choice and the same table can tell the opposite story, with no error anywhere. The classic pooled-vs-group flip is Simpson's paradox, and its causal reading, when should you trust the grouped view, lives in the Simpson's paradox guide. This guide stays on the analyst's side of the desk: aggregation level and denominator as everyday grouping craft, the two questions to ask before you believe any average.

How this playground stays honest: both clinics treat 800 whole patients whose counts follow the fixed recovery odds printed on their cards, and the stores keep their full user and session ledgers on screen. Every rate, gap, tie point, and winner on this page is recomputed from those integer counts on every slider move and toggle. Nothing is scripted.

1 · The level trap: two clinics, one flip

Northside is the better clinic for mild cases and the better clinic for severe cases. Referrals send it the harder mix. Drag the case mix sliders, toggle between the pooled table and the by-severity table, and find the point where the pooled winner flips even though Northside never stops winning both groups.

Recovery rate, 800 patients per clinic

Northside
87.0% (696/800)
Riverside
81.6% (653/800)

Pooled verdict: Northside leads by 5.4 pts

ClinicSeverityTreatedRecoveredRate
Northsidemild56052193.0%
Northsidesevere24017572.9%
Riversidemild56048787.0%
Riversidesevere24016669.2%

Every rate above is recovered divided by treated from this table, and the table is rebuilt from the sliders on every move.

30% severe

The referral center. Better with mild cases and better with severe cases.

560 mild · 240 severe · fixed skill: mild 93%, severe 73%

30% severe

The neighborhood clinic. Worse with mild cases and worse with severe cases.

560 mild · 240 severe · fixed skill: mild 87%, severe 69%

Hunt the reversal point

With Riverside as it is now, the two pooled rates tie near 57% severe at Northside, computed from the fixed skills and Riverside's current pooled rate. Drag Northside past that point: the pooled winner flips while both group winners stay put.

2 · The denominator trap: per what?

Two online stores sell the same goods. Store A is a browsing app that people open constantly; Store B is an errand people run once. The raw ledger is identical either way you read it. Switch the denominator and watch the conversion crown change heads.

Purchase rate

Store A
60.0% (60/100 users)
Store B
50.0% (50/100 users)

This framing says: Store A converts better, by 10.0 pts

Per user asks: how likely is a person to buy this month? Per session asks: how likely is a single visit to end in a purchase? Both are honest fractions of the same table below. They answer different questions, so they can crown different winners.

4 sessions per user

Store A is the app people open on the couch. More browsing means more sessions, while its 60 buyers still buy exactly once each.

100 users × 4 = 400 sessions

The whole dataset

StoreUsersBuyersSessions
Store A10060400
Store B10050120

Every buyer purchases in exactly one session, so purchase sessions equal buyers in both stores. Both rates on the left are computed from this table on every change.

The two questions to ask before trusting any average

Aggregated over what?

Pooling rows mixes their compositions. If the groups being compared carry different mixes, the pooled number rewards the easier mix, not the better performer. Always look at both levels before picking one.

Divided by what?

A rate is a claim about its denominator. Per user, per session, per order, and per dollar are four different questions wearing the same percent sign. Say the denominator out loud in every headline you write.

When the views disagree

A pooled-vs-grouped conflict is a signal, not a bug: some mix variable differs between the things you are comparing. Whether the pooled or the grouped answer is the right one is a causal question; the Simpson's paradox guide takes it from here.

← All GuidesNext Guide →