Document Behavioral Issues From the Git Go
I was just reading about recent HR litigation and something struck me. What you have to do on a weekly basis to properly manage employees is surprising.
Case in point: Project managers are often frustrated by difficult workers, and allow the problem behavior (or performance) to continue until a breaking point. When they finally act on this festering wound, they are unprepared.
It is so important that you make behavioral notes in problem employee records daily or weekly. Every project. Every week. Think about it: You are going to have to confront the worker eventually, assuming you do not find a way to transfer the employee to a competitor. Who knows what will happen during or after the confrontation? There may be worse behavior, or a lawsuit. The worker may say that it is not a problem and refuse to discuss it any further, blaming you. Any of these things and more.
You need documentation of the facts so that you are not helpless in your proper resolution of this problem. This also gives you confidence when you do take the confrontation step. If you search on progressive discipline at this site, you can get help for this, but you still have to make the time for the documentation and remember to do it.
Maybe I can find time to develop a strategy to transfer problem employees to competitors.
Posted on: April 26, 2007 08:46 AM |
Permalink
Comments (0)
Please login or join to subscribe to this item
Please Login/Register to leave a comment.
ADVERTISEMENTS
|
Do, or else do not. There is no 'try'. - Yoda |



