Faulty logic is one reason why groups make defective decisions. In long discussions, spanning many meetings, email messages and other postings, a chain of logic emerges. Usually, the chain is valid and coherent, but when the conversation becomes complex, when the stakes are high, or when time is short, a group can make logical errors. Here's a small collection.
- The fallacy fallacy
- If the argument used to reach our conclusions is later found to be flawed, we sometimes believe that the conclusion produced by that argument must also be false.
- Not so. That we reached a particular conclusion by faulty logic doesn't mean that the conclusion itself is false. The conclusion might be true, or it might be false.
- Sand castle fallacy
- If the argument is founded on premises that later prove to be false, or partly false, we sometimes believe that the conclusion produced by that argument must also be false.
- Not so. That we reached a particular conclusion based on faulty premises doesn't mean that the conclusion is false. We might have built a castle on sand, but it might still be a castle. If we can find a better foundation for that castle, it might yet prove durable.
- Affirming a disjunct
- If we know that A or B is true, and it turns out that A is true, we sometimes conclude that B must be false.
- The fallacy here arises in instances when A and B are both true. In informal conversation, we often use "or" in the exclusive sense: either A or B, but not both. But in many situations, "or" actually is valid in the inclusive sense: A or B or possibly both A and B.
- Affirming the consequent
- When a conversation becomes
complex, when the stakes
are high, or when time
is short, a group can
make logical errors - In this error, sometimes called the converse error, we conclude incorrectly that a premise must be true if the conclusion is true. That is, when we know that P implies Q, and we know that Q holds, we wrongly conclude that P must also be true.
- The problem here is that the converse of a true statement isn't necessarily true. The contrapositive is true, though: if not Q then not P.
- Denying the antecedent
- This formal fallacy, sometimes also called the inverse error, is committed when we know that if P, then Q. If we later find that P is false, we then sometimes conclude erroneously that Q is false.
- All we can say for sure is that Q might be false when P is false; Q might also be true.
Keeping these errors and their names straight can be difficult, but learning to recognize and avoid them is certainly easier. There is a trap, though. Once you notice that a group has committed one of these errors, remember that it's often possible that their conclusion is correct. To forget that possibility is to commit the fallacy fallacy. Top Next Issue
Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. 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 Personal, Team, and Organizational Effectiveness:
- Selling Uphill: Before and After
- Whether you're a CEO appealing to your Board of Directors, your stockholders or regulators, or a project
champion appealing to a senior manager, you have to "sell uphill" from time to time. Persuading
decision makers who have some kind of power over us is a challenging task. How can we prepare the way
for success now and in the future?
- Personal Trade Secrets
- Do you have some little secret tricks you use that make you and your team more effective? Do you wish
you could know what secret tricks others have? Here's a way to share your secrets without risk.
- The Perils of Piecemeal Analysis: Content
- A team member proposes a solution to the latest show-stopping near-disaster. After extended discussion,
the team decides whether or not to pursue the idea. It's a costly approach, because too often it leads
us to reject unnecessarily some perfectly sound proposals, and to accept others we shouldn't have.
- Confirmation Bias: Workplace Consequences: I
- We continue our exploration of confirmation bias, paying special attention to the consequences it causes
in the workplace. In this part, we explore its effects on our thinking.
- Solutions as Found Art
- Examining the most innovative solutions we've developed for difficult problems, we often find that they
aren't purely new. Many contain pieces of familiar ideas and techniques combined together in new ways.
Accepting this as a starting point can change our approach to problem solving.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness 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