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? rbrenkUuufvaugIMyeFfuner@ChacwUfWPNaauHmSiSMRoCanyon.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:
- Saying No
- When we have to say "no" to customers or to people in power, we're often tempted to placate
with a "yes." There's a better way: learn how to say "no" in a way that moves the
group toward joint problem solving.
- Discussion Distractions: II
- Meetings are less productive than they might be, if we could learn to recognize and prevent the most
common distractions. Here is Part II of a small catalog of distractions frequently seen in meetings.
- What Insubordinate Non-Subordinates Want: III
- When you're responsible for an organizational function, and someone not reporting to you doesn't comply
with policies you rightfully established, trouble looms. What role do supervisors play?
- 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.
- Pariah Professions: II
- In some organizations entire professions are regarded as pariahs — outsiders. They're expected
to perform functions that the organization does need, but their relationships with others in the organization
are strained at best. When pariahdom is tolerated, organizational performance suffers.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenNrBxccNNsKRwEwdjner@ChacSiEzzrpObNuCnScIoCanyon.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:
- 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
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- 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 organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.