Clueless on the Concept

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

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:

Heavy Burdens: Should, Always, Must, and Never

As a leader you carry a heavy burden. You're accountable for everything from employee development to meeting organizational objectives, and many of these responsibilities conflict. Life is tough enough, but most of us pile on a load of over-generalized rules of work life — a load too heavy for anyone to bear.

No Surprises

If you tell people "I want no surprises," prepare for disappointment. For the kind of work that most of us do, surprises are inevitable. Still, there's some core of useful meaning in "I want no surprises," and if we think about it carefully, we can get what we really need.

We Are All People

When a team works to solve a problem, it is the people of that team who do the work. Remembering that we're all people — and all different people — is an important key to success.

Finding the Third Way

When a team is divided, and agreement seems out of reach, attempts to resolve the conflict usually focus on the differences between the contrasting positions. Focusing instead on their similarities can be a productive technique for reaching agreement.

Contextual Causes of Conflict: I

When destructive conflict erupts, we usually hold responsible only the people directly involved. But the choices of others, and general circumstances, can be the real causes of destructive conflict.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming January 1: The Storming Puzzle: II

For some task-oriented work groups, Tuckman's model of small group development doesn't seem to fit. Storming seems to be absent, or Storming never ends. To learn how this illusion forms, look closely at Satir's Change Model and at what we call a task-oriented work group. Available here and by RSS on January 1.

And on January 8: The Storming Puzzle: III

For some task-oriented work groups, Tuckman's model of small group development seems not to fit. Storming seems to be either absent or continuous. To learn how this illusion forms, look closely at the processes that can precipitate episodes of Storming in task-oriented work groups. Available here and by RSS on January 8.

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:

• 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