Numerical communication and explaining scale
Making Numbers Count Summary: Explain What Numbers Mean
Making Numbers Count teaches communicators to translate numerical quantities into familiar comparisons and experiences so people can understand their meaning while retaining access to the underlying calculation.
One-Sentence Answer
Making Numbers Count teaches communicators to translate numerical quantities into familiar comparisons and experiences so people can understand their meaning while retaining access to the underlying calculation.
What The Book Is About
The US publisher’s edition identifies the subtitle as The Art and Science of Communicating Numbers and names both Chip Heath and Karla Starr. This guide uses that edition’s title rather than combining subtitles from different markets.
The authors’ official introduction distinguishes translating numbers from making a graph look better. Its concern is the meaning an audience can grasp. The practical case here concerns a fictional community sports center. All volumes, timings and staffing assumptions are invented for transparent arithmetic, not results reported by the authors or a recommendation to buy particular software.
Who Should Read It
Read it when listeners can repeat a number but cannot explain why it matters. A program manager describing a workload, a teacher explaining scale or an analyst presenting a comparison may find it more immediately useful than another lesson on chart formatting. You do not need to call yourself a numbers person to ask what a quantity means in everyday terms.
Choose a different starting point if you need statistical inference, survey design or a detailed visualization manual. A memorable analogy cannot repair a biased sample or an unsuitable comparison. For a charting task, Storytelling with Data is more directly focused; for a complete executive recommendation, DataStory provides a broader communication frame.
Main Summary
Making Numbers Count addresses a common gap between calculating a figure and communicating it. A presenter may have checked every formula, yet the audience still experiences a large quantity as an indistinct amount. Heath and Starr propose translation: connect numerical information to something the audience can picture, compare or experience. Their approach concerns how a number becomes understandable, rather than simply how it looks on a page.
The publisher highlights perspective cues, vivid comparisons, processes unfolding over time and measuring sticks connected to what people value. The authors’ introduction describes a collection of short techniques and worked transformations, rather than one mandatory presentation sequence. You can use the book as a source of alternatives when the technically correct wording leaves people without a usable sense of scale.
Consider our invented sports center. Its desk handles 1,200 bookings in a month. Staff estimate that a proposed form might reduce handling time by 90 seconds per booking. The multiplication produces 108,000 seconds, or 30 hours. None of those statements alone explains what the proposal would change for a receptionist trying to handle a queue.
Assuming 20 opening days, the estimate becomes 90 minutes of handling time per day on average. That translation gives the team something concrete to question. Are bookings evenly spread? Would the saved time occur while people are waiting? Does the estimate include help with the new form? A useful translation can improve the discussion precisely because people can inspect its assumptions.
This guide organizes the reading into five applications: state the comparison’s starting point, choose a familiar unit, describe a process, connect the amount to a real task and check that the translation remains faithful. This is an editorial practice sequence, not a five-part framework attributed to Heath and Starr.
The practical goal is an explanation that makes the magnitude easier to discuss without turning an estimate into a promise. Retain the original figure, its unit and the calculation. Ask the listener what they now believe the number means. If their interpretation exceeds the evidence, revise the translation before relying on its persuasive effect.
Key Ideas
1. Establish what is being counted before choosing a comparison
A perspective cue can help an audience interpret an unfamiliar quantity. Before designing one, make sure that the original measure has a clear referent. A figure cannot become meaningful through comparison if the speaker and listener are counting different things. This preliminary check is our application of the book’s translation problem, not a statistical method supplied by it.
At the sports center, 1,200 bookings does not necessarily mean 1,200 visitors or 1,200 distinct customers. One customer might make several bookings. One booking might reserve a court for several players. If the manager translates the number into people served without checking the records, the explanation changes the subject while appearing to clarify it.
The manager can begin with a short definition: one completed reservation entered at the desk counts as one booking. Next specify the month and whether cancellations are included. Those choices determine which comparison is useful. For a discussion of desk workload, transactions may be appropriate. For a discussion of access to community facilities, distinct participants or available sessions may answer a different question.
Write the original measure beside the proposed translation. Label the unit, period and population before searching for a vivid phrase. Invite a colleague to describe what they think the count includes. If they infer something different, correct the definition first. That small check prevents an appealing analogy from concealing an unresolved measurement problem. The result may sound less dramatic, but the audience has a firmer basis for asking the next question.
2. Choose a scale the audience can use without extra decoding
The publisher identifies familiar perspective cues and vividness among the book’s techniques. A useful comparison should reduce the listener’s interpretive work. It should not require a second explanation that is harder than the original number. Familiarity depends on the audience, so an analogy that helps a specialist may confuse a new colleague.
Our manager initially describes 108,000 seconds of potential monthly savings. A receptionist has little reason to think about a month in seconds. Dividing by 3,600 gives 30 hours. Under the explicit assumption of 20 opening days, dividing again gives 90 minutes per day. Each version represents the same estimated total, but the last one connects to the planning horizon of a shift.
Keep the relevant version for the decision. A finance colleague checking an annual projection may need monthly totals and assumptions. A receptionist deciding when to test a form may need the effect during busy periods. Neither audience benefits from cycling through every mathematically possible conversion to display the presenter’s ingenuity.
Try two translations with a willing listener. Ask which one helps them answer a practical question and what, if anything, remains unclear. Retain the original number in the supporting material so the transformation can be traced. Reject a comparison that creates a false equivalence, such as treating handling time as interchangeable with paid staffing. Choosing a familiar scale is useful when it clarifies the quantity’s role; it becomes misleading when it silently changes what that quantity represents.
3. Turn an abstract total into a process people can inspect
Converting a quantity into a process over time is one of the techniques identified by the publisher and illustrated in the authors’ introduction. Our application is to show where an estimate accumulates. A process description can make the total easier to question because the audience can inspect a repeated event rather than confront one large figure.
For the fictional desk, imagine one reservation requiring two minutes of manual entry. The proposed form is estimated to reduce that work to 30 seconds. The difference is 90 seconds per transaction. Multiply that difference by the assumed 1,200 monthly bookings to reach 30 hours. Showing the sequence lets staff identify a weak assumption: perhaps complicated bookings take longer, while routine bookings already require very little help.
The manager can propose a small observation exercise before making a commitment. Record handling time for a suitable mix of transactions, separately noting time spent correcting errors or assisting someone with the form. Explain that the initial figures are planning assumptions. The exercise might support, reduce or overturn the original estimate; this guide does not predict which result will occur.
When presenting a recurring quantity, describe one instance, its frequency and the period over which it accumulates. Keep average and peak conditions separate. An average of 60 bookings per opening day says little about a queue concentrated in the first hour. A process translation helps when it exposes such questions. It should leave the listener better able to challenge the estimate, not merely more impressed by the cumulative total.
4. Connect the amount to something people have a reason to care about
The publisher describes measuring sticks linked to concerns that matter to the audience. That need not mean adding emotion to every slide. It can mean explaining which real task a quantity affects. Our critical application is to distinguish a meaningful consequence from an outcome the available data cannot establish.
Receptionists care about answering visitors, dealing with unusual requests and avoiding a queue. Saying that the form might release 90 minutes of handling time on an average opening day gives those concerns a possible connection to the estimate. It does not show that waiting time will fall by 90 minutes, that every employee gains a long break or that one position can be removed.
The manager should ask staff where the time is likely to become available. Small gaps spread across the day may permit different work from a continuous block. If the new form creates a need for troubleshooting during the busiest hour, the effect on the queue could differ from the monthly arithmetic. These are operational questions for the center, not conclusions contained in the number.
Before presenting a quantity, complete two sentences in your notes: this could matter because, and this does not yet establish. The first keeps the communication tied to the audience’s task. The second prevents a resonant comparison from carrying an unsupported promise. Ask the listeners which consequence they need to evaluate. Their answer may reveal that a different measure, such as a distribution of handling times, would be more useful than the headline total.
5. Preserve the route back from the vivid version to the evidence
A memorable numerical explanation still needs a way back to its inputs. The authors’ introduction emphasizes understanding quantities accurately as well as intuitively. Our accompanying practice is to keep a short calculation record and test what the audience infers. This is an editorial safeguard for using translations, not a claim that the book teaches a complete audit procedure.
The manager’s record could contain four lines: estimated 1,200 transactions; estimated reduction of 90 seconds each; 108,000 seconds divided by 3,600 equals 30 hours; 30 hours divided by 20 opening days equals 1.5 hours per day. Label both the volume and the reduction as assumptions unless they have been measured. If the center opens on a different schedule, update the daily conversion.
Now ask a colleague to explain the proposal to someone else. If they report a guaranteed 30-hour payroll saving, the translation has traveled beyond its support. Clarify that the estimate concerns handling time, with no established staffing or cost outcome. If they think the center processes exactly 60 bookings every day, distinguish a monthly average from a daily forecast.
Use the listener’s restatement as feedback on the explanation. Avoid treating a quick nod as proof of understanding. Retaining the calculation does not require placing every detail in the opening sentence; it requires making the route accessible when questions arise. The best version allows people to grasp the scale and investigate its limits. Both abilities matter when the number will influence a consequential decision.
Practical Takeaways
- Define the thing being counted, its population and its time period before creating a comparison.
- Keep a plain original-number statement next to the translated version in your working notes.
- Choose a unit that fits the audience’s next decision, rather than the one that makes the result sound largest.
- When describing an accumulating total, show one event, its frequency and the period of repetition.
- Separate an average from the busiest interval and an estimate from an observation.
- State a relevant possible consequence and one outcome the number does not yet establish.
- Ask a listener to restate the meaning, then repair any inference that goes beyond the calculation.
How To Apply It
Take one number from a presentation you already give. Write its precise definition and identify the question you want it to help answer. Produce three alternatives: the original unit, a familiar comparison and a description of the process over time. Do not alter the underlying quantity to make one alternative more impressive.
Check the arithmetic separately from the wording. List assumptions about duration, frequency and the population being counted. If you round a result for an introduction, keep the unrounded value in the working calculation and avoid suggesting more precision than the inputs justify. Ask someone familiar with the subject to inspect the comparison for hidden changes of meaning.
Then ask a willing listener outside the specialty which version helps them understand the scale. Have them explain what they would do next and what they still need to know. This informal exercise does not establish general comprehension rates. It gives you a concrete misunderstanding to repair before the real discussion.
For the center, the next step might be timing a modest trial rather than announcing a staff reduction. Write down the measurement needed to test the assumption and who will review it. A useful numerical translation can end in a better question, not only a stronger recommendation.
Best Related Books
- DataStory is a better companion when the task is turning analysis into a complete recommendation and an audience decision.
- Storytelling with Data concentrates more directly on visual explanations, chart choices and removing distracting presentation elements.
- Made to Stick places concreteness and memorable communication in a broader framework for ideas beyond numerical quantities.