by Rick Brenner
When we steer the discussion away from issues to attack the credibility, motives, or character of our debate partners, we often resort to a technique known as the ad hominem attack. It's unfair, it's unethical, and it leads to bad, expensive decisions that we'll probably regret.
Luckily, Greta had a mouthful of salad and couldn't respond immediately to Walt's "You argued for the opposite position on Marigold." If she could have responded, she realized, she would have fallen into Walt's trap. While he continued on, she finished chewing, and then carefully set down her fork. Then she let him have it.
"Whether I took a different position on Marigold doesn't matter. The question now is: should we use Houston for Metronome, or should we do the work here? I admit that I'm an imperfect human being, as I'm sure you would admit that you are too, but the question is: can Houston do the job?"
Silence around the table. Walt seemed a little stunned. Greta picked up her fork and resumed work on her salad.
Walt has just paid the price for using a type of rhetorical fallacy known as an ad hominem attack. It's powerful and it can lead a group into a wilderness of confusion and sloppy thinking, where bad decisions are born.
The ad hominem attack
is powerful, and it can
lead to sloppy thinking
and bad decisionsMany of us are unprepared for ad hominem attacks. Even if we are prepared, in the heat of debate we can forget what we know. There are three common forms of the ad hominem fallacy.
- Ad hominem abusive
- This is a direct attack on your humanity. The logic: You're a rotten person; therefore your assertion is false. Example: The last project you managed was 30% over budget, so I don't believe your projections on this one.
- Ad hominem tu quoque
- The tu quoque form tries to demonstrate that you're inconsistent or hypocritical. The logic: You once said something different; therefore you aren't credible; therefore your assertion is false. Walt tried this one on Greta.
- Circumstantial ad hominem
- The circumstantial form is an attack on your associations — your job, your heritage, or other affiliations. The logic: You have rotten friends; therefore your assertion is false. Example: Since you're a hardware engineer, your suggestion that we fix this in the software is wrong.
What can you do about an ad hominem?
- Don't defend yourself or respond in kind
- If you defend yourself or respond in kind you'll only help your partner take the discussion off point. Instead, get back to the issues. Greta did it masterfully.
- If you're a spectator, identify it
- As a spectator identify the ad hominem to the group — you have more credibility than the target does, because you aren't directly under attack. And you have a right to demand that the debaters stick to the issues.
- If you notice yourself doing it, stop
- Better debates start with you. If you slip up, apologize to your partner. If not immediately, then later, privately.
During a debate, identifying an ad hominem attack against yourself is risky. Instead, get back to the issues — pointing out your partner's fallacious tactics could be an ad hominem attack in itself. Top Next Issue
For more on ad hominem attacks, see "Some Subtleties of Ad Hominem Attacks," Point Lookout for November 14, 2012.
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? Send 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 Personal, Team, and Organizational Effectiveness
- When Meetings Boil Over
- At any time, without warning, you can find yourself in a meeting that boils over. Sometimes tempers rise, then voices rise, and then people yell and scream. What can a team do when meetings threaten to boil over — and when they do?
- Should I Keep Bailing or Start Plugging the Leaks?
- When we're flooded with problems, and the rowboat is taking on water, we tend to bail with buckets, rather than take time out to plug the leaks. Here are some tips for dealing with floods of problems.
- Who Would You Take With You to Mars?
- What makes a great team? What traits do you value in teammates? Project teams can learn a lot from the latest thinking about designing teams for extended space exploration.
- 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.
- Take Charge of Your Learning
- Many of us let others set our learning agendas — peers, employers, or the mass media. But you can gain much both personally and professionally by setting your own learning agenda.
See also Personal, Team, and Organizational Effectiveness, Effective Communication at Work, Critical Thinking and Rhetorical Fallacies for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at rbrenner@ChacoCanyon.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: Ten Lessons for Project Managers
- 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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
- 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 an upcoming date for this program: