The Fallacy of the False Cause
by Rick Brenner
Although we sometimes make decisions with incomplete information, we do the best we can, given what we know. Sometimes, we make wrong decisions not because we have incomplete information, but because we make mistakes in how we reason about the information we do have.
Ginny was getting pretty steamed. "We tried code inspections back in Release 5, and you know what happened then. Everything slowed down, we got nothing done, everyone got into fights, and Morgan left the group. If we have to do inspections, you can count me out." Ginny's argument, in essence, was that since some unpleasant events happened shortly after inspections began, the code inspections caused them.
Arguments based on the
Fallacy of the False Cause
to make costly errorsAlthough her argument is convincing to many, it doesn't prove her case. It's an example of a rhetorical fallacy called post hoc ergo propter hoc — Latin for "after this, therefore because of this." Ginny argues that since the unpleasant events followed the adoption of code inspections, the code inspections caused the problems, and therefore all code inspections, of any kind whatever, are bad.
A more convincing argument would exclude other possible causes. For example, were the inspections run badly? Were people inadequately trained? Were inspections introduced when people were too busy to learn how to do inspections?
The Post Hoc fallacy is a special case of a more general type of fallacy — the fallacy of the false cause. In Post Hoc, the apparent causal connection relates to the timing of the two events. But connections can also be unrelated to timing:
All of the projects Gerhard has managed in the past few years have been late and over budget. Since people now believe that Gerhard was the cause of the overruns, he can no longer get assignments as a project lead. Nobody seems to remember that each of Gerhard's project sponsors had either reduced his budget or expanded requirements so many times that no project manager would have had much of a chance to perform well.
Gerhard's management skill was the most obvious factor common to the failed projects, but it wasn't the cause. In this case, faulty reasoning damages a career and deprives the company of a skilled manager.
How can you spot this kind of error in the heat of debate? The fallacy of the false cause might be lurking if the argument states that:
Since A was present when B occurred, then A was the cause. Or Since A preceded B, A caused B.
To respond to arguments that use this fallacy, use examples in which A was present, but B wasn't. Your debate partner might not be convinced, but it's your best shot.
Educate your colleagues about the Fallacy of the False Cause. When we understand how much it can cost, and when we understand how to avoid it, we can save much pain and frustration. Perhaps Will Rogers said it best:
It's not what we don't know that hurts; it's what we know that ain't so.
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
Would you like to see your comments posted here? rbrenVAThUNvUzQTKgzCtner@ChacGdKTAdKWXuwhUCpboCanyon.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
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.
More articles on Emotions at Work:
- The Slippery Slope That Isn't
- "If we promote you, we'll have to promote all of them, too." This "slippery-slope" tactic for winning debates works by exploiting our fears. Another in a series about rhetorical tricks that push our buttons.
- When You Make a Mistake
- We've all made mistakes, and we'll continue to do so for as long as we live. Making mistakes is part of being human. Still, we're often troubled by our mistakes, even when we remember that many mistakes turn out to be great gifts. Why do we have such a hard time acknowledging mistakes?
- Reverse Micromanagement
- Micromanagement is too familiar to too many of us. Less familiar is inappropriate interference in the reverse direction — in the work of our supervisors or even higher in the chain. Disciplinary action isn't always helpful, especially when some of the causes of reverse micromanagement are organizational.
- Changing Blaming Cultures
- Culture change in organizations is always challenging, but changing a blaming culture presents special difficulties. Here are three reasons why.
- Preventing Toxic Conflict: Part II
- Establishing norms for respectful behavior is perhaps the most effective way to reduce the incidence of toxic conflict at work. When we all understand and subscribe to a particular way of treating each other, we can all help prevent trouble.
See also Emotions at Work, Critical Thinking at Work and Rhetorical Fallacies for more related articles.
Forthcoming Issues of Point Lookout
- Coming October 14: Contextual Causes of Conflict: Part II
- Too often we assume that the causes of destructive conflict lie in the behavior or personalities of the people directly participating in the conflict. Here's Part II of an exploration of causes that lie elsewhere. Available here and by RSS on October 14.
- And on October 21: Managing Wishful Thinking Risk
- When things go wrong, and we look back at how we got there, we must sometimes admit to wishful thinking. Here's a framework for managing the risk of wishful thinking. Available here and by RSS on October 21.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenoBkQcEQsKcsidfoUner@ChacwxNsoZXLsuyEQnLCoCanyon.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:
Reprinting this article
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
- The Race to the South Pole: The Organizational Politics of Risk Management
- 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. We'll use the history of this event to explore lessons in risk management, its application to organizational efforts, and how workplace politics enters the mix. A fascinating and refreshing look at risk management from the vantage point of history and workplace politics. Read more about this program. Here's an upcoming date for this program:
- Team Development for Leaders
- Teams at work are often teams in name only — they're actually just groups. True teams are able to achieve much higher levels of performance than groups can. In this program, Rick Brenner shows team leads and team sponsors the techniques they need to form their groups into teams, and once they are teams, how to keep them there. Read more about this program. Here's an upcoming date for this program:
- Managing in Fluid Environments
- Most people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know whats coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here are some upcoming dates for this program: