Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 16, Issue 29;   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[Hofstadter 1989], or power politics, to name a few common mechanisms.
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.  Next 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

[Hofstadter 1989]
Hofstadter's Law: "It always takes longer than you expect, even when you take into account Hofstadter's Law." See Douglas 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? rbrenqNSQNbEohbuBYZKoner@ChacSnsPBVqbJhtOHuraoCanyon.comSend me your comments by email, or by Web form.

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

Senator Mark Warner (Democrat of Virginia) meets with mayorsDiscussus Interruptus
You're chairing a meeting, and to your dismay, things get out of hand. People interrupt each other so often that nobody can complete a thought, and some people dominate the meeting. What can you do?
The damaged Apollo 13 Service Module, as seen from the command moduleHealthy Practices
Some organizational cultures are healthy; some aren't. How can you tell whether your organizational culture is healthy? Here are some indicators.
A senator rests on a cot in the Old Senate Chamber during a filibusterUntangling Tangled Threads
In energetic discussions, topics and subtopics get intertwined. The tangles can be frustrating. Here's a collection of techniques for minimizing tangles in complex discussions.
The deadline at Rock Island Prison during the U.S. Civil WarIrrational Deadlines
Some deadlines are so unrealistic that from the outset we know we'll never meet them. Yet we keep setting (and accepting) irrational deadlines. Why does this happen?
A particularly complicated but well-ordered utility poleThe Utility Pole Anti-Pattern: II
Complex organizational processes can delay action. They can set people against one other and prevent organizations from achieving their objectives. In this Part II of our examination of these complexities, we look into what keeps processes complicated, and how to deal with them.

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

Forthcoming issues of Point Lookout

The end of the line for a railroad trackComing May 30: Chronic Peer Interrupters: I
When making contributions to meeting discussions, we're sometimes interrupted. Often, the interruption is beneficial and saves time. But some people constantly interrupt their peers or near peers, disrespectfully, in a pattern that compromises meeting outcomes. How can we deal with chronic peer interrupters? Available here and by RSS on May 30.
Mohandas K. Ghandi, in the 1930sAnd on June 6: Chronic Peer Interrupters: II
People use a variety of tactics when they're interrupted while making contributions in meetings. Some tactics work well, while others carry risks of their own. Here's Part II of a little survey of those tactics. Available here and by RSS on June 6.

Coaching services

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

Public seminars

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople 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. Here's a date for this program:

Technical Debt Management: Making the Business Case
This Technical Debt Management: Making the Business Caseprogram outlines the steps necessary for deploying a program for rational management of technical debt. For many organizations, adopting a program for rationally managing technical debt entails organizational change. And unlike some organizational changes, this one touches almost everyone in the organization, because technical debt isn't merely a technical problem. Technical debt manifests itself in technological assets, to be sure, but its causes are rarely isolated to the behavior and decisions of engineers. We can't resolve the problem of chronically excessive levels of technical debt by changing the behavior of engineers alone. Technical debt is the symptom, not the problem. In this program we outline the essential elements of an effective business case for adopting a rational technical debt management program. But this business case, unlike many business cases, cannot be captured in a document. We must make the case not only at the leadership level of the organization, but also at the level of the individual contributor. Everyone must understand. Everyone must contribute. We explore five issues that make technical debt so difficult to manage, and develop five guidelines for designing technical debt management strategies for the modern enterprise. Read more about this program. Here's a date for this program:

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's a date for this program:

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople 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. Here's a date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ 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.