Knowing when a number is good enough
Analysis can always be refined. More data, more controls, more scenarios, a better method — each improves the estimate and each costs time. Knowing when to stop is a skill and it is rarely taught.
The stopping rule comes from the decision rather than from the analysis.
What is the stopping rule?
That further precision would not change what is done. If the decision is the same across the plausible range of the estimate, the estimate is good enough and additional work is spent for comfort.
That is an easy test to apply and it requires the decision to be named, which is why it is so often skipped.
How do you apply it in practice?
Take the current estimate and its range, and check the decision at both ends. If both ends point the same way, stop. If they point different ways, the remaining uncertainty is decision-relevant and more work is justified.
The same test tells you what kind of work is needed: narrowing the range that matters rather than refining everything.
What are the costs of over-refinement?
Time, the delay to the decision, and a false impression of certainty. An analysis refined for three weeks arrives with more precision and an implicit claim to authority that the underlying data may not support.
There is also an opportunity cost that is rarely counted. The analyst refining a sufficient answer is not answering the next question.
What are the costs of stopping too early?
A decision made on an estimate whose range crosses the threshold, which is a decision made effectively at random. That is the failure the stopping rule is designed to prevent, and it is why the rule is about the decision rather than about effort.
How does this interact with presentation?
A good-enough estimate should be presented as such, with its range. Presenting a deliberately rough answer with precise-looking figures invites it to be treated as more than it is, and it will then be quoted in contexts the roughness cannot support.
Rounding appropriately is part of this. A figure quoted to several significant digits from an estimate with a wide range is making a claim the analysis does not.
What about numbers that will be reused?
They need more care, because a figure produced for one decision has a habit of being quoted in another where the tolerance is different. Anything likely to circulate deserves the range and the caveat attached to the number itself.
What should an analyst say when asked for more precision?
What it would cost and what it would change. If the answer is that it would not change the decision, that is worth saying plainly, and it is frequently accepted.
Frequently asked questions
Who decides what is good enough?
The decision-maker, informed by the analyst's statement of the current range. Leaving it entirely to the analyst produces either over-refinement or an arbitrary stop.
How do I estimate the range early?
Rough bounds from the data's own variability, before any modelling. An early range is usually available in minutes and it frequently shows that the question is already answered.
What if the range is too wide to decide?
Then either more evidence is needed or the decision should be structured to be reversible. Recommending a small reversible step is a legitimate response to irreducible uncertainty.
Does this apply to recurring reports?
Yes, and it should be applied to their level of detail. Reports accumulate precision nobody uses, and trimming them to what is acted on saves production time every period.
How do I resist pressure for more decimal places?
By explaining what the decimal places would mean given the underlying uncertainty. A figure presented to the nearest whole unit with a stated range is more informative than one presented to three decimals with none.
Is a rough answer risky?
Only if presented as precise. Labelled clearly, a rough answer delivered in time is usually more valuable than a precise one delivered late.
What about high-stakes decisions?
They justify more precision, and the same rule applies with a tighter threshold: refine until the decision is stable across the range, then stop.
Does this conflict with rigour?
No. Rigour is about doing the analysis correctly and honestly, not about doing more of it. A rigorous rough estimate is entirely possible and frequently the right output.
What is the single question to ask?
Would a better number change what we do. Asked at the start, it scopes the work; asked during, it ends it at the right point. Public statistical practice, such as the Census Bureau's published series, models the habit of pairing an estimate with its uncertainty.
How should a good-enough number be recorded?
With its range, its method and a note that it was produced to a tolerance. That note is what stops it being quoted later in a context that requires more precision than it has.
### What should a brand actually do with this?
Ask the stopping question at the start of the work rather than in the middle. Asked early it scopes the analysis; asked late it feels like giving up, which is why analysts tend not to ask it at all.
Then state the tolerance in the output. A figure labelled as an estimate to a stated tolerance survives being quoted; an unlabelled one becomes a fact the moment it leaves the document.
Working with retail data? See NRS Insights data solutions or contact NRS Insights.