Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 22, Issue 40;   October 12, 2022: Downscoping Under Pressure: II

Downscoping Under Pressure: II

by

We sometimes "downscope" projects to bring them back on budget and schedule when they're headed for overruns. Downscoping doesn't always work. Cognitive biases like the sunk cost effect and confirmation bias can distort decisions about how to downscope.
A hummingbird feeding on the nectar of a flower

A hummingbird feeding on the nectar of a flower. If we regard the "design" of the hummingbird as an engineering problem, it provides a fascinating example of downscoping. Birds, generally, can fly, hop, walk, hover, perch, and move sideways while perched. Over the course of their evolution, hummingbirds have become expert at hovering, presumably to facilitate their nectar gathering. Since hovering requires so much energy, low weight is an important advantage. But legs sturdy enough to support hopping and walking would have increased their weight, making hovering more difficult. And so, hummingbirds have downscoped their design to exclude hopping and walking. That's right: hummingbirds can't hop and they can't walk. Photo courtesy Natural Resources Conservation Service, U.S. Department of Agriculture.

In the previous post I briefly explored the use of downscoping in the project context, both as a tool for controlling budgets and schedules, and as a means of inflicting damage on one's political rivals. Although downscoping can be effectively abused for political purposes, there are still other reasons to question its effectiveness in controlling projects.

The fundamental limitations of downscoping as a project control measure arise from the difficulty of managing the decision-making processes used to determine which objectives to cut or defer and how to do so. Below are two examples of the effect of cognitive biases on downscoping decision-making.

The sunk cost effect

To investors, The fundamental limitations of downscoping
arise from the difficulty of managing the
decision-making processes used to
determine which objectives to cut
or defer and how to do so
the term sunk cost denotes costs already incurred and not recoverable. The sunk cost effect [Staw 1976] is a cognitive bias that tends to make us unwilling to terminate an effort. Our unwillingness arises largely from the difficulty of accepting failure, even when continuing the effort would only lead to greater losses. The sunk cost effect thus makes us unwilling to downscope our projects. We then continue to pursue unattainable objectives. But the sunk cost effect is even more insidious than that.

When we do decide to downscope, the sunk cost effect also compels us to make unwise choices of project elements to cut. Suppose a project is in trouble, and suppose we decide to downscope to address that trouble. The sunk cost effect can lead us to designate for cancellation those parts of the project in which we have the least invested. Instead, we would often do better to focus cuts on those parts of the project that are least justified in terms of business objectives.

At and above the scale of entire projects, portfolios, and programs, the situation is even more troubling. At these scales, downscoping amounts to project cancellation. The sunk cost effect causes us to prefer to cancel those projects in which we have invested least, all other things being equal, instead of cancelling the projects that have the least compelling business purpose. In this way, the sunk cost effect distorts business objectives when downscoping occurs under pressure.

Biased cost estimation

When we decide to abandon a project objective, there is a risk that the project elements so far constructed might include "anticipatory artifacts" whose sole purpose was support for the objective we've now decided to abandon. To the extent that the downscoping decision is based on budget or schedule considerations, we must consider the cost of two options. The "As-Is" option leaves these anticipatory artifacts largely in place, making adjustments only as necessary for supporting the surviving project objectives. The second option, "Cleaned-Up," removes all traces of anticipatory artifacts intended solely to support the soon-to-be-abandoned objectives.

For example, let's suppose that one of the objectives to be abandoned is an ability to support languages that use the Cyrillic alphabet, and that once this goal is removed, all supported languages will use only the Roman alphabet. In the As-Is option, the machinery for supporting multiple alphabets remains in place. The machinery is in place, but it is never invoked. We might even have a copy of the Cyrillic alphabet in the product. In the Cleaned-Up option, by contrast, we remove all evidence that we ever intended to support the Cyrillic alphabet.

But if we downscoped to save money and time, we must consider costs and schedule burdens associated with both options. To compare As-Is and Cleaned-Up we must estimate the costs of both. The two options differ, of course. As-Is has a higher future burden because of the technical debt associated with leaving in place the anticipatory artifacts that support the abandoned objective. Cleaned-Up has a higher immediate burden because of the costs and time associated with removing the anticipatory artifacts that support the abandoned objective.

Nearly all cases of downscoping that I'm aware of use a mix of both approaches — both As-Is and Cleaned-Up — but they clearly skew toward the As-Is option. One reason for the skew is the need to estimate As-Is and Cleaned-Up costs and schedules. And those estimates are subject to confirmation bias, which favors As-Is over Cleaned-Up. The result is that downscoping under pressure generally increases the burden of technical debt, which leaves the product with a higher maintenance cost profile for the indefinite future.

The role of project governance

Perhaps the most important factor limiting the effectiveness of downscoping under pressure is inadequate governance. Governance bodies that approve downscoped plans must ensure that the plans were devised using processes that mitigate the risk of decision distortion from political agendas and from cognitive biases such as the sunk cost effect and confirmation bias.

The urge to approve downscoping plans can be overpowering for everyone concerned. Governance teams are the last defense against unrealistic downscoping cost and schedule estimates. They would do a great service by requiring development of independent, "blind," estimates of cost and schedule for all options, including those rejected during the decision process.

Last words

These two posts have focused on the process of downscoping in project management. But the process is also used in other contexts. For example, one can view compromise in negotiation as a form of downscoping, in which the negotiation partners agree to limit their objectives as a technique for reaching mutual agreement. Much of the discussion in these two posts could carry over analogously in that context. Indeed, whenever we decide to alter the objectives of any kind of effort, especially under pressure, the observations contained in these two posts could prove applicable. First in this series  Go to top Top  Next issue: Bullying by Proxy: I  Next Issue

How to Spot a Troubled Project Before the Trouble StartsProjects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. It helps readers learn the subtle cues that indicate that a project is at risk for wreckage in time to do something about it. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . Order Now! .

Footnotes

[Staw 1976]
Barry M. Staw. "Knee-deep in the Big Muddy: A Study of Escalating Commitment to a Chosen Course of Action," Organizational Behavior and Human Performance 16:1 (1976), 27-44. Back

Your comments are welcome

Would you like to see your comments posted here? rbrenZLkFdSHmlHvCaSsuner@ChacbnsTPttsdDaRAswloCanyon.comSend 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.

Related articles

More articles on Cognitive Biases at Work:

The Japanese battleship Yamato during machinery trials 20 October 1941The Focusing Illusion in Organizations
The judgments we make at work, like the judgments we make elsewhere in life, are subject to human fallibility in the form of cognitive biases. One of these is the Focusing Illusion. Here are some examples to watch for.
A tire reef off the coast of Fort Lauderdale, FloridaManaging Hindsight Bias Risk
Performance appraisal practices and project retrospectives both rely on evaluating performance after outcomes are known. Unfortunately, a well-known bias — hindsight bias — can limit the effectiveness of many organizational processes, including both performance appraisal and project retrospectives.
The Bloomingdale's store in Stamford, Connecticut in January 1955Why Scope Expands: I
Scope creep is depressingly familiar. Its anti-partner, spontaneous and stealthy scope contraction, has no accepted name, and is rarely seen. Why?
An abandoned railwayPerfectionism and Avoidance
Avoiding tasks we regard as unpleasant, boring, or intimidating is a pattern known as procrastination. Perfectionism is another pattern. The interplay between the two makes intervention a bit tricky.
Braided streams in Grewingk Glacier RiverRisk Acceptance: One Path
When a project team decides to accept a risk, and when their project eventually experiences that risk, a natural question arises: What were they thinking? Cognitive biases, other psychological phenomena, and organizational dysfunction all can play roles.

See also Cognitive Biases at Work and Critical Thinking at Work for more related articles.

Forthcoming issues of Point Lookout

A form of off road driving also known as mud boggingComing November 30: Avoiding Speed Bumps: II
Many of the difficulties we encounter when working together don't create long-term harm, but they do cause delays, confusion, and frustration. Here's Part II of a little catalog of tactics for avoiding speed bumps. Available here and by RSS on November 30.
Tuckman's stages of group developmentAnd on December 7: Reaching Agreements in Technological Contexts
Reaching consensus in technological contexts presents special challenges. Problems can arise from interactions between the technological elements of the issue at hand, and the social dynamics of the group addressing that issue. Here are three examples. Available here and by RSS on December 7.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenZLkFdSHmlHvCaSsuner@ChacbnsTPttsdDaRAswloCanyon.com or (650) 787-6475, 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-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.