Discussion Locked

training to be proactive

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

A member of my team has been working extremely hard over the past few months, he is hard working, approachable and always has a good sense of humour. He has not been properly managed - he seems to have developed a purely reactive approach to everything he does.

I want to help him to become more proactive, e.g when relocating an employee from one department to another he will forsee problems with email, new printers, different file shares, different software required, different phone extension number. At the moment he just jumps in at the deep end and fixes whatever problems come up.

He also very rarely finishes a task completely because he doesn't put himself in the shoes of the end user so doesn't antipicate their problems. i.e. he may set up a piecs of software under the admin account without testing it with the users account.

This approach is part of his personality but is really effecting his productivity. I can't trust him to complete a task so constantly have to check up and have also had to resolve issues myself that he has not completed. The majority of IT personnel i've met have an analytical and methodical approach that they naturally apply to tasks such as the above.

Is there a general method to problem solving or that I can try to train him in? or is there any advice anyone can give to help me get the most from this employee?

36 replies

by softcorp.us

Hello...

This is one of the difficult parts of managing people because it takes so much time and effort to turn around. This employee's job involves taking care of a lot of details on his own. Essentially, his work method is severely flawed and is not doing his job well. It will take significant time from someone to coach, teach, and train him out of this.

A big part of his job _IS_ reacting to problems. But, the problem is that he is not preventing problems that he could and should prevent. That should be the focus: Drawing the distinction between the two.

My suggestions:

- Essentially, he is failing to perform. There is no other appropriate way to say it. Effort does not equal results. You appreciate his effort, but his results are not up to par. He must improve. He needs to be on a formal (written) performance improvement plan.

- He deserves complete clear communication so everything should be in writing. This will greatly help him improve if he is willing and able to do so. And, it will be documentation in the unfortunate event you must choose to terminate him.

- Establish with him that he must prevent problems before they happen. The goal is "zero defects" after he makes a change or completes a task. He probably won't understand this at first.

- When problems occur, review each one in detail. Pass judgement on whether that problem should have been caught by him through his work process before the user (customer) caught it for him. Keep statistics.

- From the beginning, there should be a measureable unambiguous performance objective defined and a date for it to be achieved. For example, a maximum of "N" problems per "M" changes by 6 months. The goal should be challenging but reachable for him. It sounds like you should plan on doing it again with him during the during a second period of 6 months (or whatever).

I hope this is helpful to you. Good luck!

-----Steve

by searchy

Thanks for your response, this is very helpful. It's reassuring to know that this is not an uncommon problem and that there is a way to try and resolve it. We are currently putting in a help desk system that will ensure he recieves written details of each task - this has the benefits of beaing able to measure performance and generate stats. I'll also communicate with him via email, and I too prefer written communication from other to myself.

Working out the amount of problems that occur because of changes also sounds like a good idea.

Thanks again!

by why me worry?

who expect me to be some superhuman psychic and predict every little thing that can and will go wrong on the network. Granted, some things can be caught early on and prevented from escalating into an all out hellish event, but when you have hundreds of servers to manage, you cannot sit all day long and stare at every console because that simply will not work. Even products like HP Openview, which are supposed to catch SNMP events and alert to potential problems, are not 100% perfect. I can understand that as a manager, you expect more from your employees, but I have had this same dilemma with my own manager who expects me to be Miss Cleo and predict every friggin potential server crash. Some managers simply will never be stasified and expect everything to work 100% and never have problems. As I.T. folks, we can only be proactive after being reactive to prevent such an event from occuring in the future because nobody can predict or forcast what might happen to a particular system, no matter how good one is. I agree that one can be proactive, but you have to have realistic expectations of people and not demand things that are not humanly possible or completely off the wall.

by cuteelf

I remember this stuff from a supervisory class I had to take.
Gawd I hated that one :) but I see some of it here.

I also remember...
Make a plan (as above)
stick to it (as above)
have a date for ending
go over results with that person/date

Is it possible that there are no policy/procedures on HOW TO DO X when he has to do X?
It sounds liek someoen is sending him to do a task but he forgets parts of it.
If he has a checklist to himself (not to create more paperwork) he may understand it better.
Heck, why not have him "create"the check list before your eval/training program, and have him create one at the end...see if he sees the difference?

CuteElf

by bhunsinger

Sounds like someon trying to do too much too fast. If the manager has a checklist or a policy proceedure for reaccurring tasks, it helps a LOT. The post about he is not performing- ack. His attitude is good and he needs to be trained/given tools to be more effective. That is a managers job. He may believe that he is being evaluated on how many tickets he closes, not on how well.

by j.lupo

I have to agree with Steve. This is the best way to work with both poor employees and good employees.

When I was managing large projects I had these types of plans for everyone on the project including the consultants. I had everyone help write their own. That is, I worked with each member to develop a personal plan that algned with our project goals. Since I worked on all of them with each member, I was also able to include ways the plans would support each other.

This also, gave me the opportunity to keep a check on performance without affecting the project too much. If an area became troubled, I could see it sooner and evaluate why. By including the people in building the plan, I achieve "buy-in" and varying levels of ownership and accountablity of success.

I think it is commendable for anyone to actually put the time and effort into helping their employees succeed. I think, and this is personal opinion, that most people want to succeed. We as managers/leaders need to provide them with the tools to achieve that success.

by synthetic

I do agree the an important aspect for each of the employees you manage, is goal setting with follow-up. Based on years, initial goals, interim report, and year end review. This allows for measurable progress on areas the employee is either deficient, or in areas you both would like to see growth in. Just apply any new process to all employees in kind. You have to look at yourself as well, your the manager, so where are you failing this employee, and you clients? Again, my humble opinion, take it slow and focus on what works with this employee. Sounds like a positive person who just needs some positive coaching, not threating paperwork (sign off on these or we have documents to fire you with will most likely not go over well with most employees, especially those a little left of center).

by j.lupo

360 degree feedback. It works great as long as people can accept constructive critism and objective reviews. I have a manager that admits he can't take any kind of feedback.

by jkaras

In my opinion the documentation that you are talking about only facilitates termination to get your ducks in a row. If you want your employee to truly improve then dedicate ample time to train properly with a set standards of quality of work. Documentation only puts fear in the individual on the premise either shape up or ship out, trust is not established and sometimes the person worrys too much on failing that they dont perform adequately.

Sometimes I see people all wanting to be the boss but dont want the responsibility to have to work hard when making the decisions, that making the decisions are a bother. If you are management you get paid to handle this responsibility and no magic trick is going to simplify the issue or make it go away, that is why you get the extra bucks, not just techinical expertise. I definetly applaud the original poster in his desire to improve his employee, that is a rare person to find nowadays. In short, nobody can have an uber employee, just an employee that is stimulated the proper way to enhance better productivity, there is no cookie cutter method, just proper guidance and respect hands on than criticising from a distance. Make the investment personally not through documentation, just an opinion.

by softcorp.us

I have to disagree.

"...the documentation...only facilitates termination to get your ducks in a row...". Sure, it does that. But, terminating people is part of a manager's job also (the most difficult and undesirable part). S/he (the manager) _should_ have his/her ducks in a row. If the employee is doing the job, there won't be a problem. What do you do if the employee is not doing the job well enough? You must communicate clearly what needs to change. You must be fair to the employee. You must put your thoughts in writing.

"...set standards of quality of work..." This must be done formally (in writing), not merely verbally, especially if the employee is already not "getting it" as in this case.

"...trust is not established..." It all depends on how it is done. The employee may not like it much, and may not even agree, but s/he can trust a manager who is honestly critical of him/her. More importantly, the focus of the performance improvement plan is to help the employee improve. That will be clear if it is done correctly.

"...sometimes the person worrys too much on failing that they dont perform adequately..." If this happens because the boss is intimidating, then you have a point. If this happens because the employee is just not "getting it" and not "doing it", then this is not a valid point. It's the employee's job to do the work. If s/he can't do the job due to fear of failure, s/he shouldn't be there.

-----Steve

by jmgarvin

I hear the Madam Cleo School of IT is offering both the CPSE and CPSA certs. You have to have your P+ cert along with your CCPA (Certified Cleo Pychic Administrator)

by softcorp.us

Hello RZ...

Your situation as you describe it is very different than the one SEARCHY described and I replied to in the following important ways:

- SEARCHY is a caring manager who wants to help this employee perform better: "...I want to help get the most out of a valued employee...." and "...I want to help him to become more proactive..."

- SEARCHY describes an employee who is obviously sloppy: "...he may set up a piece of software under the admin account without testing it with the users account....".

- YOU said your manager expects you to "...predict every friggin potential server crash..." and "...Some managers simply will never be stasified and expect everything to work 100% and never have problems...". SEARCHY did not describe anything resembling this.

- YOU said "...you have to have realistic expectations of people and not demand things that are not humanly possible or completely off the wall...". What is not humanly possible, unrealistic, or off the wall about checking a software installation using the user's account to be sure it actually works? Not doing so is sloppy and completely unacceptable.

- I said "...there should be a measureable unambiguous performance objective defined..." and "...When problems occur, review each one in detail..." and "...Pass judgement on whether that problem should have been caught by him through his work process before the user (customer) caught it for him...".

This is open, fair, and honest coaching, teaching, and training. If this employee is worth keeping, and I suspect s/he is, this will bring about great improvement and everyone will be happy about it. There is nothing "superhuman" or "psychic" or "Miss Cleo" or "never be satisfied" or "never have problems" or "unrealistic" about it.

As for you, I suspect that you work in a high pressure environment and have very poor management. I suspect there is little coaching, teaching and training and lots of demanding, threatening, imprecise criticism, and unmeasurable informal goals. If true, I'm sorry for that and understand where your poor attitude comes from. You should look for a better job.

Best of luck on your job search!

-----Steve

by synthetic

Before making a worse case out of this employee by going over board, consider a few options. One, considering the type of person and personality, is it possible that this person is just not in the best position? Sound like he is capable, and competent, has a good attitude, and a healthy work ethic. First, instead of trying to change this person, is there a position his temperament maybe better suited for? If not, before you hurt this persons feelings, or throughly dampen their positive attitude, consider some lesser alternatives, not just over blown step by step plans with performance enhancements and day metrics for analization and follow-up; there will always be time to move to that later if need be. Different people respond very differently to the same actions, this is also a part of management, not taking the same model to every situation. First, a checklist would be a good start. When migrating a user from one account/PC to another. Verify PST, ensure secondary software works without disk and under clients account, etc. Do not be to forceful, just make sure he understands there is a process, and nit needs to be applied each and ever time. Explain he is there to mitigate issues, and each time he is at a work station, he should not only look at the job at hand, but potential issues with both the current item, and any other issues that might be mitigated from the system at the present time. Train him to look beyond the current situation, without to much paper work, or spirit crushing over sight. Try this for a few weeks, and then adapt and make changes. If I know this type, which sounds very much like I have been, then you have the potential for a great employee; however, like me, a uber authoritive approach, might just back fire, and leave you both wanting. Again, there is always time to be more aggressive and assertive in your approach later.

by synthetic

people who state they are incapable ( translated=unwilling to learn or even try) of something, they know is important, as though you just need to live with it, even though it is their short coming. Instead of the person being humble, they wear it like a badge. In the instance of a manager who states they can't take feedback, this person should realize it is their job, and they will only grow by learning such skills. How does this person expect to field a strong, positivity team, as well as learn and grow, if they can't/are unwilling to hear both accolades and irritants?

by j.lupo

He is one of the reasons, I am back on the market looking. Including the fact that my contract is up. I had a big lesson learned with this contract. Everything looked wonderful when I signed on, then I learned that they don't want a knowledgeable worker- especially a female who supports their position with good backup - technically.

They flat out told me they feel I am too opinionated (for asking questions, and taking a stand on solutions I recommend). They actually gave me an example of expected behavior which is the only other female in the office who is very submissive, never speaks up, and basically is a yes person. During this conversation was when he mentioned how he envied my ability to accept feedback, and that it was his weakness that he couldn't. Ugh.

At any rate, I try my best to remain professional, do my job to the best of my ability (or as far as they will let me) and continue to hunt for the right "home".

by why me worry?

I can relate to what you are saying because I have seen women in such situations where they were expected to follow the stupidity and ignorant culture of the bandwagon. The whole notion that they expect you to be "submissive" is disgustingly cheuvanistic on their part and comes dangerously close to them commiting what is known as "sexual harrasment" in the workplace. Sexual harrasment does not need to be physical or verbal intimidation of sexual nature. Just the fact that they expect you to act like Susie Sunshine and be "submissive" and not challenge their decision or authority says quit a lot about their own insecurities and confidence. I am not a pyshologist and do not claim to be, but what I have noticed is that the managers who are the worst control freaks are the ones that have deep seated self image and low self esteem issues, so they have to yell or intimidate others to get a feeling of empowerment. Control freaks are a sign of weakness and cowardness. Do not back down and certainly do not to be afraid to voice your opinion and concerns. This is the U.S.A., not the middle east, and women in my book should demand the same respect and equal treatment as men in any workplace. More power to you!

by j.lupo

It is cultural here. The department has 2 women (I am US, the other is from India), 4 US men, 12 men from India, 1 man from China.

I recognize the issue for what it is. I just deal with it and move on. I will always do my best to keep my professionalism. I appreciate the suggestions and the encouragement. It helps on the days when I am really getting "picked on". :)

by dc_guy

I've helped a lot of subordinates improve over the years but your question stumped me. How do you turn a reactive person into a proactive one? A lot of good suggestions were offered but not many really responded to this central question.

I think it's a basic personality trait. Probably difficult to change but not impossible. I'd still be interested in specifics on how to help someone with this.

IT departments have always been criticized for being reactive. It stands to reason that the people they attract would be reactive by nature. They would drive a proactive person nuts.

by j.lupo

I have seen this work where we did what Steve suggested. We developed personal improvement plans and goals. We cross-trained like crazy and did a lot of design/analysis sessions. Slowly these went down in number, because the person got the idea about seeing how things could happen before they happened.

One thing I have always encouraged in my developers is: if you see something that could be a problem, don't wait to fix it. If you aren't sure ASK, if you are sure fix it.

Now obviously, company policy and procedures have to be followed, but encouraging and rewarding people for proactive behavior motivates them to continue that behavior.

You know it reminds me of the commerical I have seen lately on TV. There is a sink with water running and everyone in the room keeps looking at it and making suggestions, but noone does anything. Then someone walks up and just turns it off.

by softcorp.us

Yes! You get have the concept.

In the end, it is up to the employee to "get it", "want it", and "do it", or not. Given the appropriate environment and encouragement, most employees will respond well to the kind of thing I suggested.

The main purpose of doing this in writing and being measurable and unambiguous is to be clear. The employee deserves a fair shake at getting it, wanting it, and doing it. It's the managers responsibility to communicate clearly. That is best be done in writing, especially when there already is a problem as in this case.

But, termination is the manager's job also (the worst part actually). How many managers have you seen over the years that don't terminate people who should be terminated, or when they do, they do it in all the wrong ways?

As a manager, you need to do the work to document what is needed and set unambiguous measurable goals with dates for achievement. After this, if the employee is not getting it, not wanting it, and not doing it, it is the manager's responsibility to send him on his way.

-----Steve

by jmgarvin

Try to mentor him as a person that really cares about how things are done. Have him "help" you write a SOP on how you should do the general tasks of the IT department.

If that doesn't work you should do performance evals and make sure he understands what is expected of him.

by zlitocook

If you do things the same way for each department make a check list for things that have to be done. It may make some IT mad but with a list if some thing is not done you can come back to the person and show it to them. After awhile it will become a proccess and not need to be looked at. If this dose not work, look at what this person has going on. I have seen this before and found that he was given more then he could handle.

by bevmillar

There are lots of templates for checklists and policy and procedures, and completing them (online) and saving them for performance reviews works. Documents if the employee just needed guidance or a different type of job.

by j.lupo

Yes it is the hardest and the scariest at times. I have been fortunate. I only had 2 occurances in 20 years of IT work where I had to terminate someone. The first person, the company wouldn't let me do it because they were afraid he would hurt me. He had some sort of issues, but I felt it was my job.

The second person was at a government job. The manager didn't want to do it, she wanted to transfer him to another department. I suggested the PIP (personal improvement plan), with the stipulation that if in 6 months he didn't improve, then we needed to terminate not transfer. She gave me the job. So, six months later after really trying to help turn this guy around I fired him. He wasn't happy, but he couldn't say "WHY?".

by maxwell edison

.
My philosophy is to hire (and retain) for attitude, and train for skills. It's extremely difficult to train someone, generally speaking, to have a good attitude, regardless of the strength of his technical skills. (Although it can be done.) But if you have a person whose attitude is as you describe (hard working, approachable, good sense of humor, etc.), he's worth keeping, he's worth training, and he's worth helping.

Someone else in the thread mentioned the idea of a checklist. I think that's a great idea -- and it's a tool we use as well. A checklist really serves two purposes. It makes a person think about what needs to be done under certain circumstances, and it helps get the tasks completed. When, for example, you're relocating an employee from one department to another, you always have to do this, that, and the other thing, each and every time. Writing the checklist (and let him do it, by the way) will force him to think ahead. And make it very detailed. One item on the checklist, for example, can actually have subsets of more things to do. Using the checklist in the process of working on a task ensures it all gets done, and perhaps at the right time and in the right order. (Creating the mail account on the server first, for example, before configuring the client email software.) And a checklist doesn't have to be set in stone, so to speak. It can be a growing and changing document that's refined over time. He can use it as both a thinking and planning tool, as well as a completion tool.

You can also help him with his approach to things, and it sounds like he'd probably be receptive to suggestions. When you said, "he doesn't put himself in the shoes of the end user so doesn't anticipate their problems", the first thing that came to mind is one of Stephen Covey's habits of effective people, seek first to understand, then to be understood. Although that habit in Covey's context is generally applied to communicating with people, it can certainly be applied to technically helping people as well, especially in one's approach. You might even buy him the book and help him refine those kinds of skills as well.

Praise him for what he does well, and help him do it even better. Working on those strengths to make them stronger is what's needed. Like I said, if you try working with someone whose weakness is his attitude, it could be a losing proposition. But this could be a real winner for everybody.

I'd help this guy as much as I could - take him under my own wing and help him fly. You'll both be better as a result.

by why me worry?

Look at yourself in the mirror if you don't know what I mean. I have no issues with authority figures, but some authority figures, such as managers, think they are "know it alls" and get defensive or offended when their decisions are questioned or their asses are not being kissed by their subordinates. As IT pros', we are not robots or slaves, we are human beings fully capable of reason and logic and our opinions count too, whether or not management likes what we have to say. I will not allow any company or manager to dictate to me how I must carry myself professionally or what "opinions" I should have. If you want mindless employees who will kiss your ass all day and not challenge your authority, I suggest you hire trained chimpanzees instead of human beings to work for you.

by bmedlock

I've been reading a book by Stephen Covey titled 'The 7 Habits of Highly Effective People'. It's about geing an effective 'leader', whether that be manager or CEO. The first 'habit' is 'Be Proactive'. I suggest you get a copy, read it, and do it. I think the principles found in this book will help you inspire your employee.

by jkaras

I do get your point of view, but I just disagree with the excuse that writting form solves all problems. In my opinion documentation only benefits the employer not the employee, there never is positive documentation, only negative. In today's world is if it written down somehow there is absolute validity, when not all documentation is completely factual or non biased yet it is accepted as so. What if a manager abuses his power and writes anything he wants and twists the facts to facilitate an agenda or to cover their butt? Counselings are done one on one in private and any words exchanged are not witnessed by others, so who's words get taken and whose gets dismissed? The employee cannot seek legal counsel because there was no witness and some sort of documentation from one point of view only is presented as fact to absolve liability.

Yes I agree that documentation is needed to weed out workers who refuse to do their work, but it is not used professionally in the intended sense in most cases. Today the American work force has zero trust in employer and employee because everyone is looking out for themselves, hiding behind the me factor. As a result our quality of work has gone down and documentation isnt helping. You can ruin someone's reputation over it and possibly hinder their possibility for success. Trust is established through a mutual investment in eachother, that's teamwork, not hiding behind a mantra of we are a team, but nobody wants to be apart of. I see things like a parent giving guidance to their child. Does a parent write everything down for record and continually punish? No there is give an take with a desire to improve the child, not well its just too much work, so I'll trade up. How about a sargent that cant effectively train a private, its the sargents job to prepare the individual with a never say no attitude that determines his fate. I know these are abstract examples but the overall message is that both decided like a manager to take on the responsibility to improve another through their experience, knowledge, and wisdom to make the other a more capable individual. Who you are today is a representation of the amount of concern people invested in you to be more, because they choose to accept that responsibility. The is regardless of talent or intelligence factors, everything can be learned and armed with proper guidance, the skys the limit pending on your determination. To lead is more than making decisions, its a responsibility and management is paid extra to make that happen, they promise to team lead, be respectful, be fair, and unfortunately most get drunk with power thinking that their position at work makes them un accountable or above reproach. If their employee fails, does the manager take any blame for not properly preparing the employee, that he/she isnt a reflection of the managers leadership skills?

Not all these scenarios turn out this way, its works both ways, and I conceed that point, but it isnt all that its made out to be is my point. What the workforce needs to get back on track in my opinion is the human factor, then the U.S. economy will flurish till then we will just flounder in mediocrity.

by joetechsupport

Communicate with him.

Wow! I would have killed to have a supervisor like you. Both you and he are in luck and can look forward to a productive and friendly working relationship.

Speak with him.

If what you say about your tech's personality is true and if you are as honest, open and non-threatening to him as you are to us while showing how he can improve he should be pleased to receive you.

Just tell him how you want to help. Done the right way, no problem.

There are some schools that say do not tell employees directly, instead deceive them by dropping hints and suggestion strategically so that the employee develops the belief that they thought of the idea themselves.

This is not only a waste of tame but an insult to to any IT tech worth their salt's intelligence. And yours. The guy sounds clever. Do YOU want to treat him like an idiot? I'm not speaking to you,sir, but the argument.

He will be as pleased with his improvement in proactivity as you are. Your rapport will improve.

A respectful use of psychology- if your office clears out mostly after office hours and its common to see you and this fellow still around at this time talk to him then. If he's on his own time, pay him OT if you can, It's a meaningful gesture for 1/2 to 1 hour. Outside of office hours doesn't spark the office rumour mill and put him out of ease. If there's lots of empty private space like a learning center try out of your office for neutral ground.

Speaking from experience, often all that is missing is some human and technical mentoring.

People may know how to format a hardrive, add a user account etc. People may not be clear on what is expected. In fact I can almost guarantee he's not clear what PRECISELY is expected.

To very many people, very busy=OK. Free time=out the door. That my be all he is concerned with, that he keeps busy.

The other thing that is missing in most relationships be they familial, working, romantic or friendly is empathy. Not feeling sorry. Understanding, knowing and owning the others point of view.

There is so much of the "BS-management-assert-yourself-start-motivation-drive- start-running-the-company-in-3-months-you that he may be thinking more about that or his job security than keeping his mind on his work.

But he's luck, he's got you, one of the few and far betweens, you can help him settle down, IF he turns out to be a little nervous.

Communication is the most imoportant. Everyone talks about it, but few practice it between hiring and firing.

by maxwell edison

.
You replied to RZ's message, but addressed a manager/boss. RZ complains about managers, but is not one himself, at least not that I've gathered. As a manager/boss, myself, I agree with you 100 percent. In fact, I've even mentioned (and read) that book myself, and on more than one occasion:

https://www.techrepublic.com.com/5208-6230-0.html?forumID=7&threadID=172857&messageID=1760210

Personally, I almost live by those 7 habits, at least I strive to, and urge others to do the same.

But RZ, in my opinion, and from the attitude I've seen him display, is a cocky, know-it-all, smart-ass of an employee who wouldn't know a good manager if he/she came up and bit him in the butt. Read his messages (in multiple discussions) and you see evidence after evidence of how he doesn't apply any semblance of those 7-Habits. And he's the kind of guy who might read Covey's 7-Habits, but would think how other people could use the advice, not applying it to himself. My advice to him is to read the book, apply the habits to his own way of thinking, and shed the stinkin' thinkin' attitude.

I've had a few "RZs" come through my department, and they're all the same -- the complainers and negative thinkers who try to spread their poison; the "know-more-than-everybody" attitudes, but who always seem to wallow in mediocrity; the "don't expect too much from me" people who always think that giving 110 percent is tantamount to being dumped on; the "me-first" and company second people, and the back-stabbers who always seem to resent other people's efforts.

But then I've had scores of the others. I can't begin to tell you how many people have come and gone from my department, not because they were moved out, but because they were moved up. My job, in many ways, is to help them excel and advance within the company, I'm a manager and a trainer -- and I do a pretty good job. I hire a lot of young people right out of school, and I'd say that 9 of 10 people who have worked for me over the years have either been promoted and moved up in the company (with my urging), have grown and moved on (and up) with another company, or have been content to stay where they are, just doing what they love doing, not really wanting to advance. I treat them all with the utmost respect, help facilitate their goals and aspirations, and help with both their technical growth as well as their personal/motivational growth.

But then there's always the 1 out of 10 "RZs". I don't waste my time on such people. It's not fair to the other 9.

RZ, some advice for you: Seek first to understand, then to be understood.

by j.lupo

Yes that is one of the really good books. Of course I like Bennis for a lot of leadership information along with Max Dupree and a lot of others. Has anyone read S. Collins "Good to Great"? Interesting book.

by greenhouse

I agree with joetechsupport, the key is to tell him the truth in a clear but constructive manner. What has always worked for us has been having a meeting after a problem has been fixed and discussing how we might have anticiopated the problem. If we could not possibly have anticipated it then being reactive is the correct course. But a good discussion about what we may have overlooked or missed helps us not do the same thing the next time. Elicit answers from your employee, he should be the expert on the situation. Partner with him and he will learn to adapt to this new way of thinking. I also find that formal analysis beforehand of risks can help mitigate many problems.

This discussion is closed to new replies.