Toxic Projects

Martin dejectedly handed the message to Jeri, who read it out loud: "You've been volunteered for Amethyst. You'll be working with Weldon and the architecture team." Amethyst was by now the tail wagging the organizational dog, and everyone understood that when it came to Amethyst, "volunteered" meant "indentured."

"Probably the best place to be, if you have to be on Amethyst," Jeri said, trying to console Martin.

"Yeah, right," said Martin, "like the southern Yukon in February."

Amethyst was a "Monster" project — one that gradually claims more and more organizational resources. Monster projects are one type of toxic project. Even when they're "on track," they harm the organization by consuming resources that are much better used elsewhere.

Here are some other kinds of toxic projects.

The Pet

The pet project is funded because its champion not only has the urge to play around with a favorite idea, but also the political clout to gather the resources for the needed toys. What's the cost of not using these resources productively?

The Turnover

Toxic projects
harm their organizations
even when — especially when —
they "succeed"

Some projects are so frustrating and deadly to the morale of the project team that they cause skilled and productive team members to leave the organization. What's the cost of turnover?

The Trap Door

This is a project that commits the organization to a path that severely limits its future strategic options. What's the cost of lost flexibility?

Seawater

People adrift at sea, dying of thirst and desperate, sometimes drink seawater. Organizations do something analogous — they fund projects that seem useful, but which actually threaten the organization. What's the cost of treatment once you realize you've been drinking seawater?

Why don't organizations just cancel toxic projects? Often people don't realize that the projects are toxic, because the accounting system masks their impact.

When we compute project costs, we sometimes understate certain organizational costs. For instance, a Turnover project creates organizational costs that aren't actually charged to the project, such as increased recruiting costs, delays in other projects, and depressed morale. If these costs are recognized at all, they appear as overhead, and they're distributed across all organizational activity using a "flat tax" system that allocates them to all projects in proportion to labor hours, management time, square feet or dollars spent.

But projects differ, and these costs vary by project. A toxic project creates more than its share of these costs, but the organization never realizes it.

What can we do? Decision makers can assess project toxicity by making a serious attempt to apportion organizational costs fairly. Computing these costs can be difficult, because it feels subjective, but almost any honest effort would be fairer than the flat tax system. Denying the reality of these costs doesn't eliminate them — they're real, they cannot be known exactly, and we must deal with them.  Top    Next Issue

The article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More

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 Project Management:

Make a Project Family Album

Like a traditional family album, a project family album has pictures of people, places, and events. It builds connections, helps tie the team together, and it can be as much fun to look through as it is to create.

Deep Trouble and Getting Deeper

Here's a catalog of actions people take when the projects they're leading are in deep trouble, and they're pretty sure there's no way out.

How to Get Out of Firefighting Mode: II

We know we're in firefighting mode when a new urgent problem disrupts our work on another urgent problem, and the new problem makes it impossible to use the solution we thought we had for some third problem we were also working on. Here's Part II of a set of suggestions for getting out of firefighting mode.

The Planning Fallacy and Self-Interest

A well-known cognitive bias, the planning fallacy, accounts for many unrealistic estimates of project cost and schedule. Overruns are common. But another cognitive bias, and organizational politics, combine with the planning fallacy to make a bad situation even worse.

Tuckman's Model and Joint Leadership Teams

Tuckman's model of the stages of group development, applied to Joint Leadership Teams, reveals characteristics of these teams that signal performance levels less than we hope for. Knowing what to avoid when we designate these teams is therefore useful.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on 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.

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