Discussion Locked

The employee who is never wrong

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Question: How to deal with an employee (in this case a db developer/admin) who can never admit that he may have done something wrong.

Scenario: Yesterday, our test web server suddenly would no longer authenticate our test users. We went through the usual things to check and then checked more. Everything looked ok on the web server and on the database server.

During the whole time, he kept going on about how everything is ok and there "shouldn't be a problem." But there was!

Finally, this guy admitted that he had installed a MS security patch and rebooted the test server at about the same time that the trouble started. (Why did it take him two hours to mention that?) I checked the event logs and found that some of the services did not restart properly when the server came back up. After restarting the services, everything returned to normal.

I tried to explain to him that he needs to check the event logs after a reboot, but he insisted that the services were running because Enterprise Manager (for whatever reason) showed them as running.

Of course, he took no responsibility and blamed the problem on the patch, on EM or anyone else. His entire approach during the whole time of the troubleshooting was negative. This exemlifies his personality - or at least the way he comes off.

Note: He's from eastern Europe and perhaps this could be part of the way he was raised or his native culture. In any case, it's not the way we work and it's not productive.

I'm his manager and I don't appreciate his approach. Oddly enough, nobody else seems to mind.

Any thoughts?

16 replies

by jamesrl

When I first started to do post mortems at my previous employer I ran into this constantly.

You have to set a reasonable expectation. You have to let them know that your purpose in asking the question is to improve, not to lay blame. This is a an emotional gut level issue. Your guy probably lacks confidence. He needs to hear that you understand that things happen.

James

by dafe2

Yes, if you don't "coach" them through how to deal with failures they will never learn.

Coach them through speaking up right away. Help them understand the only mistake is not taking ownership of it to begin with.

by packratt

it's usually an ego thing... Many, not all, IT professionals have some rather big egos, just take a look at the discussions here and you see them insist that other IT professionals who are out of work must be inferior to them and you see a lot of flame wars erupt from simple disagreements.

For an IT professional with a large but fragile ego to admit error, especially one based in a lack of knowledge, is very damaging to that egotistical psyche, almost to the point that so much self denial will occur that the person will convince themselves that they didn't make a mistake when they knew they did in the first place. (the repressed Doh! syndrome I like to call it as I've watched people jab at keys in desperation after making mistakes and shouting expletives only to later deny it happened when there was nothing on the line in the admittance of such a mistake.)

We are all human and can never know all that there is to know, even the self proclaimed "IT Gawds" make mistakes. Humility the fundamental teacher as learning starts with the acceptance that there is something which we do not know.

by oz_media

This is such a basic human reaction it cannot be discounted as a cultural difference.

Some people have worked in positions where credibility is everything, they are built on pride. Perhaps he has worked with IT teams where th entire day is a pissng contest? Some of these code junkies get pretty internally competitive, it is just a poor social skill.

He may have so much pride that he just didn't feel comfortable admitting fault. He may have simply been unaware thet the logs should be reviewed, but I doubt it.

It sounds like his ego got the best of him, just learn how to stroke his ego and show that you can easily accept mistakes without the need to impose blame. Not what your post indicates.

Your post shows me you are looking to point a finger, whether a concious decision or not, that's the message shown. Especially when you try and equate it to a cultural difference resulting in some anomoly in his character.

Be OVERLY accepting of people's mistakes when you are around him, once he feels tht he is not going to be scolded or blamed as incapable he will probably open up a bit. I think he was proably repressed somewhere along the line or had a manager/employer who would come down hard on peple for little mistakes. He was probably too scared to admit his fault and hoped it would just be fixed without it showing as his error. In this case it very well COULD be a result of cultural difference where his former employers may be much less accepting, but in most cases I would say it is an ego issue and fear of failure.

Make him comfortable with admitting mistakes by showing how you will react rationally and without pointing a finger or looking to instill blame on someone. You just want to resolve th eissue as a team should. He will get better I'm sure.

by cfk

From the general tone of your question I have identified some issues I think need dealing with.
1. You recongnize the employee is having an issue with accepting responsibility.
2. The employee does not wish to recognize he has caused errors
3. The process of change in your team is not managed well
4. The team, apart from this emplyee, has been working together for a while and understands your approach to situations.
5. The penalty (blame) approach is not working.

To address (and correct) these issues will require some work on your part and your team.
1. You need to take charge of the employee and explain the process of problem identification and rectification. This should be an instruction session, requiring his input to help identify ways of improving the process in future. This will allow him to buy into the process, too.
2. Ask the team as a whole for their feedback on the issues raised through the current issue, carefully explaining that you are looking at the consequences of the issue, not at the causes. This explains to the employee clearly and from peers how actions such as this have a flow-on effect and cause aggravation and problems further down the track. Focus not on the immediate remedial action taken to resolve the problem, but on issues such as lost productive time, cost, and delays to the project. Also, as an exercise ask the team to consider the impact on their personal time as a result of this as it demonstrates that they all suffer. This generally works well to get people to be more responsive.
3. Review how changes are applied to your test systems. They should be as well documented and as tight as a production system. This will ensure that where changes are made and issues arise they can be quickly traced and identified. Ensure that where patches are applied there is a backout plan in place which can be executed later. This is an area you are directly responsible for.
4. Consider your reaction, especially to other cultural issues. You think it may be because this person is from another culture to your own. That points to your indifference to other cultures, even if these have no relevance to the working situation. You need to address this and understand this better if you, as a person, are to progress. I am appalled you do not know enough about this persons background and culture, and have obviously not taken the time to find out. Consider all your team, and see if there is an opportunity to involve them, but start with yourself and lead by example.
5. Rather than seeking to expose public blame, and therefore penalise the employee, consider the reward aspect to finding issues and errors in advance of the fact. This will encourage a more scrupulous approach to development, especially if the reward can be shared between members. These do not have to be big, but they should be public rewards. If an issue does arise consider rewarding the 'finder' based on the time it takes to find it out to a max of 24 hours to find it. After that there is no reward as everyone is suffering, including you.

The major theme I am trying to bring to you here is not that the difference between you and your employee is major, but that your team is apathetic to both of you, and some major changes need to take place to bring them all back to a positive approach as a team.

Think long and hard about your attitudes and whether some of these issues are infact yours for not being as well rounded as your could be.

by fitnut

I greatly appreciate the input of cfklenner and others on this issue. Your comments are very insightful and I take them seriously.

One thing I want to clarify:
I was NOT looking to blame anyone or to penalize or punish anyone. I was just trying to get the problem solved. Even after the fact, when we realized that the reboot and failure to check the event logs was the problem, there was no blame. We just restarted the services and life went on without a negative word.

I do plan on addressing the change control issue with the team when they are all back in the office after the holiday. Your suggestion to tighten the change control on the test system is a good one.

What I AM trying to do is instill an approach to troubleshooting whereby the person responsible for the server (or whatever system is having trouble) thinks "Ok, what's happened recently that may have caused this? Is there anything that I've done that may have caused this reaction? If so, let's see what we can do about it."

I lead by example by modeling this behavior when I myself make mistakes. I just fess up and say, "Gee, I screwed up. Let's fix this."

The problem is that this particular employee is constantly blaming someone else. His entire reaction was to blame either the web server or someone/thing else. He would even consider the thought that the database server that he's responsible for was the problem until all the
arrows were pointing in his direction.

This employee consistently demonstrates this type of negative attitude on other issues, even when I'm not involved. So I don't think it's an issue that he has with me. I hear his negativity all the time.

I'm sure you've experienced those users who constantly and consistently blame "the system" or an application or (especially!) Microsoft for all their problems, only to find out that much of the time it's due to user error.

This is the type of workplace negativity that I'm trying to combat.

Again, I appreciate your comments and I take them to heart. I know that I'm not infallible and that I could improve in many ways. In this case though, I don't think I'm the cause of the problem. I just need to find an effective way to deal with it. That's my real challenge.

by oz_media

"The Employee that was never wrong"

Once upon a time, Tommy the Taylor went down past the tumbly bumbleweeds to open his shop by the big town clock in Fumble Dumbleville.

Here he made shoes and sold contraceptives to the teenage hookers on the corner in exchange for freebies and crack to pass the day away...sorry. Now you know why I don't write kids stories! :p

tee, hee, hee...ahem.... I mean HO! HO! HO!

MEEEEERY CHRISTMAAAAAS EVERYONE!!!!!! :D

by aceskaraoke

I know several 'adults' who might almost have the vocabulary and certainly would have interest in the subject material.

If you just get an artist to draw pretty, and graphic, pictures, you'll certainly become a millionaire.

Unless you just trade the books for freebies and crack to pass the day away...it seems to be all the rage these days.

P.S. Didn't you mean Hoe, Hoe, Hoe?

Merry X-Mas

by oz_media

TR is going through growing pains masking swear words. I typed HORE with a W in front of it and it was masked. A few months ago I called a guy a c**ksucker and it wasn't masked though.

It's a fun game to play and see how many different ways you can spell things to see what is masked and what isn't. Phuque is still acceptable though!
:D

by aceskaraoke

I prefer using well-placed asterisks, if I can't find another word and don't wanna be too vulgar.

by oz_media

I actually made a whole list up (before they added th eedit fesature) and MOST of what I thought would be censored wasn't and what I didn't think would be censored was. Oh well, just fun and games while things are tweaked.

Have fun,
OM

by aceskaraoke

They had trouble spelling "war".

You remember the War of Babylon and how people were always going warring or warring themselves.

That must be it...yeah...that's it.

by vanight

I work in production and we have STRICT hand chopped off change control adherence. Not sure if testing uses this but it might not be a bad idea for a streamlines change control process. This would have prevented this problem before it started. I guess that sorta defeats the purpose of the testing though right?

This discussion is closed to new replies.