Bob Lewis
Columnist

Another Mr. Know-it-all

analysis
Feb 14, 20063 mins

Dear Bob ...I'm facing a situation similar to the one Not screaming yet is handling. This guy is an exact replica of George. However, I don't have the luxury of losing him either to another project or to another company. I want to explain him in plain "English" what he is doing to the team by his behavior. Any pointers would really be helpful.- Not screaming either, but closeDear Close ...Plain English? Gee, I'd

Dear Bob …

I’m facing a situation similar to the one Not screaming yet is handling. This guy is an exact replica of George. However, I don’t have the luxury of losing him either to another project or to another company.

I want to explain him in plain “English” what he is doing to the team by his behavior.

Any pointers would really be helpful.

– Not screaming either, but close

Dear Close …

Plain English? Gee, I’d thought I’d been pretty blunt already. But okay, here are some more thoughts:

* You say you don’t have the luxury of losing him to another project or company. That puts you in a weaker position – closer to what the manager of unionized employees faces. I won’t push the point, other than to suggest you ask yourself whether this is really the case or you just would rather not go through the pain of replacing someone who isn’t working out.

* As much fun as confrontation is, the best way to teach is to help the other person figure out the right answer. “So tell me – where do you see yourself as strong, and where do you think you need to develop?”

Listen to what he has to say, and don’t hesitate to respond, “That’s pretty interesting, in particular because, speaking as your manager, that’s the last place I’d have you focus. Before you spend time and energy learning new languages [substitute whatever he says], you need to learn the difference between individual programming and development in a team environment. That isn’t something you learned in your classes, but it’s the difference between being a valuable employee and a liability to the company.”

He’ll likely object that he already knows how to do this. If he does, ask him to demonstrate his knowledge: “Okay, great. Tell me – what do you see as the three biggest differences between programming as an individual and programming as part of a development team.”

If he doesn’t, ask him anyway: “You’re a smart guy. Figure it out. What do you think the differences are?”

When you finally get him to the right answer, ask how well it matches how he’s been programming. Don’t let him off the hook, either. He’ll likely tell you that’s what he’s been doing. Have some of his code handy so you can bring it out, point to it, and say, “This is your code. Let me show you where it doesn’t measure up to what you and I just agreed is the right way to program in a team environment.”

As is always the case, you have to be the adult in the conversation. Be on your guard for whatever might trigger your anger, and whenever you experience it, force yourself to relax and smile. That’s an important part of getting your point across, too.

– Bob