Someone recently corrected my pronunciation of schism. I had said shism, and I was corrected to skism, which I accepted without retort. Looking at a dictionary the next day, I learned that both are acceptable in U.S. English, but both are less acceptable than sizm. (See Merriam-Webster.com.) I also learned from this exercise that my corrector didn't actually know what he was talking about.
That was a minor incident, but it reminded me that correcting the words or meaning of another can be a perilous proposition. Here are some of the risks of correcting others.
- Too much alacrity suggests an agenda beyond simple correction. It suggests anger, insecurity, revenge, or something even darker.
- Too much confidence puts you at risk of appearing arrogant.
- A mistaken correction risks making you look foolish — if not immediately, later.
- Even if you're right, you risk offending the person you corrected, or offending others, which can create or exacerbate tension in the group.
- Correcting something irrelevant to the conversation can deflect the group from its intended focus.
Probably you can think of half a dozen more risks if you spend an hour at it.
And there are oodles of ways to offer your views abrasively. When you hear someone use one of these, take cover, because something bad could be about to happen:
- You're wrong (mistaken, misinformed, …)
- The right answer is X
- That's not so; that's old information
- I used to think so, too (before I achieved my current state of enlightenment)
Sometimes, the urge to correct can be overwhelming. And sometimes, correction is actually called for. Here are some tips for offering your own views in ways that limit the risks.
- Check for necessity and effectiveness
- Is correction really necessary? Will correction advance the conversation in a material way? Generally, unless you're responding to a prior request, it doesn't pay to correct others' grammar, diction, pronunciation, tact, or manners.
- Acknowledge your own fallibility
- Acknowledge that you could be mistaken. For instance, "I remember that a little differently — I thought it went this way, …."
- Make details optional
- Ask yourself, "Is correction
really necessary? Will correction
advance the conversation
in a material way?"
- For even more safety, give the person or the group a choice: "I remember that discussion a bit differently — if that would be helpful."
- Acknowledge your own subjectivity
- "I disagree," is mostly a statement about your own thoughts; "You're wrong," is mostly a judgment about what the other has said, or what you believe the other said. The former is a little safer because it's information about yourself.
Most important, when you offer an alternative view, or a correction, in whatever form, look first for potholes. Leading the group in the wrong direction can be hazardous to all, especially to the one who led them there. Top Next Issue
For more about differences and disagreements, see "Appreciate Differences," Point Lookout for March 14, 2001; "When You Think They've Made Up Their Minds," Point Lookout for May 21, 2003; "Blind Agendas," Point Lookout for September 2, 2009; and "Is the Question 'How?' or 'Whether?'," Point Lookout for August 31, 2011.
Do you spend your days scurrying from meeting to meeting? Do you ever wonder if all these meetings are really necessary? (They aren't) Or whether there isn't some better way to get this work done? (There is) Read 101 Tips for Effective Meetings to learn how to make meetings much more productive and less stressful — and a lot more rare. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrencGrBYdALGfSClGGJner@ChacQoEGHzKNuXjsfSzaoCanyon.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:
- Food for Thought
- Most companies have employee cafeterias, with the usual not-much-better-than-high-school food service.
By upgrading — and subsidizing — food service, these companies can reduce turnover and improve
- Selling Uphill: Before and After
- Whether you're a CEO appealing to your Board of Directors, your stockholders or regulators, or a project
champion appealing to a senior manager, you have to "sell uphill" from time to time. Persuading
decision-makers who have some kind of power over us is a challenging task. How can we prepare the way
for success now and in the future?
- Achieving Goals: Inspiring Passion and Action
- Achieving your goals requires both passion and action. Knowing when to emphasize passion and when to
emphasize action are the keys to managing yourself, or others, toward achievement.
- Deciding to Change: Trusting
- When organizations change by choice, people who are included in the decision process understand the
issues. Whether they agree with the decision or not, they participate in the decision in some way. But
not everyone is included in the process. What about those who are excluded?
- The Risks of Too Many Projects: I
- Some organizations try to run too many development projects at once. Whether developing new offerings,
or working to improve the organization itself, taking on too many projects can defocus the organization
and depress performance.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenBLqrMJlydRnczIbkner@ChacfswHhFqdrKrVPCTmoCanyon.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
- 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 an upcoming date
for this program:
- 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 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's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England 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.