Overcoming an urge to slap his own forehead, Jesse realized that they'd wasted the past six weeks. Just to be sure, he asked, "Courtney, are you saying, for example, that the Tier 2 languages aren't needed until Q3 next year?"
"Yes. I don't know how to be clearer. No Tier 2 languages till Q3 next year." Courtney was cool on the outside, but really steamed inside. She looked across the table at Miguel, and nodding slightly, replayed in her mind what he'd said on the way over: "These guys are genetically incapable of delivering anything within a decade of the plan date."
"I see," Jesse continued. "When you said 'full compliance with the spec Rev 2.07,' we thought you meant 'full compliance with the entire spec Rev 2.07,' which included languages. Now I understand that you meant only 'full compliance with the networking spec Rev 2.07."
We can't control
what others do
with what we sayMix-ups like this cost real money. One small word — 'entire' vs. 'networking' — made all the difference. Here are some reasons why the receiver might not receive the message the sender sends:
- Wandering attention
- We get distracted, and don't listen carefully. Or sometimes, we don't feel the need to listen.
- We assume that our first interpretation is correct
- This can happen because we anticipate or have pre-set expectations. Sometimes receivers even "repair" the message they receive, because it makes no sense as received.
- Differences in usage
- Sender and receiver might use the language differently. Perhaps they're a different sex, or in a different profession, as Jesse and Courtney are, or have different native languages.
- Past associations
- Our personal history with concepts, people, procedures, or technologies can be misleading.
- Anticipated discounting or padding
- Receivers might discount estimates or promises, because of past experience with the sender or with others. Or senders, anticipating a discount, might inflate estimates or promises differently from the receiver's discount.
And sometimes we just make mistakes. It's all very frustrating, and tempers can flare.
Language is ambiguous. When we're stressed or hurrying to save time, we don't check carefully enough for unrecognized ambiguity. But we can reduce the effects of message mismatches if we keep two ideas in mind.
- We can't control what others do with what we say
- Once the words are out, it's up to the hearer (or reader) to interpret them. We'll feel better about unexpected interpretations if we give up the idea that we control how people interpret our words.
- Let others check it out
- When we hear, "Let me see if I've got this right," we sometimes feel as if our competence or integrity is in doubt. But if we can learn to interpret this as a simple verification of understanding, we gain a valuable tool for preventing misunderstanding.
And you can check it out, too. Whether you're receiving or sending, you can uncover message mismatches with examples, what-ifs, restatements, and even humor. Whenever you try, you'll almost surely uncover at least some tiny differences. The time to worry is when you don't. Top Next Issue
The article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More
Your comments are welcomeWould you like to see your comments posted here? rbrenpqpguteWwrhHXEvoner@ChacYMNviKlyshKdRsIsoCanyon.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 Personal, Team, and Organizational Effectiveness:
- Figuring Out What to Do First
- Whether we belong to a small project team or to an executive team, we have limited resources and seemingly
unlimited problems to deal with. How do we decide which problems are important? How do we decide where
to focus our attention first?
- Help for Asking for Help
- When we ask for help, from peers or from those with organizational power, we have some choices. How
we go about it can determine whether we get the help we need, in time for the help to help.
- When Stress Strikes
- Most of what we know about person-to-person communication applies when levels of stress are low. But
when stress is high, as it is in emergencies, we're more likely to make mistakes. Knowing those mistakes
in advance can be helpful in avoiding them.
- The Limits of Status Reports: II
- We aren't completely free to specify the content or frequency of status reports from the people who
write them. There are limits on both. Here's Part II of an exploration of those limits.
- Why Sidebars Happen
- Sidebar conversations between meeting participants, conducted while someone else has the floor, are
a distracting form of disorder that can waste time and reduce meeting effectiveness. Why do sidebars happen?
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming August 23: Look Where You Aren't Looking
- Being blindsided by an adverse event could indicate the event's sudden, unexpected development. It can also indicate a failure to anticipate what could have been reasonably anticipated. How can we improve our ability to prepare for adverse events? Available here and by RSS on August 23.
- And on August 30: They Just Don't Understand
- When we cannot resolve an issue in open debate, we sometimes try to explain the obstinacy of others. The explanations we favor can tell us more about ourselves than they do about others. Available here and by RSS on August 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenoKDAArHMiHTkboENner@ChacSBjAFOGpkjlhpLdgoCanyon.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
- 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 are some dates for this program:
- The Westin Virginia Beach Town Center, 4535 Commerce Street,
Virginia Beach, VA 23462: September 13,
Monthly Meeting, Hampton Roads 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.
- The Westin Virginia Beach Town Center, 4535 Commerce Street, Virginia Beach, VA 23462: September 13, Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- 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 a date for this
- 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 Power Affect: How We Express Our Personal Power
- Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.
- "Rick is a dynamic presenter who thinks on his feet to keep the material relevant to the
— Tina L. Lawson, Technical Project Manager, BankOne (now J.P. Morgan Chase)
- "Rick truly has his finger on the pulse of teams and their communication."
— Mark Middleton, Team Lead, SERS