Compare cert salaries and plan your next career move
skrpune wrote: I agree, try talking with the tech first...and if you get nowhere, then move on to talking to your manager. But if you don't feel like you will be well received when you talk to the contractor, or if you're uncomfortable, then go right to talking to your manager. Technically, unless you're in some sort of management role, it's not up to you to address personnel issues (which is what I think this would fall under) so there's nothing wrong with going to your manager first if you want to go that route.
networker050184 wrote: Would you want one of your coworkers going straight to the manager if they didn't agree with what you were doing? I'm sure you would rather them come to you first if there was an issue, I know I would. You should also give your coworkers the same respect you would expect in the work place.
gorebrush wrote: But is he really a "co-worker" being that he is a contractor?
skrpune wrote: gorebrush wrote: But is he really a "co-worker" being that he is a contractor? I'd say yes...we can split hairs & say that he's not a co-employee, but co-worker would still apply in my opinion. If you are (or in this case, should be) working together toward a common goal for a common customer, then I say you're co-workers.
blargoe wrote: networker050184 wrote: Would you want one of your coworkers going straight to the manager if they didn't agree with what you were doing? I'm sure you would rather them come to you first if there was an issue, I know I would. You should also give your coworkers the same respect you would expect in the work place. My way of handling things like this might not be the correct way, but here's how I'd probably handle it. If you're busy with work lined up, and he's at his desk goofing off, show him all the work there is to do and ask him if he could help you. After one or two occurrences of him refusing, go to your manager. Him behaving the way he is behaving is like stealing.
networker050184 wrote: It may just be something that has stuck from my time in the military but I believe all problems should be resolved at the lowest level. If that doesn't work then go up the chain but only after making an attempt to solve the issue on your own level.
eMeS wrote: In my warped view of the world, this is what I would consider: 1) How is your and your coworker's performance evaluated? 2) Does that performance evaluation affect the amount of your raise and/or bonus, or the availability of promotions? 3) Is that performance evaluation scheme somewhat accurate? That is, are you being evaluated higher than your slothful co-worker, and therefore receiving more (insert whatever is important in your organization here) than your coworker?IMO, if the above fits your situation, then continuing to compete against someone who is lazy and does less than you is much better for you than any of the alternatives... In general, it's best to go to management with solutions instead of problems (this is similar to some of the advice you've seen in this thread). Also, the role of "work ethics police" is one of those things in an organization that is voluntary, doesn't pay well, and doesn't tend to lead to a high performance career. MS
Mrock4 wrote: networker050184 wrote: It may just be something that has stuck from my time in the military but I believe all problems should be resolved at the lowest level. If that doesn't work then go up the chain but only after making an attempt to solve the issue on your own level. +1. It's easy to run to the boss, but whether you're right or wrong, it makes you look bad without trying to resolve it at a lower level first.
Compare salaries for top cybersecurity certifications. Free download for TechExams community.