The Risks of Too Many Projects: II

When organizations commit themselves to too many projects simultaneously, they risk loss of strategic focus and encourage resource contention, as we saw last time. But those are just the most obvious problems. Here are three more.

Resource depletion

Some organizational resources must be available to all projects. Financial resources come to mind immediately. Projects need money, and the more projects we have, the more thinly we spread our financial resources. This applies not only to the financial resources needed for routine project execution, but also to reserves that must be available to cover adverse events.

Other resources have this same property. Consider just one example. To some degree, senior management must be aware of everything the organization does. If a project encounters trouble, senior management must be able to grasp the problem and respond to it effectively, even when multiple projects require their attention at once. The greater the number of projects underway, the more likely is the capacity of senior management to be saturated.

Many other classes of organizational resources have this property — they can be saturated unexpectedly when too many projects need them simultaneously.

Organizational "firestorm" frequency

When organizations run large numbers of projects simultaneously, some individuals serve more than one project. If one of the projects encounters difficulty, that project gets their attention, while the others go on hold.

We can grasp the dynamics of this configuration more easily using a "forest fire" metaphor. Think of a project portfolio as a forest, and project trouble as forest fire. When one part of the forest catches fire, the shared "resources" provide a means for that fire to spread. This happens because trouble in one project disrupts the carefully scheduled sharing of resources, propagating trouble to projects that share resources with the troubled project.

Reducing project numbers reduces resource sharing, which prevents trouble from propagating. If we can't reduce project numbers, we can at least try to isolate high-risk projects from others by dedicating resources to them.

Wheel re-invention

When many If we can't reduce project numbers,
we can at least try to isolate
high-risk projects from others
by dedicating resources to themprojects are active, similar or even identical problem solutions might be simultaneously underway. Indeed, it can be easier to solve a given problem than it would be to determine whether or not that problem is being solved elsewhere in the organization.

Duplicating productive effort is only one form of waste. Duplicating unproductive effort is another. When a team discovers that a particular approach is unworkable, announcing that it has just wasted significant resources is not necessarily in its interest, politically speaking. Uncovering this kind of information can be difficult in any case, but when many projects are active, duplication of wasted effort is both more likely to have occurred, and less likely to be exposed.

Running many projects simultaneously might seem sensible, but I hope I've raised some questions about its wisdom. If you aren't in a position to reduce the number of active projects in your organization, maybe you know someone who is.   First issue in this series   Top    Next Issue

Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

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 Personal, Team, and Organizational Effectiveness:

Take Regular Temperature Readings

Team interactions are unimaginably complex. To avoid misunderstandings, offenses, omissions, and mistaken suppositions, teams need open communications. But no one has a full picture of everything that's happening. The Temperature Reading is a tool for surfacing hidden and invisible information, puzzles, appreciations, frustrations, and feelings.

Email Antics: II

Nearly everyone complains that email is a time waster. Yet much of the problem results from our own actions. Here's Part II of a little catalog of things we do that help waste our time.

Mudfights

When we steer the discussion away from issues to attack the credibility, motives, or character of our debate partners, we often resort to a technique known as the ad hominem attack. It's unfair, it's unethical, and it leads to bad, expensive decisions that we'll probably regret.

Finding Work in Tough Times: Communications

Finding work in tough times entails presenting yourself to many people. You'll be conversing, interviewing, writing, presenting, and when you're finally successful, negotiating.

Why Don't They Believe Me?

When we want people to believe us, and they don't, it just might be a result of our own actions or demeanor. How does this happen?

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

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