They'd been at it for an hour, and Chuck was convinced that agreement was still out of reach. Geoff and the people from Diamond Square wanted to ship immediately and deal with any remaining problems in the field. Chuck and everyone else wanted to spend a little more time finding out how bad the problems were, and then make a more careful go/no-go decision. So the meeting was stuck.
Chuck offered an idea: "Why don't we all take a break and return at half past? Maybe get a bite to eat and if we come back refreshed, we might find a compromise."
Geoff quickly replied, "Not on your life. I've had enough dithering and stalling. Let's keep going until we decide."
By labeling Chuck's suggestion "dithering" and "stalling," Geoff hoped to devalue the idea. He used the power of naming not to advance the group's effort to resolve its differences, but to characterize Geoff's suggestion so as to devalue it. If he wins his point by attaching a one-dimensional name to the rich, open-ended tactic of taking a break, the team could be deprived of a possibly fruitful resolution of its impasse.
Abusive naming
tactics are
surprisingly commonSometimes, naming hurts.
And it's a tactic that many abuse. Over the next week, you can take an inventory of naming tactics in your organization. Once you start watching for name abuse, you'll be surprised at how common it is, and you'll be less likely to do it yourself.
Here are some typical examples of naming that can hurt.
- Analysis paralysis
- This name can end thinking and discussion when used like this: "Let's not get stuck in analysis paralysis." Another favorite term is "over-analysis."
- Rushing and haste
- By calling the resolution to act "rushing" we can halt action: "Let's not rush into this." Another form: "Let's not be so hasty."
- Bureaucratic micromanaging
- Labeling regulation and controls as bureaucratic micromanaging can cause an organization to abandon responsible and necessary controls. Not all controls are bureaucratic. Not all management is micromanagement.
- Human capital, Human resources
- By using the same name for people as we use for trucks or copy paper, we dehumanize the people. This makes it easier for us to make decisions that trouble us morally or ethically. If you call people "people" you're more likely to take your own values into account.
Labeling someone's ideas or behaviors, as Geoff did above, can be especially destructive, because we can hear the label as if it were applied to us personally, rather than to our ideas or behavior. Anger and defensiveness can follow. If you notice someone using these tactics on you, inhale, then exhale, and only then respond. Reminding yourself of your own humanity helps you forgive the namer and deflect the name. 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 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 Emotions at Work:
- Never, Ever, Kill the Messenger
- If you're a manager in a project-oriented organization, you need to know the full, unvarnished Truth.
When you kill a messenger, you deliver a message of your own: Tell me the Truth at your peril. Killing
messengers has such predictable results that you have to question any report you receive — good
news or bad.
- Reverse Micromanagement
- Micromanagement is too familiar to too many of us. Less familiar is inappropriate interference in the
reverse direction — in the work of our supervisors or even higher in the chain. Disciplinary action
isn't always helpful, especially when some of the causes of reverse micromanagement are organizational.
- Responding to Threats: III
- Workplace threats come in a variety of flavors. One class of threats is indirect. Threateners who use
the indirect threats aim to evoke fear of consequences brought about not by the threatener, but by other
parties. Indirect threats are indeed warnings, but not in the way you might think.
- Not Really Part of the Team: II
- When some team members hang back, declining to show initiative, we tend to overlook the possibility
that their behavior is a response to something happening within or around the team. Too often we hold
responsible the person who's hanging back. What other explanations are possible?
- Directed Attention Fatigue
- Humans have a limited capacity to concentrate attention on thought-intensive tasks. After a time, we
must rest and renew. Most brainwork jobs aren't designed with this in mind.
See also Emotions at Work and Effective Communication at Work for more related articles.
Forthcoming issues of Point Lookout
- Coming April 3: Recapping Factioned Meetings
- A factioned meeting is one in which participants identify more closely with their factions, rather than with the meeting as a whole. Agreements reached in such meetings are at risk of instability as participants maneuver for advantage after the meeting. Available here and by RSS on April 3.
- And on April 10: Managing Dunning-Kruger Risk
- A cognitive bias called the Dunning-Kruger Effect can create risk for organizational missions that require expertise beyond the range of knowledge and experience of decision-makers. They might misjudge the organization's capacity to execute the mission successfully. They might even be unaware of the risk of so misjudging. Available here and by RSS on April 10.
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
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.
- More