The Fallacy of the False Cause

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
lead organizations
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 (though the thought has been attributed to many others as well):

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? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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 Organizational Change:

Names and Faces

Most of us feel recognized, respected, and acknowledged when others use our names. And many of us have difficulty remembering the names of others, especially those we don't know well. How can we get better at connecting names and faces?

How to Avoid Responsibility

Taking responsibility and a willingness to be held accountable are the hallmarks of either a rising star in a high-performance organization, or a naïve fool in a low-performance organization. Either way, you must know the more popular techniques for avoiding responsibility.

Exploiting Functional Fixedness: I

Functional fixedness is a cognitive bias that creates difficulty in seeing novel uses of things that have familiar uses. Some devious moves in workplace politics exploit functional fixedness.

Facts, Opinions, Estimates, and Desires

One reason why resource allocation debates can become so difficult is confusion about the differences among facts, opinions, estimates, and desires. Clarifying their differences can reduce the length and intensity of resource allocation debates.

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.

See also Organizational Change and Organizational Change for more related articles.

Forthcoming issues of Point Lookout

Coming February 12: On Substituting for a Star

Newcomers to work groups have three tasks: to meet and get to know incumbent group members; to gain their trust; and to learn about the group's task and how to contribute to accomplishing it. All can be difficult; all are made even more difficult when the newcomer is substituting for a star. Available here and by RSS on February 12.

And on February 19: Yet More Ways to Waste a Meeting

Experts have discovered that people have been complaining about meetings since the Bronze Age (3300-1200 BCE). Just kidding. But I'm probably right. As an aid to future archaeologists I offer this compilation of methods people use today to eliminate any possibility that a meeting might produce results worth the time spent. Available here and by RSS on February 19.

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