Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 16, Issue 0;   July 20, 2016 The Risks of Too Many Projects: I

The Risks of Too Many Projects: I

by

Some organizations try to run too many development projects at once. Whether developing new offerings, or working to improve the organization itself, taking on too many projects can defocus the organization and depress performance.
Rapids in a northern stream

Rapids in a northern stream. Rapids occur because the stream flow is too great for the geometry and slope of the channel. In such conditions, the flow can actually alter the channel itself. At lower volumes, the stream would flow more "gently" with less turbulence. Something analogous happens in organizations that try to push too much "production" through their systems. Turbulence breaks out, in the form of unpredictable and unanticipated events, which makes managing the organization more difficult, and which can also damage the organization itself. By reducing production goals, the organization becomes more manageable, requiring less effort from management per unit of production.

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 events
usually 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.  The Risks of Too Many Projects: II Next issue in this series  Go to top Top  Next issue: The Risks of Too Many Projects: II  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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

Comprehensive list of all citations from all editions of Point Lookout
[Hofstadter 1989]
Douglas R. Hofstadter. Gödel, Escher, Bach: An Eternal Golden Braid. New York: Vintage Books, 1989. Order from Amazon.com. Back

Your comments are welcome

Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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:

A cup of coffeeHow to Procrastinate
You probably know many techniques for procrastinating, and use them regularly, but vociferously deny doing so. That's what makes this such a delicate subject that I've been delaying writing this article. Well, those days are over.
The Lincoln Memorial at sunriseOrganizational Loss: Searching Behavior
When organizations suffer painful losses, their responses can sometimes be destructive, further harming the organization and its people. Here are some typical patterns of destructive responses to organizational loss.
One site auditing a virtual presentationVirtual Presentations
Modern team efforts almost certainly involve teleconferences, and many teleconferences include presentations, often augmented with video or graphics. Delivering these virtual presentations effectively requires an approach tailored to the medium.
Then-Capt. Elwood R. Quesada who became commanding general of the 9th Fighter Command in operation OverlordCommunication Refactoring in Organizations
Inadequate communication between units of large organizations is one factor that maintains the dysfunction of "silo" structures in large organizations, limiting their ability to act coherently. Communication refactoring can help large organizations to see themselves as wholes.
C. Northcote Parkinson in 1961Meeting Troubles: Collaboration
In some meetings, we collaborate not in reaching objectives, but in preventing our doing so. Here are three examples of this pattern.

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

Forthcoming issues of Point Lookout

A garden sundialComing September 24: Time Is Not a Resource
In the project management community, it's often said that time is the most precious resource. Although time is indeed precious, to regard it as a resource — like finance, equipment, or people — can be a dangerous mistake. Time is not a resource. Available here and by RSS on September 24.
An owl of undetermined speciesAnd on October 1: On the Risks of Obscuring Ignorance
A common dilemma in knowledge-based organizations: ask for an explanation, or "fake it" until you can somehow figure it out. The choice between admitting your own ignorance or obscuring it can be a difficult one. It has consequences for both the choice-maker and the organization. Available here and by RSS on October 1.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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 Bluesky, or share a post 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.