Occasionally a team member or two seem clueless on the concept. They haven't understood something basic to the effort, or worse, they think they understand, but they don't. If the rest of the team is wrong — and doesn't realize it — even one clueless individual can truly be a gift. Debates lead to new understanding, and usually that's progress. But most often, the minority view was just wrong, and everyone else was on the right path.
Sometimes the minority is confused because of indolence or distraction. That's best treated as a performance issue. At other times, the problem is miscommunication, or lack of background, or the difficulty of the concept itself. If this situation is handled indelicately, it is most fraught with risk to relationships.
Here are three tips for avoiding those risks. In what follows, Charlie is the clueless one, and I'll alternate Charlie's gender.
- The clueless usually don't identify themselves
- If Charlie doesn't realize that he's clueless, he sees no need to announce his cluelessness. But even if he senses that something is amiss, he might conceal his confusion to avoid embarrassment, especially if ridicule or derision — even the good-natured kind — is part of team culture.
- Even when everyone seems to grasp the issue, it can be risky to assume without careful verification that they actually do. Be attuned to the nuances that suggest confusion.
- Misimpressions and misconceptions happen for a reason
- Charlie might have developed her conceptual understanding on the basis of ambiguous information. The information might not have been sufficient to clearly distinguish between the misconception she developed, and the concept everyone else acquired. Charlie's version of the concept might actually be consistent with the information she was given.
- Even though the If people don't realize that
they're clueless, they see no
need to announce
their cluelessnessinformation Charlie got might have been identical to what others received, her past experience and knowledge might have led her to see things differently. To manage this risk, be ridiculously explicit when communicating difficult or abstract ideas. Use numerous examples. - Consider a private discussion
- When you suspect that Charlie's conceptual understanding is somehow incorrect, public inquiry is an ineffective and risky way to investigate the matter. By the time others suspect confusion, Charlie almost certainly does, too. He'll notice any investigation, even the indirect kind, and he might very well respond so as to conceal the misconception.
- A private conversation can be much more productive and sparing of Charlie's feelings, because he's more likely to be forthcoming in private than he is in a more public setting.
Very likely, you felt that you weren't clueless on the concept of being clueless on the concept. But if you were clueless about it, you wouldn't have known it. Anyway, I hope you aren't now. But then, I have no way of knowing. Top Next Issue
Occasionally we have the experience of belonging to a great team. Thrilling as it is, the experience is rare. In part, it's rare because we usually strive only for adequacy, not for greatness. We do this because we don't fully appreciate the returns on greatness. Not only does it feel good to be part of great team — it pays off. Check out my Great Teams Workshop to lead your team onto the path toward greatness. More info
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 Personal, Team, and Organizational Effectiveness:
- Recovering Time: I
- Where do the days go? How can it be that we spend eight, ten, or twelve hours at work each day and get
so little done? To recover time, limit the fragmentation of your day. Here are some tips for structuring
your working day in larger chunks.
- Assumptions and the Johari Window: I
- The roots of both creative and destructive conflict can often be traced to differing assumptions of
the parties to the conflict. Working out these differences is a lot easier when we know what everyone's
assumptions are.
- How to Avoid Getting What You Want
- Why would you want to know how to avoid getting what you want? Well, suppose you had perfected ways
of avoiding getting what you want, but you weren't aware that you were doing it. This one's for you.
- Embolalia and Stuff Like That: II
- Continuing our exploration of embolalia — filler syllables, filler words, and filler phrases —
let us examine the more complex forms. Some of them are so complex that they appear to be actual content,
even when what they contain is little more than "um."
- Be Choosier About Job Offers: I
- A serious error some job seekers make is accepting an offer that isn't actually a good fit. We make
this mistake for a variety of reasons, including hating the job-search process, desperation, and wishful
thinking. How can we avoid the error?
See also Personal, Team, and Organizational Effectiveness and Problem Solving and Creativity for more related articles.
Forthcoming issues of Point Lookout
- Coming April 24: Antipatterns for Time-Constrained Communication: 1
- 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 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.
- And on May 1: Antipatterns for Time-Constrained Communication: 2
- Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.
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