Scope Creep and the Planning Fallacy
by Rick Brenner
Much is known about scope creep, but it nevertheless occurs with such alarming frequency that in some organizations, it's a certainty. Perhaps what keeps us from controlling it better is that its causes can't be addressed with management methodology. Its causes might be, in part, psychological.
A visual illusion. While staring at the dot in the center of the image, move your head forward and back. You'll see the two rings of quadrilaterals rotate in opposite directions. They don't actually rotate at all, much less in opposite directions, but your visual system tells you that they do. Even after you're aware that this is an illusion, you can't make the illusion "go away." That is also the hallmark of cognitive biases. Even when we're aware of their effects, we can't manage to exercise unbiased judgments. To avoid the effects of a cognitive bias that affects personal judgment in a given situation, we must recruit the assistance of someone (or several someones) who aren't in that situation, and who thus aren't subject to that cognitive bias. Of course, because they could be subject to some other cognitive bias or biases, designing bias-avoidance procedures can be tricky. Image courtesy U.S. National Institute of Environmental Health Sciences.
Google "scope creep" and you get over half a million hits. Mission creep gets over three million. Feature creep gets over 18 million. That's pretty good for a technical concept, even if it isn't quite "miley" territory (115 million). The concept is known widely enough that anyone with project involvement has probably had first-hand experience with scope creep.
If we know so much about scope creep, why haven't we eliminated it? One simple possible answer: Whatever techniques we're using probably aren't working. Maybe the explanation is that we're psychologically challenged — that is, we, as humans, have a limited ability to detect scope creep, or to acknowledge that it's happening. If that's the case, a reasonable place to search for mechanisms to explain its prevalence is the growing body of knowledge about cognitive biases.
A cognitive bias is the tendency to make systematic errors of judgment based on thought-related factors rather than evidence. For example, a bias known as self-serving bias causes us to tend to attribute our successes to our own capabilities, and our failures to situational factors. An example of this bias is the "outside agitators" theory of civil disorder.
Cognitive biases offer an enticing possible explanation for the prevalence of scope creep despite our awareness of it, because "erroneous intuitions resemble visual illusions in an important respect: the error remains compelling even when one is fully aware of its nature." [Kahneman 1977] Let's consider one example of how a cognitive bias can make scope creep more likely.
In their 1977 report, Kahneman and Tversky identified one particular cognitive bias, the planning fallacy, which afflicts planners. They The planning fallacy can lead to
scope creep because underestimates
of cost and schedule can lead
decision makers to feel that
they have time and resources
that don't actually existdiscuss two types of information used by planners. Singular information is specific to the case at hand; distributional information is drawn from similar past efforts. The planning fallacy is the tendency of planners to pay too little attention to distributional evidence and too much to singular evidence, even when the singular evidence is scanty or questionable. Failing to harvest lessons from the distributional evidence, which is inherently more diverse than singular evidence, the planners tend to underestimate cost and schedule.
But because the planning fallacy leads to underestimates of cost and schedule, it can also lead to scope creep. Underestimates can lead decision makers to feel that they have time and resources that don't actually exist: "If we can get the job done so easily, it won't hurt to append this piece or that."
Accuracy in cost and schedule estimates thus deters scope creep. We can enhance the accuracy of estimates by basing them not on singular data alone, but instead on historical data regarding organizational performance for efforts of similar kind and scale. And we can require planners who elect not to exploit distributional evidence in developing their estimates to explain why they made that choice.
In coming issues we'll examine other cognitive biases that can contribute to scope creep. Next in this series Top Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. Order Now!
Your comments are welcome
Would you like to see your comments posted here? Send me your comments by email
, or by Web form
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful,
and that you'll consider recommending it to a friend
Point Lookout is a free weekly email newsletter. Browse the archive
of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout,
as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in,
anonymously if you like, and I'll give you my two cents.
More articles on Project Management
- Restarting Projects
- When a project gets off track, we sometimes cancel it. But since canceling projects takes a lot of courage, we look for ways to save them if we can. Often, things do turn out OK, and at other times they don't. There's a third choice, between pressing on with a project and canceling it. We can restart.
- Declaring Condition Red
- High-performance teams have customary ways of working together that suit them, their organizations, and their work. But when emergencies happen, operating in business-as-usual mode damages teams — and the relationships between their people — permanently. To avoid this, train for emergencies.
- Project Improvisation Fundamentals
- Project plans are useful — to a point. Every plan I've ever seen eventually has problems when it contacts reality. At that point, we replan or improvise. But improvisation is an art form. Here's Part I of a set of tips for mastering project improvisation.
- Project Improvisation and Risk Management
- When reality trips up our project plans, we improvise or we replan. When we do, we create new risks and render our old risk plans obsolete. Here are some suggestions for managing risks when we improvise.
- How to Make Good Guesses: Tactics
- Making good guesses probably does take talent to be among the first rank of those who make guesses. But being in the second rank is pretty good, too, and we can learn how to do that. Here are some tactics for guessing.
See also Project Management and Emotions at Work for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout
are available in six ebooks:
Reprinting this article
Are you a writer, editor or publisher on deadline?
Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: The Power of Agile Development
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:
- The Politics of Meetings for People Who Hate Politics
- There's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here's an upcoming date for this program:
- Managing Virtual Meetings for Real Results
- Leading or participating in virtual meetings — teleconferences, Web conferences, video conferences, and more — is challenging. Miscommunications, misunderstandings, distractions, politics, and interpersonal conflict all thrive in the typical environment of the virtual team. We'll inventory the challenges virtual meeting leaders and participants face, and provide tools for anticipating and addressing them. The focus of this program is practical — attendees will learn concrete techniques for preventing and dealing with the problems that arise in virtual meetings. Read more about this program. Here's an upcoming date for this program:
- Organizational Politics for People Who Hate Politics
- Have you ever felt powerless to implement an important new idea? Have you ever been "blind-sided" at a meeting? Have you ever lost two good employees because you could find no way to keep them from attacking each other? These are some of the issues of organizational politics. Many of us have become enmeshed in them from time to time, but we've also known some people who seem to be able to engage and prosper. How is that done? We'll inventory the challenges of organizational politics, and provide tools for anticipating and addressing them. The focus of this program is practical — attendees learn concrete techniques for dealing with the problems that arise in workplace politics, while keeping their integrity intact. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: Lessons in Risk Management for Leaders
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders and project managers, the story is fascinating. We'll use the history of this event to explore lessons in risk management and its application to organizational efforts. A fascinating and refreshing look at risk management from the vantage point of history. Read more about this program. Here are some upcoming dates for this program:
- New York Marriott Downtown, 85 West Street at Albany Street, New York, NY 10006: May 22, Breakfast Seminar, IT Metrics and Productivity Institute Conference Series. Register now.
- Toronto Marriott Downtown Eaton Centre Hotel, 525 Bay Street, Toronto, Ontario, Canada M5G2L2: June 5, Breakfast Seminar, IT Metrics and Productivity Institute Conference Series.
- Boston Marriott Newton, 2345 Commonwealth Avenue, Newton, MA 02466: June 26, Breakfast Seminar, IT Metrics and Productivity Institute Conference Series.
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program: