Anecdotes and Refutations

Alpha and Bravo are debating how to complete their project, given the rumors of coming rounds of "reductions in force," and therefore looming shortages of people to do the work. Alpha says, "I'm worried about resource availability. Bravo replies, "I know, I've heard the same rumors, but I think we'll be OK."

Alpha isn't satisfied. "What about Charlie [the lead on the effort]? He might not be available. His Dad isn't well, and Charlie missed some days last week. Even if his Dad pulls through, I don't think we have his full attention."

Alpha is using an anecdote to make his point. Charlie's situation is an example of Alpha's concern that the project is vulnerable to a risk of staff shortages more general than just Charlie's situation. Alpha actually wants to make arrangements to manage that risk.

Because argument-by-anecdote can't ever prove anything, Alpha hasn't proven that the risk of staff shortage is something that must be addressed. Alpha has merely supplied an example. But the more serious problem with argument-by-anecdote is that it invites refutation-by-anecdote.

Here's how. Bravo replies, "Haven't you heard? Charlie's Dad's surgery was a success! He's already in rehab, and the family is greatly relieved. Charlie is like a new man."

Bravo is refuting Alpha's anecdote with another anecdote, indicating that Charlie will be available and able to focus on the project. But Bravo's anecdote is no more proof of the absence of risk of staff shortage than is Alpha's anecdote proof of the presence of that risk.

Alpha and Bravo can dance like this forever, trading anecdotes and refutations. It's a waste of time, and it leads to bad decisions. What can you do if proof-by-anecdote and refutation-by-anecdote have taken root in your organization?

Educate

Talk about the role of anecdotes in argumentation. Define anecdotes as illustrative stories about specific events that might or might not be true.

Identify them

If you use an anecdote to illustrate a point, say so: "I'm using this anecdote as an illustration." If someone else uses an anecdote, and doesn't explicitly say so, anyone else is free to point that out: "I appreciate your offering that anecdote."

Define standards of proof

Explain to everyone Argument-by-anecdote can never
prove anything. It can only disprove
by counterexample, and then
only if validated.that anecdotes can never, ever, prove anything generally, because they aren't validated, and because they're specific. If an anecdote is true, if might disprove a general assertion, but then we call it a counterexample.

Don't refute anecdotes

Refuting anecdotes doesn't advance the argument, because anecdotes aren't part of the logic. Refuting anecdotes admits them, illicitly, into the logic of the debate. Anecdotes are always illustrations, and that's all they can ever be.

Become an anecdote census-taker. Count examples of anecdotes being used as proof or refutation. If you can't get through a day without observing one or two anecdote incidents, your organization might have a problem.  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

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 Conflict Management:

Making Memories to Cherish

We all have cherished memories — lovely moments we can replay whenever we want to feel happy. How would you like to have a lot more of them?

Recognizing Hurtful Dismissiveness

"Never mind" can mean anything from "Excuse me, I'm sorry," to, "You lame idiot, it's beyond you," and more. The former is apologetic and courteous. The latter is dismissive and hurtful. We have dozens of verbal tactics for hurting each other dismissively. How can we recognize them?

Reframing Hurtful Dismissiveness

Targets of dismissive remarks often feel that their concerns are being judged as unimportant, which can be painful when their concerns are real. But there is an alternative to pain. It requires a little skill and discipline, but it can work.

Agenda Despots: II

Some meeting chairs crave complete or near-complete control of their meeting agendas. In this Part II of our exploration of their techniques, we emphasize methods for managing unwanted topic contributions from attendees.

On Delegating Accountability: II

What happens to accountability when we delegate responsibility for a mission? As a result of delegation, the distribution of responsibility, authority, and accountability can assume any of eight possible forms. Here's a catalog.

See also Conflict Management and Conflict Management for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

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