Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 24, Issue 17;   April 24, 2024: Antipatterns for Time-Constrained Communication: I

Antipatterns for Time-Constrained Communication: I

by

Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part I of a collection of communication antipatterns that arise in technical communication under time pressure.
Three gears in a configuration that's inherently locked up

Three gears in a configuration that's inherently locked up. They look like they might do something, but they can't move at all. In this way, they're a metaphor for the concept of antipattern. Any combination of an odd number of planar gears configured in a loop is inherently locked. When we communicate with each other under time pressure we're at risk of attempting to do the impossible without realizing it. We might inadvertently place too much emphasis on communication speed, and too little on communication quality. Image by J_Alves.

Communication can go wrong in so many ways and for so many different reasons that it's a wonder we can exchange any thoughts at all. But somehow, often, we can. And we can do even better if we learn to recognize communication patterns that lead to trouble even though they seem to be useful at first. Because these patterns lead to unwelcome results, they're usually called antipatterns. [Koenig 1995]

This post and two more to come contain elements of one more tool you might add to your toolbox to help untangle miscommunications or — even better — to help prevent them. And to make this exploration manageable, I'll restrict it to time-constrained communication.

The elements of this tool consist of a collection of antipatterns. Quoting Andrew Koenig, who coined the term in the context of software engineering, "An antipattern is just like a pattern, except that instead of a solution it gives something that looks superficially like a solution, but isn't one."

We use many different patterns when we communicate. Among the simplest is what we say when we answer a phone: "Hello". Hello means, roughly, "I'm here and I'm listening; your turn." There are probably thousands of communication patterns. Some work, many don't. The ones that don't work are what we call antipatterns. This post has three examples.

In what follows, I use the name Eugene (E for Expressing) when I'm referring to the person expressing an idea, asking a question, or in some other way contributing new material to an exchange. And I use the name Rachel (R for Receiving) when I'm referring to the person Receiving Eugene's communication. Finally, I assume that both Eugene and Rachel are under time pressure.

With that prolog, here are three antipatterns that increase the risk of miscommunication.

Too big and too complicated
Eugene is busy and he knows that Rachel is too, so he tries to pack his message with his questions, insights, talking points, and all the background information he regards as relevant.
As a Dealing with any subject with too
little time is unlikely to produce
the outcome we want
result, what Eugene is trying to express is too big, too complicated, or requires too much time compared to the time available. If Rachel and Eugene push ahead anyway, confusion and miscommunication are the probable results.
Dealing with any subject with too little time is unlikely to produce the outcome they want. If Eugene's thoughts need more time, the two partners would do well to solve that problem first, and then address the subject of their conversation. If they can't expand the time available, exchanging messages in more compact packets is the best available alternative.
Mismatched knowledge stacks
A person's knowledge stack is the partially ordered collection of terms, experiences, and concepts that are needed to understand a message. For example, when someone asks for your email address, you retrieve it from your knowledge stack and relay it to the requestor. Or when you need to know the local time of day for someone you're planning to engage by phone, you reach into your knowledge stack for that answer or perhaps how to find that answer. Less trivial examples include the meanings of acronyms, or the current assessment of the capabilities of a market rival.
When we fail to verify that participants in an exchange have compatible knowledge stacks, they might get deep into the exchange before they realize that they aren't using words or concepts in the same way. Then they have to retreat and reconstruct the conversation after they've verified that they're using terms compatibly. And they need to check that everyone's stack is free of gaps and omissions.
One way to limit the occurrence of this antipattern is to publish and maintain a "terminology and concept glossary."
Inappropriate focus: the McNamara Fallacy
The McNamara Fallacy is the discredited idea that one can manage the missions of complex organizations by deriving guidance solely from numeric measurements of inputs and outputs. If these "metrics" are correctly chosen, so says the Fallacy, we can make good decisions based only on these metrics. [Baskin 2014] [Muller 2019] In this way, the Fallacy causes us to confuse Objectivity with Importance. More
An antipattern in itself, the McNamara Fallacy appears in many contexts beyond communications. In the communications context, the McNamara Fallacy causes the exchange participants to focus attention on the values of one or a few metrics, instead of the process or entity that the metrics supposedly represent.
For example, if a team is concerned that attendance at meetings is 85% instead of the goal value of 95%, the conversation might focus on percentage overall attendance instead of the fact that on average, all of the "right people" for any given meeting have been attending with regularity.
By misleading the team with objective-sounding data, the Fallacy can cause a team to focus on related but inessential material instead of material that's central to the team's mission.

Last words

These three causes of miscommunication under time pressure are generic in the sense that they don't depend on message content. Next time I'll examine some patterns that lead to miscommunications in ways that do depend on message content.  Antipatterns for Time-Constrained Communication: II Next issue in this series  Go to top Top  Next issue: Antipatterns for Time-Constrained Communication: II  Next Issue

101 Tips for Managing Conflict 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!

Footnotes

Comprehensive list of all citations from all editions of Point Lookout
[Koenig 1995]
Andrew Koenig. "Patterns and Antipatterns," Journal of Object-Oriented Programming 8:1, 1995, pp.46-48. Back
[Baskin 2014]
J.S. Baskin, "According To U.S. Big Data, We Won The Vietnam War," Forbes Magazine, 2014. Available here. Retrieved 6 February 2023. Back
[Muller 2019]
J.Z. Muller. The Tyranny of Metrics. Princeton (New Jersey): Princeton University Press, 2018. Order from Amazon.com. Back

Your comments are welcome

Would you like to see your comments posted here? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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 Effective Communication at Work:

Henry David ThoreauEncourage Truth Telling
Getting to the truth can be a difficult task for managers. People sometimes withhold, spin, or slant reports, especially when the implications are uncomfortable or threatening. A culture that supports truth telling can be an organization's most valuable asset.
Shaking an orange treeWhen You Aren't Supposed to Say: III
Most of us have information that's "company confidential," or even more sensitive than that. Sometimes people who want to know what we know try to suspend our ability to think critically. Here are some of their techniques.
A Roman coin from the reign of Marcus Cocceius NervaThe Ups and Downs of American Handshakes: I
In much of the world, the handshake is a customary business greeting. It seems so simple, but its nuances can send signals we don't intend. Here are some of the details of handshakes in the USA.
Publicity photo of American entertainer Bert Lahr, promoting his role as the Cowardly Lion in the 1939 feature film, "The Wizard of Oz".What Is Hypophora?
Hypophora is a rhetorical device that enables its users to deliver simple messages with enhanced power. But it has a dark side. The people who read or hear those messages tend to assess them as having more merit than they do.
A happy dogMore Things I've Learned Along the Way: V
When I gain an important insight, or when I learn a lesson, I make a note. Example: If you're interested in changing how a social construct operates, knowing how it came to be the way it is can be much less useful than knowing what keeps it the way it is.

See also Effective Communication at Work and Effective Communication at Work for more related articles.

Forthcoming issues of Point Lookout

A white water rafting team completes its courseComing December 11: White Water Rafting as a Metaphor for Group Development
Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
Tuckman's stages of group developmentAnd on December 18: Subgrouping and Conway's Law
When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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:

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-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.