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? rbrenqzBohrFqXtZuhwOGner@ChacVeScbaNNRHggsgOeoCanyon.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:
- When Meetings Boil Over
- At any time, without warning, you can find yourself in a meeting that boils over. Sometimes tempers
rise, then voices rise, and then people yell and scream. What can a team do when meetings threaten to
boil over — and when they do?
- Status-Report as a Second Language
- Sometimes, the clichés the losing team's players feed to sports reporters can have hidden meaning.
So it is with Project Status Reports, especially for projects in trouble.
- If Only I Had Known: I
- Have you ever regretted saying something that you wouldn't have said if only you had known just one
more little fact? Yeah, me too. We all have. Here are some tips for dealing with this sticky situation.
- When the job market eases for job seekers, we often see increases in job shifting, as people who've
been biding their time make the jump. Typically, they're the people we most want to keep. How can we
reduce this source of turnover?
- Deciding to Change: Choosing
- When organizations decide to change what they do, the change sometimes requires that they change how
they make decisions, too. That part of the change is sometimes overlooked, in part, because it affects
most the people who make decisions. What can we do about this?
Forthcoming issues of Point Lookout
- Coming May 23: Narcissistic Behavior at Work: IX
- An arrogant demeanor is widely viewed as a hallmark of the narcissist. But truly narcissistic arrogance is off the charts. It's something beyond the merely annoying arrogance of a sometimes-obnoxious individual. What is narcissistic arrogance and how can we cope with it? Available here and by RSS on May 23.
- And on 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.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenAnRPPyyihEmlYKpBner@ChacygPOYCSqMrwDbqoToCanyon.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, 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
- Technical Debt Management: Making the Business Case
- This program
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:
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield,
Illinois 62701: June 12,
Monthly Meeting, Central
Illinois Chapter of the Project Management Institute. Register now.
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield, Illinois 62701: June 12, Monthly Meeting, Central Illinois Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: The Power of Agile Development
- 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. 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:
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227:
Monthly Meeting, Cincinnati
chapter of the International Institute of Business Analysis. Register now.
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. Register now.
- The Power Affect: How We Express Our Personal Power
- Many people 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.