The art of confronting an employee whose undermining the team is the subject of this week's Leader's Digest Mail Bag Q & A.
Dear Smart Development,
Mitigating Harm
Dear Mitigating,
Thanks for this interesting and important question. We're often asked how to give feedback to direct reports who act in ways that cause problems. Sometimes these challenging individuals are described as having "bad chemistry" with their coworkers. On other occasions, they're labeled "hard to work with," "troublesome," or even worse. In this case, the individuals in question cause uproars, turn people against each other, stir the pot, and pick on newbies.
As their supervisor, it's your job to do something about the bad behavior. But what?
At first glance, suggesting that the individuals in question cause an uproar or turn people against each other may sound like a description of what they do, when, in fact, these particular words describe the effect not the cause. They behave in some particular way to cause an uproar or turn people against each other, but it's impossible to decipher from these expressions alone which from millions of possible behaviors they enact.
If you expect the individuals in question to improve, they'll need to change their behaviors—swapping out the old and replacing them with new. As a leader, you'll need to adeptly describe, in detail, what they're currently doing to cause an uproar and the other effects you've described.
Describing behaviors requires an understanding of exactly what the offending parties do along with the ability to describe their behavior in a way that is crystal clear. You have to see what others actually do and then metaphorically hold up a mirror so they can see what they need to change.
This can get complicated. When you suggest that the problem employees "stir the pot," the metaphor masks the actual actions they take. If you tell them they "stir the pot," they might know what you're hinting at and change, but it seems unlikely. The same is true with expressions like "picking on newbies." You include a verb that hints of certain behaviors, but alas, also leaves a lot to the imagination.
When I talk with people facing similar challenges and ask them to provide the behaviors (causes) behind the effects or vague conclusion they describe to me, they often can't. Their conclusions are firm: "They constantly stir the pot." That part they feel strongly about, but when I probe for detail, they aren't able to describe the behaviors the other person enacts. They remember their emotional reaction far more clearly than the actions that took them there.
For instance, when trying to help a district sales manager with a salesperson who was "socially backward," I asked for a detailed description of what the salesperson did. The supervisor explained that he was "a nerd, a geek—you know, a dweeb." The supervisor knew what he had concluded about the fellow, and was able to come up with synonyms, but couldn't describe any actual behaviors.
So I asked him, "The last time he did something you thought was nerdy, what exactly did he do?"
"He looked like he had no confidence in what he was saying," the supervisor responded. (Also a vague conclusion.)
"And what made him appear unconfident to you?" I continued to probe.
"He stared at the floor. He started a sentence three different times. He spoke in a low voice. The minute the person disagreed, he backed off even though he was correct . . ." and so forth.
At last, behaviors the other person might be able to recognize and replace. This is what the salesperson needed to hear and correct.
Most of us use shorthand negative adjectives along with vague outcomes when talking with others because such simple expression often works for us. "Quit teasing your brother!" you bark to your son. He knows exactly what he's doing and what to do instead. He knows because you've told him before—focusing on his actual actions. "Yes, I know you said his new shirt was cool, but you said it in a sing-song tone and rolled your eyes—and that appeared insincere."
You've described several versions of "teasing" to your son, so now when he does it, you can address it in shorthand.
However, with direct reports, where we don't have a long history and the specialized code that comes with it, we need to carefully observe others in actions, take note of the actual behaviors that aren't working, share those in a direct and non-punitive way, check to see if they understood us, and then talk about replacement behaviors.
I'm assuming you've watched your direct reports in action and have a whole list of undesirable actions they take, so you're ready to hold a discussion in a way that will be helpful.
Start by holding separate conversations—one with each employee. Privacy is essential. Select no more than one or two of the areas you'd like to talk about. You don't want to overwhelm the other person. Start by describing the undesirable behavior and what you'd like to see instead. Share three or four example actions and take special care to focus on their behaviors, not your conclusions. Share actions you've personally observed—hopefully recently.
Open the conversation for questions. Ask the other person if he or she sees it differently, and jointly develop a plan of action.
Obviously, there's a lot that goes into such a feedback discussion. Today, I chose to focus on one element that can turn a painful and vague discussion into a helpful feedback session.
Focus on behaviors. Become skilled at both observing and describing them. Know the difference between a behavior and a result or conclusion. Help the other person see what he or she is doing, not merely what you think about him or her.
To your greater success,
Peter Mclees, MS LMFT
http://smartdevelopmentinc.com/
No comments:
Post a Comment