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 welcomeWould you like to see your comments posted here? rbrenTXpbNuwjDRFbaOEmner@ChacFMcwFwTokXxyViaGoCanyon.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.
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 Personal, Team, and Organizational Effectiveness:
- Team Thrills
- Occasionally we have the experience of belonging to a great team. Thrilling as it is, the experience
is rare. How can we make it happen more often?
- Dealing with Deadlock
- At times it seems that nothing works. Whenever we try to get moving, we encounter obstacles. If we try
to go around them, we find more obstacles. How do we get stuck? And how can we get unstuck?
- Let's Revise Our Rituals
- Throughout the workday, we interact with each other on many levels. Some exchanges are so common and
ritualized that we're no longer aware of them. If we revise these rituals slightly, we can add some
zing to our lives.
- Tactics for Asking for Volunteers: I
- CEOs, board chairs, department heads and team leads of all kinds sometimes seek people to handle specific,
time-limited tasks. Asking the group for volunteers works fine — usually. There are alternatives.
- The Ups and Downs of American Handshakes: II
- Where the handshake is a customary business greeting, it's possible to offend accidentally. Here's Part
II of a set of guidelines for handshakes in the USA.
Forthcoming issues of Point Lookout
- Coming May 23: Narcissistic Behavior at Work: IX
- An arrogant demeanor is widely viewed as a hallmark of the narcissist. But truly narcissistic arrogance is off the charts. It's something beyond the merely annoying arrogance of a sometimes-obnoxious individual. What is narcissistic arrogance and how can we cope with it? Available here and by RSS on May 23.
- And on May 30: Chronic Peer Interrupters: I
- When making contributions to meeting discussions, we're sometimes interrupted. Often, the interruption is beneficial and saves time. But some people constantly interrupt their peers or near peers, disrespectfully, in a pattern that compromises meeting outcomes. How can we deal with chronic peer interrupters? Available here and by RSS on May 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenkAzuUDGSrFWFKEKtner@ChacVEFeKbyJjDPiMYecoCanyon.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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Technical Debt Management: Making the Business Case
- This program
outlines the steps necessary for deploying a program for rational management of technical debt. For
many organizations, adopting a program for rationally managing technical debt entails organizational
change. And unlike some organizational changes, this one touches almost everyone in the organization,
because technical debt isn't merely a technical problem. Technical debt manifests itself in technological
assets, to be sure, but its causes are rarely isolated to the behavior and decisions of engineers. We
can't resolve the problem of chronically excessive levels of technical debt by changing the behavior
of engineers alone. Technical debt is the symptom, not the problem. In this program we outline the essential
elements of an effective business case for adopting a rational technical debt management program. But
this business case, unlike many business cases, cannot be captured in a document. We must make the case
not only at the leadership level of the organization, but also at the level of the individual contributor.
Everyone must understand. Everyone must contribute. We explore five issues that make technical debt
so difficult to manage, and develop five guidelines for designing technical debt management strategies
for the modern enterprise. Read more about
this program. Here's a date for this program:
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield,
Illinois 62701: June 12,
Monthly Meeting, Central
Illinois Chapter of the Project Management Institute. Register now.
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield, Illinois 62701: June 12, Monthly Meeting, Central Illinois Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: The Power of Agile Development
- 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. Lessons abound. Among the more important
lessons are those that demonstrate the power of the agile approach to project management and product
development. Read more about this program. Here's
a date for this program:
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227:
Monthly Meeting, Cincinnati
chapter of the International Institute of Business Analysis. Register now.
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. Register now.
- The Power Affect: How We Express Our Personal Power
- Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.