gtmjosh
Report on What Matters
Chapters
  1. 01 · Ask a Business Question, Not for a Dashboard
  2. 02 · Choose the Right Population and Denominator
  3. 03 · Separate Volume, Speed, Quality, Cost, and Outcome
  4. 04 · Compare Trends and Useful Segments
  5. 05 · Use Leading and Lagging Indicators
  6. 06 · Show Sample Size, Missing Data, and Blind Spots
  7. 07 · Connect Summary Metrics to the Records
  8. 08 · Design for the Person Using the Report
  9. 09 · Capstone: Build a Reporting Brief
Guide overview →

14 min · Interactive exercise

Chapter 6 of 90 complete

Show Sample Size, Missing Data, and Blind Spots

Print the thing next to the number that stops it being misread.

This is the chapter most worth taking away, and it contains no statistics.

Show the count beside the average

A real breakdown displays a per-segment average next to the number of records in that segment, and carries a note saying the highest-scoring segment rests on too few records to be treated as a benchmark.

One extra column. That column prevents the single most common reporting error there is, which is somebody quoting the top segment's rate in a meeting as a target.

Note what it does not do: it does not suppress the number. Suppress the conclusion, not the data. Showing a rate on a handful of records with the count attached is honest. Hiding it is a different distortion, because now the reader does not know the segment exists.

The ratio that flatters

A real analysis reports two groups a couple of points apart and describes the difference as roughly double. Both statements are arithmetically true. They land completely differently.

“Three in a hundred versus five in a hundred” and “almost twice as likely” describe the identical finding. The first invites the question of whether two points is worth reorganizing around. The second sounds like a strategy.

Neither is a lie. The rule is simply: when you state a ratio, state the difference too. Both, together, one sentence. The reader can then decide which framing matters for their decision, which is their job and not yours.

Publish the blind spots

The best single practice in this space: a metric that ships with a section listing what it cannot see.

A real engagement metric publishes that a particular kind of activity earns nothing at all, that a scheduled event nobody attended still scores full marks until the date passes, and that events predating the record are invisible. Every one of those is a real limitation, published, next to the number.

A metric with a published blind-spot list is trustworthy in a way one without cannot be, and the reason is not that it has fewer blind spots. It is that somebody went looking.

GTM Lab

Saved locally
Metric Dictionary and Reporting Brief · 0 of 9 sections started

Saved locally to your browser.

Print the thing that stops it being misread

Three sentences above describe one identical finding. All three are true. Choose which belongs in the brief, then decide where a caveat is needed and where it is noise.

Fixture: three-honest-sentences

One finding, three framings, all true

FIXTURE-THREE-SENTENCES
As a difference
A couple of points apart
As a ratio
Almost twice as likely
With the sample size
A couple of points apart, on small groups
Arithmetically
All three identical
In a meeting
Three different decisions
Resets every run.
Which framing goes in the brief?
Which metrics need a sample-size disclosure?
What else travels next to a metric?
Chapter 6 of 90 complete