The Cheapest Way to Run a Project Is with Enough Resources

Boston's Big Dig, the largest highway project in U.S. history, was originally projected to cost about $2 billion. The price now is over $14 billion. I don't know why they're over budget, but I do know that there has been intense pressure to hold costs down. Maybe part of their problem is the pressure to reduce costs.

Since the need to cut costs suggests that earlier estimates were off, why do we believe the new estimates? They're usually made under extreme time pressure, and with obvious bias. They might even be worse than the estimates they replace.

Yet, we do it and we do it again. Whenever we cut budgets, we risk cutting too much. And then we must deal with a hard truth: if we cut too much, the project will likely cost even more than if we hadn't cut at all.

When we cut too much, new mechanisms — many invisible — kick in, and all are beyond the control of project management. Uncontrolled processes lead to uncontrolled costs, and that's why cutting too much raises costs. Some examples:

Wishing

Responding to the call for cuts, people re-estimate their work, knowing that only the "right answers" can save their pieces of the project. Unaware, they bias their estimates. Overruns are inevitable.

Bootlegging

When we charge time to one project and work on another, or when we "borrow" equipment, we're bootlegging. It's widespread, and it's completely off the books.

Hoarding

Excessive budget
cuts encourage
"underground" behavior,
which is hard
to control

If we believe that we won't gain approval for additional staff, we might be tempted to keep some people we have, even when we don't really need them, because we doubt that we can get them back when we do need them again. So when money is tight, we find some people sitting around.

Bingeing and purging

When an organization goes through a sequence of "freezes," it inevitably goes through a matching sequence of thaws. During thaws we grab whatever we can. Often, this grab goes beyond satisfying backlogged needs, and becomes a true binge. Like squirrels burying acorns, we acquire what we can whether we need it or not.

Deferring

When budgets are tight, we sometimes defer addressing problems. For example, if a project is late, we shorten testing. This defers discovery of problems, often until after the product ships, when resolving the problems is even more expensive. The project cost is reduced, but the cost to the enterprise climbs dramatically.

Find out if any of this stuff is happening in your organization. If it's increasing, perhaps you're trying to run projects with budgets that are too small.  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! .

One symptom of resource starvation is the urge to make every effort "count" towards the ultimate deliverable. For a discussion of the downside of this approach, see "Trying to Do It Right the First Time Isn't Always Best," Point Lookout for March 14, 2007.

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.

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 Project Management:

TINOs: Teams in Name Only

Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.

Unnecessary Boring Work: I

Work can be boring. Some of us must endure the occasional boring task, but for many, everything about work is boring. It doesn't have to be this way.

Managing Wishful Thinking Risk

When things go wrong, and we look back at how we got there, we must sometimes admit to wishful thinking. Here's a framework for managing the risk of wishful thinking.

Yet More Obstacles to Finding the Reasons Why

Part III of our catalog of obstacles encountered in retrospectives, when we try to uncover why we succeeded — or failed.

Missing the Obvious: I

At times, when the unexpected occurs, we recognize with hindsight that the unexpected could have been expected. How do we miss the obvious? What's happening when we do?

See also Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming October 23: Power Distance and Teams

One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.

And on October 30: Power Distance and Risk

Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: Lessons in Leadership

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, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.

Here's a date for this program:

• Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
   

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.