How Big Things Get Done
Bent Flyvbjerg & Dan Gardner · 2023
Editorial rating
- Evidence
- 9/10
- Actionability
- 9/10
- Originality
- 8/10
The thesis
Big projects fail less from bad luck than from predictable errors made before execution begins. Plan through testing and outside data, then deliver quickly with repeatable modules.
Who this is for
Project leaders estimating a major transformation, executives approving capital investments, consultants scoping complex implementations, and homeowners about to discover that a renovation is also a project.
My favorite quote
Think slow, act fast: That's the secret of success.
Why it matters
The sentence separates patient learning from slow delivery, two activities that organizations routinely confuse.
Do this
Before advancing your current project, name one assumption you can test cheaply before real execution begins.
Start here
Use reference class forecasting before trusting your project plan. Find a group of genuinely similar completed projects, calculate what normally happened to their costs and schedules, and treat that outside view as your baseline before adding details unique to your case.
Critical summary
Bent Flyvbjerg spent decades studying why ambitious projects disappoint, while journalist Dan Gardner turns that research into a readable operating manual. Their database covers more than 16,000 projects, and its headline result is brutal: only 8.5 percent were delivered on both budget and schedule, while roughly 0.5 percent also produced the promised benefits. The book argues that failure begins with the commitment fallacy. Leaders fall in love with an idea, announce it too early, and then use planning to justify a decision already made. Optimism bias understates difficulty, strategic misrepresentation keeps approval numbers attractive, and every month of slow execution creates more opportunities for inflation, political change, accidents, and small problems to combine. The alternative is to think slow and act fast. Start by defining the project's real purpose, study comparable outcomes through reference class forecasting, and reduce unknowns through experience and experiments. Pixar storyboards films repeatedly before expensive production, while Frank Gehry's teams use models and simulations to expose design problems early. Once execution starts, move quickly and build with modular, repeatable units whenever possible. A solar farm can add standardized panels one by one, while a first-of-a-kind nuclear plant concentrates too much novelty in one enormous bet.
What it gets right
- Replaces confident internal estimates with base rates from comparable completed projects
- Shows why early testing is not hesitation but the fastest route to reliable execution
- Connects modularity with learning curves, repetition, lower risk, and scalable delivery
What it overstates or misses
- The broad project database combines very different sectors, governance systems, and definitions of success
- Modularity is powerful but cannot fully solve projects dominated by site conditions, politics, or genuinely novel science
- The book gives less attention to power, procurement incentives, and organizations that benefit from optimistic forecasts
The evidence is unusually substantial for a management book, although the memorable case studies sometimes carry more explanatory weight than the statistics can support on their own. Reference class forecasting and modularity are the durable ideas; some of the surrounding project stories mainly make them easier to remember. The verdict: required reading before anyone approves a budget with more than one comma in it.
Key concepts
The Iron Law of Megaprojects
Major projects repeatedly arrive over budget, over time, and under benefits, so assume failure is normal until your process proves otherwise.
Commitment Fallacy
Publicly committing before uncertainty is reduced turns later analysis into justification; delay irreversible promises until alternatives have been tested.
Reference Class Forecasting
Estimate from the actual outcomes of comparable projects rather than the polished logic of your own plan.
Think Slow, Act Fast
Spend time experimenting and rehearsing before delivery, then shorten execution to reduce exposure to unexpected events.
Modularity
Build from small repeatable components so each unit improves the next and one failure cannot sink the entire undertaking.
Core insights
-
Your Project Is Less Unique Than You Think
The details may differ, but cost and schedule behavior usually resembles a reference class that can correct inside-view optimism.
-
Planning Means Testing
A document full of dates is not a plan unless its critical assumptions have survived models, prototypes, simulations, or rehearsal.
-
Long Execution Is a Risk Multiplier
Every additional month gives inflation, politics, staff turnover, and random events more chances to damage delivery.
-
Small Units Create Big Advantages
Repetition improves speed and quality while allowing useful output before the entire project is complete.
-
Ask Why Before Asking How
A precise purpose prevents technically impressive teams from efficiently delivering the wrong thing.
Implementation steps
Today
- Write the project's purpose in one sentence that describes the benefit, not the asset or software being delivered.
- List the three assumptions most capable of destroying the budget, schedule, or expected benefit.
This week
- Find at least five comparable completed projects and record their original estimate, final cost, planned duration, and actual duration.
- Design one cheap experiment, prototype, or rehearsal that tests the riskiest assumption before execution expands.
This month
- Rebuild the estimate using the reference class median and an explicit contingency rather than the team's preferred scenario.
- Divide delivery into the smallest repeatable modules that can produce learning or value independently.
Ongoing
- Track forecast accuracy at every milestone and update the estimate when evidence changes instead of defending the original number.
- Keep the planning phase psychologically open and the execution phase operationally fast.
Suggested 30-day practice plan
An editorial application plan created by Monolithic Vault - an interpretation of the book's ideas, not part of the original book.
- Day 1
Rewrite the project purpose and identify the decision that has already been treated as irreversible.
- Day 3
Build a first reference class from comparable projects and calculate the median overrun.
- Day 7
Review the outside-view estimate with the sponsor before additional commitments are made.
- Day 14
Run a prototype, simulation, pilot, or premortem against the largest remaining uncertainty.
- Day 21
Redesign the work into repeatable modules with clear completion criteria and owners.
- Day 30
Approve or revise the project using tested assumptions, outside-view numbers, and a shorter execution window.
Free PDF summary
Take this analysis with you: a designed two-page field-notes sheet with the thesis, my favorite quote, the key concepts and core insights, and the full 30-day checklist. Print it or keep it - free, no signup.
Go deeper
If this analysis earned your attention, the full book goes further than any summary can. The original is always the primary source.