The Risks of Too Many Projects: I

Many organizations are under pressure to increase revenue, to achieve or maintain market leadership, or to reach any of dozens of organizational goals. To respond, some launch initiatives they feel will meet the challenges they face. Often, they take on too much. Let's explore the consequences of so doing.

Strategic blur

If an organization is running only one project, strategic focus is assured. With each additional active project, the risk of loss of focus increases. The best-run organizations manage this risk by reviewing each new project for consistency with current strategy. Although waivers are granted now and then, they do maintain strategic focus — at first.

Inevitably, some projects stumble. They take longer than planned. In some cases, after the organization adopts a new high-level strategy, or amends the current strategy, some projects that were formerly consistent with organizational strategy no longer are, because the strategy on which they rested has migrated out from under them. Yet, we don't cancel these holdover projects, for various reasons: the sunk cost effect, Hofstadter's Law ("It always takes longer than you expect, even when you take into account Hofstadter's Law."), or power politics, to name a few common mechanisms. [Hofstadter 1989]

Executing the newly adopted or newly amended strategy usually requires chartering new projects. When holdover projects are already in place, portfolio bloat can develop, along with strategic blur, the opposite of strategic focus. Strategic blur also afflicts the organization's customers, who, upon examining the projected stream of offerings, might have even more difficulty discerning the organization's strategy than the company's leaders have expressing it.

Resource contention

Development projects require human, financial, and infrastructural resources. As active projects increase in number, their needs can sometimes collide, because resources might not be available on demand. For example, if we decide to hire all the people we need, bottlenecks might develop in the hiring and onboarding apparatus.

Resource sharing When organizations try to push
too much "production" through
their systems, turbulence breaks
out in the form of unpredictable
and unanticipated eventsusually resolves resource contention, but it can create problems of its own. For example, to share human resources (people), we assign them to multiple projects — two, three, five — I've known people who were managing more than 20 active projects. Daily life for people serving multiple projects can be a staccato stream of interruptions, messages sent and received through various media, and endless meetings.

In "Recovering Time: I," Point Lookout for February 23, 2005, I explored these conditions and their attendant high costs. Individual performance and output quality can suffer. Managing this risk with quiet hours and other techniques usually yields positive though disappointing results, because such strategies address the symptoms of the problem, rather than its cause. The primary cause: too many projects.

Rules of thumb regarding numbers of projects per capita are legion, and of limited value, because project work is too varied for such simplistic dogma. Determine a number of projects that works well enough for your organization, and strive to reduce it.

We'll continue next time, examining some less commonly considered risks of running too many projects.   Next 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!

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

How We Avoid Making Decisions

When an important item remains on our To-Do list for a long time, it's possible that we've found ways to avoid facing it. Some of the ways we do this are so clever that we may be unaware of them. Here's a collection of techniques we use to avoid engaging difficult problems.

Smart Bookshelves

If you like to browse in bookstores, you probably know the thrill of new ideas and new perspectives. When I find a book worth reading, I want to own it, and that's how it gets to my shelf. Here are some tips to help you read more of what you really want to read.

The Paradox of Confidence

Most of us interpret a confident manner as evidence of competence, and a hesitant manner as evidence of lesser ability. Recent research suggests that confidence and competence are inversely correlated. If so, our assessments of credibility and competence are thrown into question.

How We Waste Time: II

We're all pretty good at wasting time. We're also fairly certain we know when we're doing it. But we're much better at it than we know. Here's Part II of a little catalog of time wasters, emphasizing those that are outside — or mostly outside — our awareness.

How to Answer When You Don't Know How to Answer

People engaged in knowledge work must often respond to questions that test the limits of their knowledge, or the limits of everyone's knowledge. Responding effectively to such questions advances us all.

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

Forthcoming issues of Point Lookout

Coming 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.

And on February 5: On Shaking Things Up

Newcomers to work groups have three tasks: to meet and get to know incumbent group members; to gain their trust; and to learn about the group's task and how to contribute to accomplishing it. General skills are necessary, but specifics are most important. Available here and by RSS on February 5.

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