Perhaps you've witnessed destructive collisions between teammates. Destructive collisions can arise from innocent misunderstandings, long-term campaigns to advance careers, spontaneous attacks, or acts of revenge. They can be mildly awkward or intensely damaging. Rarely do they advance the team's work. At best, they slow progress; at worst, they move the team so far from its objectives that success requires redefining the objectives.
Historical debates are one kind of collision in which the issue is who said what, who agreed to what, who decided what, or the like. Historical debates can take place in any medium: face-to-face, email, text, stone tablets, whatever. The exchanges being debated might or might not have been witnessed; there might or might not be a record of the incident or of the exchange. None of that matters.
What does matter is that the past is always debatable. Usually, the debaters' recollections differ; the witnesses' (if any) recollections (if any) differ; and interpretations of any records that might exist likewise differ. The past is always debatable.
Historical debates are difficult to settle. Sadly, many bystanders feel that they aren't involved; the debate concerns only the debaters. These bystanders just, well, stand by, while time, the most precious asset of any team effort, passes.
Other bystanders recognize the damage being done, but feel helpless to resolve the debate. Indeed, they are helpless, or nearly so. These bystanders tend to wait, hoping for a debate fizzle. At best, in meetings, a bystander might intervene to suspend the debate, suggesting, for example, "Can't you take this off line?" The debate might halt for a time, only to arise again later.
Two strategic moves can help teams experiencing repeated historical debates. First, end the debate, permanently, and return to real work. Second, prevent historical debates from arising in the future. Here are two suggestions for accomplishing this.
- Identify the pattern
- When no When no debate is actually
underway, educate the team
about the historical debate
pattern. Explore its
futility and irrelevance.debate is actually underway, educate the team about the historical debate pattern. Explore its futility and irrelevance. Identifying the pattern, and naming it, gives the team a verbal and conceptual vocabulary essential for calling out historical debates when they arise. The existence of that vocabulary can deter people from initiating historical debates. - Learn how bystanders can intervene
- To end historical debates when they occur, neutral intervention is required. Taking sides usually just intensifies the debate. Instead, bystanders can offer, "Would either of you like to hear how I saw the situation?" Most often, the bystander's view will differ from the views of the debaters. Such offers won't resolve the debates, but they can demonstrate clearly how useless the debates actually are, and that can lead to voluntary suspensions of the exchanges.
When you broach this topic with your team, refrain from using a past debate as an example. That might ignite a historical debate about whether a past debate was a historical debate. 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
Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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.
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:
- Top Ten Signs of a Blaming Culture
- The quality of an organization's culture is the key to high performance. An organization with a blaming
culture can't perform at a high level, because its people can't take reasonable risks. How can you tell
whether you work in a blaming culture?
- Responding to Threats: III
- Workplace threats come in a variety of flavors. One class of threats is indirect. Threateners who use
the indirect threats aim to evoke fear of consequences brought about not by the threatener, but by other
parties. Indirect threats are indeed warnings, but not in the way you might think.
- How to Misunderstand Somebody Else
- Misunderstandings are commonplace at work, as in most of the rest of Life. At work, they might be even
more commonplace, because at work it sometimes seems that people are actually trying to misunderstand.
Here's a handy guide for those who want to get better at misunderstanding others.
- When You Feel Attacked
- Verbal attacks might be upsetting, but in creative conflicts they're usually permissible if related
to substantive matters. When verbal attacks are personal, they can be unfair and illegitimate. The ability
to recenter yourself quickly is invaluable.
- Resolving Ambiguity
- Ambiguity is anathema to success in collaborations. It causes errors and rework, extending time-to-market.
When we interpret information, we often choose the first interpretation we find, never recognizing that
others are possible. That leads to failure.
See also Conflict Management, Effective Meetings and Cognitive Biases at Work for more related articles.
Forthcoming issues of Point Lookout
- Coming May 8: Antipatterns for Time-Constrained Communication: 3
- Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 3 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing past experiences of participants. Available here and by RSS on May 8.
- And on May 15: Should I Write or Should I Call?
- After we recognize the need to contact a colleague or colleagues to work out a way to move forward, we next must decide how to make contact. Phone? Videoconference? Text message? There are some simple criteria that can help with such decisions. Available here and by RSS on May 15.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed