Only accepted work is recordedAboutGuidesContactSign in
CitePepCitePep
What Is the Planning Fallacy and Why Projects Always Run
Concepts Corrected & verified

What Is the Planning Fallacy and Why Projects Always Run

This is the CitePep accuracy record for “What Is the Planning Fallacy and Why Projects Always Run”, published by When Notes Fly. It lists every change experts checked and accepted on that page.

Published by When Notes Fly · View original ↗

The planning fallacy explains why projects consistently take longer and cost more than planners expect, and how reference class forecasting corrects it.

What has been corrected on this page?

Every accepted correction to this page is recorded with the exact change, so readers can see how the page improved over time.

  1. 12 July 2026 · corrected by Emir Baycan

    2 corrections applied: Sydney Opera House figures are Australian dollars, not pounds sterling | Kahneman reports the curriculum project was completed in about eight years, not ten

    Before
    (1) The Sydney Opera House, estimated at £7 million, cost £102 million. (2) they increased their estimate to eight years. The project ultimately took ten.
    After
    (1) The Sydney Opera House, estimated at about AU$7 million, cost about AU$102 million. (2) they increased their estimate to eight years. The project ultimately took eight.

    Why: Verified both corrections already correctly applied in the article body (AU$ currency for Sydney Opera House; 'took eight' for the curriculum project). No other mentions elsewhere in article. FAQ field checked, does not reference either fact. No changes needed.

    View the full record →

Who checked this page?

1 contributor has checked "What Is the Planning Fallacy and Why Projects Always Run" on When Notes Fly. Each name below links to that person's public CitePep profile, where every contribution they have made is listed with the exact change they proposed.