A topic in the Open Knowledge Graph — a free, open map of 15,290 topics and the order to learn them in.
Reference class forecasting predicts the outcome of a specific case by looking at the base rate of similar cases — the "reference class." Instead of asking "how long will MY software project take?" (subject to optimism bias), ask "how long do software projects of this type and size typically take?" The outside view, as Kahneman calls it, anchors your estimate to empirical reality before you adjust for case-specific factors. Bent Flyvbjerg's research on infrastructure projects showed that reference class forecasting dramatically reduces cost overruns. The technique is simple: identify the reference class, find the distribution of outcomes, and use that as your starting point.
Apply reference class forecasting to a personal project: before estimating how long it will take, look up how long similar projects took for other people. Notice the gap between your inside-view estimate and the base rate. Practice identifying the right reference class — too broad loses specificity, too narrow loses statistical power.
From calibration training, you know that most people are systematically overconfident -- their stated certainty exceeds their actual accuracy. Reference class forecasting is one of the most direct and effective tools for correcting this overconfidence, and it works by replacing the question you naturally ask with a better one.
When you plan a project, your mind naturally takes the inside view: you examine the specific details of your plan -- the steps, the team, the technology, the timeline -- and construct a mental scenario of how it will unfold. This scenario is vivid, detailed, and almost always optimistic. You imagine the steps going roughly as planned, perhaps with minor setbacks you account for. What you do not imagine is the full distribution of delays, surprises, and failures that actually occur in projects like yours -- because you are focused on your plan's unique features, not on the base rate of outcomes for the reference class. Kahneman and Tversky identified this as the root cause of the planning fallacy: the inside view systematically generates optimistic estimates because it constructs a best-case narrative rather than consulting empirical data.
The outside view -- reference class forecasting -- asks a different question: "What actually happened to projects like this one?" Instead of "how long will my software feature take?", you ask "how long do software features of this type and complexity typically take at my company?" If historical data shows that similar features average 4 weeks, and your inside-view estimate is 1 week, the 4-week number should be your anchor. You can still adjust for genuinely distinctive features of your project -- perhaps this feature uses a technology your team knows unusually well -- but the adjustment should be modest and explicit, starting from the base rate rather than from your optimistic scenario.
Bent Flyvbjerg's research on infrastructure projects provides dramatic evidence of the technique's value. He found that large infrastructure projects consistently overrun their budgets by 50% or more, and that this pattern persists across decades, countries, and project types. Planners know about past overruns but consistently believe their project will be different -- the inside view generates compelling reasons for exceptionalism every time. Reference class forecasting cuts through this by forcing the planner to confront the base rate before constructing the narrative. The practical skill is choosing the right reference class: too broad (all construction projects) loses meaningful similarity, too narrow (only suspension bridges built in the same country in the last five years) leaves too few data points. The ideal reference class is narrow enough to be genuinely comparable but broad enough to provide statistical signal. Once you have it, the base rate anchors your estimate to what actually happens rather than what you hope will happen.
Topics in reflective domains aren't scored by quiz answers. Read, reflect, and mark when you've thought it through.