Characterizing is a rhetorical tactic used for evaluating a person, event, or concept. For example, "Let's not make such a big deal out of this decision," is a way of disagreeing with another's approach to making the decision not by critiquing the specifics of their approach, but by labeling it as a "big deal." To characterize is to devise a description, usually a judgmental one, for evaluating a person, event, or concept. Because characterization often serves to support the speaker's preconceptions, it's a popular debate tactic that can lead to making decisions on bases other than the merits of the question.
When we characterize pejoratively, even if accurately, the person characterized, or the proponents of the idea characterized, can feel personally attacked. They might retaliate later, if not immediately. And the targets of that retaliation can be anyone or anything. Pejorative characterization is risky.
But characterizations can cause trouble even if not pejorative. In private settings, positive characterizations can be harmless, or even constructive. But if a public positive characterization is comparative, it can offend others. For example, "That's the most brilliant idea we've heard so far," praises that idea, while simultaneously and implicitly characterizing the other ideas as less brilliant.
Some try to mitigate the risks of positive comparative characterizations by means of carefully worded hedges:
- "That's a brilliant idea — no idea we've heard so far is more brilliant."
- "Robert is a great team player. None better."
These hedges explicitly eliminate the implication that the alternative ideas are less brilliant, or that the other team members have less team spirit. While the intentions of the speaker might be laudable, hedges are ineffective, for two reasons. First, the person being characterized, or the proponent of the idea being characterized, often does hear the hedge, and does notice the faintness of the praise. And second, ironically, most other people don't hear the hedge. They often feel attacked anyway.
What can we do about this? Begin by accepting that there's no place for public, pejorative characterization of people, their behavior, or their contributions. Constructive, critical commentary is helpful, if delivered privately, respectfully, and with permission. But how can we offer support for good ideas, or commend constructive behavior, without characterization?
One There's no place for public, pejorative
characterization of people, their
behavior, or their contributionsapproach that limits the risk of giving offense is to focus not on the person, or their contributions, but on the consequences for organizational goals, while avoiding comparisons. Examples:
- "That suggestion could lead to big savings in maintenance costs."
- "When Robert stepped up after the server crashed, he really helped us avoid a catastrophe."
In these forms, we avoid directly commending the personhood of the contributor. Instead, we commend the outcomes of the contributions, which avoids devaluing by implication any other contributors.
Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrenmljxwgBJoMKFPPBZner@ChacnKzGlBXqsiddtTCUoCanyon.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 Conflict Management:
- Shining Some Light on "Going Dark"
- If you're a project manager, and a team member "goes dark" — disappears or refuses to
report how things are going — project risks escalate dramatically. Getting current status becomes
a top priority problem. What can you do?
- 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.
- Obstructionist Tactics: II
- Teams and groups depend for their success on highly effective cooperation between their members. If
even one person is unable or unwilling to cooperate, the team's performance is limited. Here's Part
II of a little catalog of tactics.
- A Critique of Criticism: I
- Whether we call it "criticism" or "feedback," the receiver can sometimes experience
pain, even when the giver didn't intend harm. How does this happen? What can givers of feedback do to
increase the chance that the receiver hears the giver's message without experiencing pain?
- OODA at Work
- OODA is a model of decision-making that's especially useful in rapidly evolving environments, such as
combat, marketing, politics, and emergency management. Here's a brief overview.
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 rbrenmjiXBCyxJzyTUgWyner@ChacNLSnkQEIghjKdRTRoCanyon.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.