Tool/Mental Model/No. 0381
Fermi Estimation
Fermi estimation is a method for estimating an uncertain quantity by breaking it into simpler parts and combining rough guesses with arithmetic. Named after physicist Enrico Fermi, it gives an order-of-magnitude estimate and makes the assumptions behind the result explicit.
Also called Fermi Estimate · Fermi Method
- Evidence
- Useful, modest evidence
- Read
- 6 min
- Links
- 8 connections
01You've seen this when…
- in life
You are budgeting a move. Before every item has been weighed, you estimate boxes per room and weight per box.
- at work
A team needs a storage budget for a camera system. Nobody has the final specification, so you start with cameras, recording hours and file size per hour.
- out in the world
A council considers collecting food scraps from households. Before commissioning a study, staff estimate households, participation and kilograms per participating household each week.
02The idea
Reasonable guesses for the parts can give you a way to estimate a total that seems beyond reach. Estimating a city’s weekly food waste sounds impossible. Its parts are easier to estimate: start with the number of households, then work out how many will participate and how much waste each will produce.
Fermi estimation turns one difficult unknown into several simpler ones. You make the assumptions visible and connect them with arithmetic to calculate a rough answer. Often the aim is an order-of-magnitude estimate: knowing whether you need hundreds, thousands or millions, with only enough precision to identify that scale.
The calculation matters, and the model does the most important work. A list of ingredients forces you to say what you think drives the total. Someone can then make a disagreement with your final number specific by challenging a particular assumption.
This differs from reference-class forecasting, which starts with outcomes from comparable cases. Fermi estimation usually builds upward from components. The two work well together: comparable cases can supply or check your guesses.
It is not permission to invent confident numbers. It is a way to make uncertainty inspectable.
03How to use it
- Name the quantity and its unit. Specify what you need: tickets per week, dollars per year or liters per event. Add a time period and boundary. Estimating active users is a different task from estimating registered accounts.
- Build a short chain of components. Write the total as a few quantities multiplied, divided or added together. For support workload, that might be users × fraction contacting support × tickets per contacting user × minutes per ticket. Start simple, then add detail only when it changes the answer.
- Give each input a basis. Use a known fact, a comparable case, a small sample or an explicitly labeled guess. Round generously. Keep units beside the numbers so mistakes such as mixing daily demand with weekly capacity are easier to catch.
- Calculate a central estimate and alternatives. Work out a reasonable middle case, then change uncertain inputs to plausible lower and higher values. These are scenarios. Calling their range a statistical confidence interval requires statistical justification. Avoid reporting more precision than the inputs deserve.
- Check the answer another way. Compare it with a known total, a physical limit or a similar operation. If you estimate that a small venue sells more lunches than it has visitors, revisit the model. A second calculation offers a stronger check when it uses different ingredients.
- Investigate the assumption that could change the decision. Use sensitivity analysis: change one input and watch the result. If checking one uncertain input could determine whether you hire two people or ten, that information has high value.
04A worked example
Imagine a software company preparing a launch. It expects 20,000 new users during the first week. The operations lead must arrange temporary support coverage, but the product has no launch history. The following numbers are illustrative assumptions.
What it looks like An unanswerable staffing question. There is no reliable forecast of how many people will ask for help, and the team could spend days debating a head count.
What’s actually going on Staffing depends on a chain of smaller quantities. The lead writes down a first-pass model:
- Expected new users total 20,000. This comes from the launch team’s forecast.
- Five percent contact support. That gives 1,000 people needing help.
- Each contacting user generates 1.5 tickets on average. That gives 1,500 tickets, including follow-ups.
- Each ticket takes eight minutes of active work. That gives 12,000 minutes, or 200 hours.
- Each agent provides 25 hours of ticket handling that week. Training and meetings take part of the week, and agents also need time for other duties. The total is eight agent-weeks.
Eight estimates total workload. A finished staffing plan also requires knowing whether everyone will arrive on Monday morning and whether particular languages need separate coverage. Lowering the contact rate from 5% to 3% gives roughly five agent-weeks with the same calculation. At 8%, it gives roughly thirteen.
What made it work The model exposes the contact rate as a consequential uncertainty. The team can test onboarding with a small group and consult similar launches before committing. It can also plan flexible coverage for peaks. The estimate turns a vague disagreement about staffing into specific questions about how available capacity compares with the workload implied by demand and handling time.
05When to reach for it
It is especially useful early in planning, when choosing what to investigate next matters more than producing a final forecast.
06When it misleads
- The structure is wrong. Even careful arithmetic carries through structural errors when a model omits repeat purchases, double-counts customers or ignores a capacity limit. Such errors are model risk.
- Every guess leans in the same direction. Rough errors can accumulate. An enthusiastic planner can produce a badly inflated total by overestimating demand and conversion while also assuming high spending.
- An average hides the constraint. Eight agent-weeks might cover total support work and still leave customers waiting during a sharp arrival peak. Check the total against the capacity of the bottleneck.
- A neat answer acquires undeserved authority. Multiplying guesses can produce 8.37, giving uncertain inputs an appearance of precision. Resist the appeal of precision; report a rounded estimate and its assumptions together.
- A rough result becomes authorization. A preliminary estimate can identify whether a bridge design or medical supply plan is plausible. Establishing safety in consequential decisions requires appropriate measurements, expert review and a justified margin of safety.
Stop refining when the next improvement is unlikely to change what you do. Keep refining when the decision sits close to a threshold or the cost of being wrong is high.
07Roots
At the Trinity nuclear test in New Mexico in July 1945, Enrico Fermi used scraps of paper as an improvised measuring instrument. As the blast wave reached him, he dropped the pieces and observed how far they moved. He used that displacement to estimate the explosion’s strength at about ten kilotons of TNT.
The paper complemented the test’s instruments. It gave Fermi a quick estimate of scale while more elaborate measurements were being assessed. The episode captures the habit behind the technique: connect something observable to the quantity you need through a workable physical model.
Approximate calculation existed long before Fermi. His name became attached to a particularly resourceful version, associated with his scientific problem-solving and teaching. Questions such as how many piano tuners a city could support became familiar examples: begin with population, estimate piano ownership and tuning frequency, then divide by a tuner’s capacity.
Later teachers carried these questions beyond physics. Books such as Lawrence Weinstein and John Adam’s Guesstimation made the approach accessible through everyday problems. The enduring lesson is a practical approach to estimation: a large unknown often becomes tractable once its ingredients are visible.
08How solid is this?
Fermi estimation is a well-established practice in scientific and practical problem-solving. Forecasts can still be inaccurate: reliability depends on the model and inputs. Several rough guesses need not cancel one another’s errors.
09Connections
- Helps counterModel Risk, Appeal of Precision
- See also Sensitivity Analysis, Margin of Safety, Value of Information, First Principles Thinking, Bottleneck, Reference-Class Forecasting
10Origin and sources
Named after physicist Enrico Fermi, whose teaching and scientific problem-solving in the 20th century emphasized estimates built from simple assumptions. Approximate calculation itself predates him.
- [1]Weinstein, L., & Adam, J. A. (2008). Guesstimation: Solving the World's Problems on the Back of a Cocktail Napkin. Princeton University Press.
- [2]Rhodes, R. (1986). The Making of the Atomic Bomb. Simon & Schuster.
Suggest an edit· Updated 2026-10-02