Difference between revisions of "Planning fallacy"

From Lesswrongwiki
Jump to: navigation, search
m (byline removal)
Line 17: Line 17:
*[http://lesswrong.com/lw/jg/planning_fallacy/ Planning Fallacy]
*[http://lesswrong.com/lw/jg/planning_fallacy/ Planning Fallacy]
*[http://lesswrong.com/lw/rj/surface_analogies_and_deep_causes/ Surface Analogies and Deep Causes]]
*[http://lesswrong.com/lw/rj/surface_analogies_and_deep_causes/ Surface Analogies and Deep Causes]
==See also==
==See also==

Latest revision as of 06:25, 17 November 2009

Wikipedia has an article about

It always takes longer than you expect, even when you take into account Hofstadter's Law.

A common cognitive bias resulting in predicting absurdly short timeframes for planned projects, famously observed with, among other projects, the Sydney Opera House, completed ten years late and a hundred million dollars overbudget.

Symptomatic of the Planning Fallacy is an assumption of a best-case scenario; people plan as if everything will go smoothly, as hoped for, with no unexpected delays. In practice, this is typically not the case, and delays quickly mount.

The bias also seems to be related to taking an "inside", detail-oriented view of the project to be planned; studies show that the more detailed a plan is, the more optimistically inaccurate it is likely to be.

Debiasing techniques

When possible, take the outside view. Avoid estimating the time for a project by adding time estimates for sub-tasks; instead, look for previously completed projects of similar type and scale, and base the estimate on how long those other projects took.

Blog posts

See also