"Other Than That," It Was Okay
A cognitive bias in project planning where people systematically underestimate completion time and costs because they focus on internal project factors and neglect external uncertainties, a phenomenon called 'tunneling.' Even without incentives, planners are too narrow-minded to account for 'unknown unknowns,' leading to delays and overruns.
THE IDEA
"Other Than That," It Was Okay
We have used the story of the Sydney Opera House as a springboard for our discussion of prediction. We will now address another constant in human nature: a systematic error made by project planners, coming from a mixture of human nature, the complexity of the world, or the structure of organizations. In order to survive, institutions may need to give themselves and others the appearance of having a “vision.”
Plans fail because of what we have called tunneling, the neglect of sources of uncertainty outside the plan itself.
The typical scenario is as follows. Joe, a nonfiction writer, gets a book contract with a set final date for delivery two years from now. The topic is relatively easy: the authorized biography of the writer Salman Rushdie, for which Joe has compiled ample data. He has even tracked down Rushdie’s former girlfriends and is thrilled at the prospect of pleasant interviews. Two years later, minus, say, three months, he calls to explain to the publisher that he will be a little delayed. The publisher has seen this coming; he is used to authors being late. The publishing house now has cold feet because the subject has unexpectedly faded from public attention—the firm projected that interest in Rushdie would remain high, but attention has faded, seemingly because the Iranians, for some reason, lost interest in killing him.
Let’s look at the source of the biographer’s underestimation of the time for completion. He projected his own schedule, but he tunneled, as he did not forecast that some “external” events would emerge to slow him down. Among these external events were the disasters on September 11, 2001, which set him back several months; trips to Minnesota to assist his ailing mother (who eventually recovered); and many more, like a broken engagement (though not with Rushdie’s ex-girlfriend). “Other than that,” it was all within his plan; his own work did not stray the least from schedule. He does not feel responsible for his failure.*
The unexpected has a one-sided effect with projects. Consider the track records of builders, paper writers, and contractors. The unexpected almost always pushes in a single direction: higher costs and a longer time to completion. On very rare occasions, as with the Empire State Building, you get the opposite: shorter completion and lower costs—these occasions are becoming truly exceptional nowadays.
We can run experiments and test for repeatability to verify if such errors in projection are part of human nature. Researchers have tested how students estimate the time needed to complete their projects. In one representative test, they broke a group into two varieties, optimistic and pessimistic. Optimistic students promised twenty-six days; the pessimistic ones forty-seven days. The average actual time to completion turned out to be fifty-six days.
The example of Joe the writer is not acute. I selected it because it concerns a repeatable, routine task—for such tasks our planning errors are milder. With projects of great novelty, such as a military invasion, an all-out war, or something entirely new, errors explode upward. In fact, the more routine the task, the better you learn to forecast. But there is always something nonroutine in our modern environment.
There may be incentives for people to promise shorter completion dates—in order to win the book contract or in order for the builder to get your down payment and use it for his upcoming trip to Antigua. But the planning problem exists even where there is no incentive to underestimate the duration (or the costs) of the task. As I said earlier, we are too narrow-minded a species to consider the possibility of events straying from our mental projections, but furthermore, we are too focused on matters internal to the project to take into account external uncertainty, the “unknown unknown,” so to speak, the contents of the unread books.
There is also the nerd effect, which stems from the mental elimination of off-model risks, or focusing on what you know. You view the world from within a model. Consider that most delays and cost overruns arise from unexpected elements that did not enter into the plan—that is, they lay outside the model at hand—such as strikes, electricity shortages, accidents, bad weather, or rumors of Martian invasions. These small Black Swans that threaten to hamper our projects do not seem to be taken into account. They are too abstract—we don’t know how they look and cannot talk about them intelligently.
We cannot truly plan, because we do not understand the future—but this is not necessarily bad news. We could plan while bearing in mind such limitations. It just takes guts.
When to use it
Estimating time for a software development project: developers often focus on coding tasks but ignore potential server outages, sick days, or requirement changes.
Planning a wedding: couples budget for venue and catering but forget unforeseen costs like weather backups or vendor cancellations.
Writing a thesis: students plan research and writing but overlook delays in IRB approval or finding participants.
Construction projects: contractors plan materials and labor but may not account for strikes, weather, or supply chain disruptions.
FROM THEORY TO EVERYDAY LIFE
In practice
Joe the Biographer's Book Deadline
Joe, a nonfiction writer, gets a book contract with a delivery date two years away. He plans based on internal factors – interviews and writing – but fails to account for external events like 9/11, his mother's illness, and a broken engagement. As a result, he is delayed despite his own work staying on schedule. Joe tunneled – he neglected sources of uncertainty outside the plan.
Student Project Time Estimation
Students were asked to estimate how long their projects would take. Optimistic students estimated 26 days, pessimistic 47 days, but the actual average was 56 days. Even participants trying to be realistic systematically underestimated the time needed.
A MOMENT TO REFLECT
Put it to work.
Think of a recent project you planned. What external uncertainties did you overlook?
How can you incorporate 'unknown unknowns' into your project timelines?
Why do you think even pessimistic estimates often fall short?
CONTINUE THE CONVERSATION
Source texts
- The Black Swan The Impact of the Highly Improbable With a new section On Robustness and Fragility (Nassim Nicholas Taleb)