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 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 welcomeWould you like to see your comments posted here? rbrenYNSClUphBstVZsosner@ChacEzLJnRnIRnGWWWmQoCanyon.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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- Pygmalion Side Effects: Bowling a Strike
- Elise slowly walked back to her office, beaten. Her supervisor, Alton, had just given Elise her performance
review — her third consecutive "meets expectations." No point now to her strategy of
giving 120% to turn it all around. She is living a part of the Pygmalion Effect, and she's about to
experience the Pygmalion Side Effects.
- Poverty of Choice by Choice
- Sometimes our own desire not to have choices prevents us from finding creative solutions. Life
can be simpler (if less rich) when we have no choices to make. Why do we accept the same tired solutions,
and how can we tell when we're doing it?
- Patching Up the Cracks
- When things repeatedly "fall through the cracks," we're not doing the best we can. How can
we deal with the problem of repeatedly failing to do what we need to do? How can we patch up the cracks?
- Virtual Clutter: II
- Thorough de-cluttering at work involves more than organizing equipment and those piles of documents
that tend to accumulate so mysteriously. We must also address the countless non-physical entities that
make work life so complicated — the virtual clutter.
- Still More Things I've Learned Along the Way
- When I have an important insight, or when I'm taught a lesson, I write it down. Here's another batch
from my personal collection.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenSPambYCwIHITutXhner@ChacotjguVwSZHnWIvOQoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- 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. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.