False Precision: Why Specific Numbers Feel More Credible Than They Are
When you forecast something, the grain you report should track the evidence you actually have. Report it finer than that and you're smuggling false confidence into the room. Here's how to set the grain right, and how to read someone else's.
Someone on your team presents the five-year plan: revenue of £12.4 million in year three, £18.7 million by year five, margin of 22.3%. The decimals do something to the room. Nobody pushes back, because the numbers look worked-out, and the people in the chairs start building plans on top of them. You half-know that predicting revenue to three figures five years out is a fiction. But the precision overrides that knowledge anyway, and the slide gets treated as a measurement when it’s really just a guess.
You already know precision and accuracy are different. Precision is how fine the number is: 22.3% is finer than “low twenties.” Accuracy is how close it lands to what actually happens. A forecast can be extremely fine and badly wrong at the same time. Skip the definition, because the part that matters is this: the fineness of a number is itself a claim about how much evidence sits behind it, and most people pitch that claim far higher than their evidence can pay for. Your real job is to set the grain to match the evidence, and to read the grain when someone hands you theirs.
The evidence
Start with why the fiction sells. When people judge two forecasts, the fine point estimate gets rated as more expert and more useful than the wide range, even when the range is the one more likely to contain the true answer. Say “between 10% and 30%” and you’re marked down as less competent than the person who says “23.7%,” despite having told the more honest story. This is the accuracy-informativeness trade-off, and it’s among the more reliably reproduced findings in judgment research. It sets up a perverse incentive: the forecaster who shows real uncertainty gets penalised, and the one who hides it behind decimals gets rewarded with credibility. Audiences pull for precision, so forecasters supply it, accuracy be damned.
It gets worse once the number drives a decision. When people are handed precise probability estimates, they treat them as more reliable than vague ones, commit resources harder on them, and hedge less, even when the precise and the vague numbers came out of the very same model. The fineness of the figure, not the strength of the evidence, is what moves the money.
And there’s a reason it works on capable people, not just careless ones. People are poor at holding a probability distribution in mind. Told there’s a 70% chance of something, you don’t naturally build the 30% world where it doesn’t happen. You round the 70% up toward “basically yes.” A point estimate makes this worse by collapsing a whole spread of outcomes into one value and hiding the spread completely. The single number is not only easier to remember than the range, it actively erases the variance you most needed to see.
How it works
Two things run underneath this. The first is fluency. A clean figure like £18.7 million is easy to process, easy to repeat, easy to anchor a plan to. A range like £12M to £25M asks more of you: hold two numbers, sit with the gap, plan for more than one world. Your mind reaches for the figure not because it’s more useful but because it’s less work, and that ease gets mistaken for solidity.
The second is the one most people miss, and it’s where your leverage is. A range carries information that a point estimate throws away: the width is a readout of the evidence. A forecast of £17M to £20M and a forecast of £10M to £30M are not two versions of the same claim with different caution settings. The first says the evidence is good enough to pin the answer inside a narrow band. The second says the evidence can barely tell apart two futures that would mean very different things for your plan. Same midpoint, completely different state of knowledge. When the analyst reports only the midpoint, that readout is exactly what gets deleted, and you lose the one number that told you how much to trust the rest.
The width of a range is the part that tells you how much to trust it, and it’s the part people delete when they report only the midpoint.
The discipline, then, isn’t to chase the finest number you can. It’s to match the grain of the estimate to the quality of the evidence. The strongest forecasters do this on purpose: they reach for fine probabilities, 65% against 70%, only when their evidence genuinely supports a distinction that sharp, and they coarsen to “roughly likely” when it doesn’t. The grain of the number should report the evidence, and nothing beyond it.
How to use it
When a number lands in front of you, ask for the range before you do anything with the point estimate. If the person can’t give you one, the precision is invented and you should treat the figure as a guess. If they can, read the width before you read the middle. A tight band on a delivery estimate (“done in eight to ten weeks”) is a real claim about real evidence. A band of “two to six months” tells you the honest answer is that nobody knows yet, and you plan for the slow end.
Then check where the precision is coming from, because not all of it is fake. A calibrated instrument reading 23.7 degrees is fine and accurate both, because it was built to deliver that resolution. A five-year revenue model reading £23.7M is fine and almost certainly not accurate, because the model’s error bars dwarf the decimal. The test is simple: does the precision come from a measuring device with known resolution, or from an estimate where the decimals are decoration? Measurement earns its grain. A model usually hasn’t.
The harder move is on your own side of the table, because the same incentive that fools you will tempt you. When you forecast a launch date, a deal size, a vendor’s delivery, you’ll feel the pull to give a crisp number, because crisp reads as competent and the range reads as hedging. Hold the line. Set the grain to your evidence and say it out loud: “eleven to thirteen weeks if the integration holds, and I’d widen that to sixteen if it doesn’t.” When your evidence is thin, widen on purpose: “somewhere between fifty and seventy thousand users, and I can’t narrow that honestly yet.” You’ll feel less impressive in the moment. You’ll be right more often, and the people who plan off your numbers will learn they can.
Why it matters
Look back at the estimates that hurt you most and they share a shape. A revenue line modelled to the decimal came in a third under. A product forecast to reach 50,000 users got to 12,000. In each one the original number was fine enough to feel like a commitment, so everyone downstream built as if it were one. The figure wasn’t just wrong. It was wrong in a way that hid how unsure it always was, and that concealment is what made the plans on top of it so brittle.
The whole professional culture pushes the wrong way here. Clean numbers look decisive, ranges look wishy-washy, and the person who says “it depends on three things I can’t predict” looks less useful than the one who picks a number and sounds sure. So the system keeps rewarding false precision and keeps paying for it later, off-screen, when reality arrives. The fix isn’t to give up on precision. It’s to stop handing it out for free, and to start treating every fine number, yours and theirs, as a claim that has to be backed by evidence of the right grain before you build anything on it.
References
- Yaniv, I., & Foster, D. P. (1995). Graininess of judgment under uncertainty: An accuracy-informativeness trade-off. Journal of Experimental Psychology: General, 124(4), 424–432.
- Budescu, D. V., & Du, N. (2007). Coherence and consistency of investors' probability judgments. Management Science, 53(11), 1731–1744.
- Goldstein, D. G., & Rothschild, D. (2014). Lay understanding of probability distributions. Judgment and Decision Making, 9(1), 1–14.
- Tetlock, P. E., & Gardner, D. (2015). Superforecasting: The Art and Science of Prediction. Crown.
- Gigerenzer, G., Hertwig, R., van den Broek, E., Meder, B., & Martignon, L. (2005). 'A 30% chance of rain tomorrow': How does the public understand probabilistic weather forecasts? Risk Analysis, 25(3), 623–629.
One tool a week
How you think, decide, lead, focus, and stay steady under pressure. A specific way to practice one move before the next seven days are out. Grounded in evidence, not self-help.
One email a week. Leave whenever. Powered by Buttondown.
You're almost in. Check your inbox to confirm your subscription.