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 —
- 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?
- 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 welcomeWould you like to see your comments posted here? rbrenogMhuqCxAnbfLvzbner@ChacigAthhhYwzZDgxshoCanyon.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.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
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 Project Management:
- See No Evil
- When teams share information among themselves, they have their best opportunity to reach peak performance.
And when some information is withheld within an elite group, the team faces unique risks.
- An Agenda for Agendas
- Most of us believe that the foundation of a well-run meeting is a well-formed agenda. What makes a "well-formed"
agenda? How can we write and manage agendas to make meetings successful?
- Long-Loop Conversations: Asking Questions
- In virtual or global teams, where remote collaboration is the rule, waiting for the answer to a simple
question can take a day or more. And when the response finally arrives, it's often just another question.
Here are some suggestions for framing questions that are clear enough to get answers quickly.
- The Retrospective Funding Problem
- If your organization regularly conducts project retrospectives, you're among the very fortunate. Many
organizations don't. But even among those that do, retrospectives are often underfunded, conducted by
amateurs, or too short. Often, key people "couldn't make it." We can do better than this.
What's stopping us?
- Joint Leadership Teams: Risks
- Some teams, business units, or enterprises are led not by individuals, but by joint leadership teams
of two or more. They face special risks that arise from the organizations that host them, from the teams
they lead, or from within the joint leadership team itself.
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming December 13: Contrary Indicators of Psychological Safety: I
- To take the risks that learning and practicing new ways require, we all need a sense that trial-and-error approaches are safe. Organizations seeking to improve processes would do well to begin by assessing their level of psychological safety. Available here and by RSS on December 13.
- And on December 20: Contrary Indicators of Psychological Safety: II
- When we begin using new tools or processes, we make mistakes. Practice is the cure, but practice can be scary if the grace period for early mistakes is too short. For teams adopting new methods, psychological safety is a fundamental component of success. Available here and by RSS on December 20.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenogMhuqCxAnbfLvzbner@ChacigAthhhYwzZDgxshoCanyon.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
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.