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?
- 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 welcomeWould you like to see your comments posted here? rbrennnFJXjAOFUQTQIRVner@ChacrcjwfJYVGnieDhgooCanyon.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 Conflict Management:
- See No Evil
- When teams share information among themselves, they have their best opportunity to reach peak performance.
And when some information is withheld within an elite group, the team faces unique risks.
- Is It Blame or Is It Accountability?
- When we seek those accountable for a particular failure, we risk blaming them instead, because many
of us confuse accountability with blame. What's the difference between them? How can we keep blame at bay?
- How to Create Distrust
- A trusting environment is critical to high performance. That's why it's important to recognize behaviors
that erode trust in others. Here's a little catalog of methods people use — intentionally or not
— to create distrust.
- Handling Heat: II
- Heated exchanges in meetings can compromise both the organizational mission and the careers of the meeting's
participants. Here are some tactics for people who aren't chairing the meeting.
- Contextual Causes of Conflict: II
- Too often we assume that the causes of destructive conflict lie in the behavior or personalities of
the people directly participating in the conflict. Here's Part II of an exploration of causes that lie
Forthcoming issues of Point Lookout
- Coming May 15: Entry Intimidation
- Feeling intimidated about entering a new work situation can affect performance for both the new entrant and for the group as a whole. Four trouble patterns related to entry intimidation are inadvertent subversion, bullying, hat hanging, and defenses and sabotage. Available here and by RSS on May 15.
- And on May 22: Newtonian Blind Alleys: I
- When we decide how to allocate organizational resources, we make assumptions about how the world works. Often outside our awareness, the thinking of Sir Isaac Newton influences our assumptions. And sometimes they lead us into blind alleys. Universality is one example. Available here and by RSS on May 22.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenIqQyDzXAAYujtNGuner@ChactOQpGiTOZboPvifWoCanyon.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
- 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.