Downscoping Under Pressure: II

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 sothe 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 issue in this series   Top    Next Issue

Projects 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

Your comments are welcome

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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

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 Trap of Beautiful Language

As we assess the validity of others' statements, we risk making a characteristically human error — we confuse the beauty of their language with the reliability of its meaning. We're easily thrown off by alliteration, anaphora, epistrophe, and chiasmus.

Some Perils of Reverse Scheduling

Especially when time is tight, project sponsors sometimes ask their project managers to produce "reverse schedules." They want to know what would have to be done by when to complete their projects "on time." It's a risky process that produces aggressive schedules.

Be Choosier About Job Offers: I

A serious error some job seekers make is accepting an offer that isn't actually a good fit. We make this mistake for a variety of reasons, including hating the job-search process, desperation, and wishful thinking. How can we avoid the error?

Unrecognized Bullying: III

Much workplace bullying goes unrecognized because of cognitive biases that can cause targets, perpetrators, bystanders, and supervisors of perpetrators not to notice bullying. The Halo Effect and the Horn Effect are two of these biases.

The Risk Planning Fallacy

The planning fallacy is a cognitive bias that causes underestimates of cost, time required, and risks for projects. Analogously, I propose a risk planning fallacy that causes underestimates of probabilities and impacts of risk events.

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

Forthcoming issues of Point Lookout

Coming December 11: White Water Rafting as a Metaphor for Group Development

Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.

And on December 18: Subgrouping and Conway's Law

When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

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