Nan pushed the door open, and she and Trish stepped out of the conference center into the morning air. On their first break from the off-site meeting, they hadn't quite yet relaxed from the pressure cooker that was the final stretch of Marigold, their latest project. It hadn't gone well, and they were all spending three days trying to figure out what happened.
"So what do you think?" Nan opened.
"I've been to off-sites before," said Trish. "But this is the first time I've felt hopeful that truth would come out."
Nan agreed. "Me too. I liked the bit about myths and fallacies."
Nan sat down on one of the plastic chairs. Trish sat too. "But knowing these fallacies," she asked, "won't we just get better at fooling ourselves? If we could get any better which I seriously doubt."
Nan smiled. "Well, I think his point was that by naming the fallacies, it gets harder to use them."
And Nan is right about that. By naming the fallacies, the patterns become obvious to everyone, which deters us from using them. Here's Part I of a little catalog of the fallacies of project management. For Part II, see "Nine Project Management Fallacies: II," Point Lookout for December 14, 2005.
Universal awarenessof common fallacies
deters us all
from using them
- The Fallacy of Positivism
- The Fallacy of Positivism holds that if we believe we can accomplish something, we're more likely to actually accomplish it; and inversely, if we express doubts about accomplishing something, we're less likely to execute it successfully.
- This fallacy is especially tempting to leaders who want to motivate reluctant teams to attempt (or keep trying to do) the impossible. They're using it as a tool of manipulation.
- All things being equal, it's probably helpful to have a positive attitude. But Truth is most important. Be positive when it's appropriate, and express doubts when they're real and relevant. Both staying positive and expressing doubt inappropriately can lead to catastrophe.
- The Bad Actor Fallacy
- If a team exhibits a repeated pattern of dysfunction, we commit the Bad Actor Fallacy when we assume that one single team member is the likely cause of the problem.
- Isolating the cause of a team problem to a single individual is tempting because it suggests that dealing with that individual can resolve the problem. No need for messy and expensive team interventions; no need for involving more than one person.
- While it's possible for a single individual to keep a team in a state of dysfunction, more typically many individuals contribute to team problems. Team performance is an attribute of the team's system, and the organization in which that team is embedded.
One more fallacy is perhaps most common: the Purity Fallacy, which holds that we are personally pure: we never use fallacies ourselves. We all use them, of course — we're human. The trick is to catch yourself when you do. Next issue 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 welcome
Would you like to see your comments posted here? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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.
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:
- Start a Project Nursery
- In a Project Nursery, professionals from across the entire organization collaborate to conceive of new
projects. When all organizational elements help decide which projects to investigate, the menu they
develop best suits organizational needs and capabilities.
- Unresponsive Suppliers: II
- When a project depends on external suppliers for some tasks and materials, supplier performance can
affect our ability to meet deadlines. How can communication help us get what we need from unresponsive
suppliers?
- Seven Planning Pitfalls: III
- We usually attribute departures from plan to poor execution, or to "poor planning." But one
cause of plan ineffectiveness is the way we think when we set about devising plans. Three cognitive
biases that can play roles are the so-called Magical Number 7, the Ambiguity Effect, and the Planning Fallacy.
- Anticipating Absence: Quarantine and Isolation
- When the pandemic compels some knowledge workers to quarantine or isolate, we tend to treat them as
if they were totally unavailable. But if they're willing and able to work, even part-time, they might
be able to continue to contribute. To make this happen, work out conditions in advance.
- Cost Concerns: Comparisons
- When we assess the costs of different options for solving a problem, we must take care not to commit
a variety of errors in approach. These errors can lead to flawed decisions. One activity at risk for
error is comparing the costs of two options.
See also Project Management and Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming December 11: White Water Rafting as a Metaphor for Group Development
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
- And on December 18: Subgrouping and Conway's Law
- When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed