Timeline for Slow coworker receiving compliments while I receive complaints
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 6, 2019 at 1:01 | comment | added | Please stop being evil | @KateGregory Fair enough | |
| Oct 5, 2019 at 23:06 | comment | added | Kate Gregory | @thedarkwanderer it's possible you're right. Though how a boss is supposed to magically know how hard something is from a vague ticket entry and it getting closed 10 minutes later, I don't know. But let's pretend the boss "should" know. Do you want to sit at your desk feeling righteous, and being undervalued, or do you want to make sure everyone knows your value, even though you think they should have figured it out themselves? These are good and respectable things and they are also sometimes necessary, because we work in the real world with real (and sometimes flawed) managers. | |
| Oct 5, 2019 at 21:55 | comment | added | Please stop being evil | @KateGregory It's important because the metrics firms use to evaluate employee performance are so bad. I shouldn't have to tell my boss "Reminder! I do my job really well :D", they should have monitoring systems and effective metrics to analyze that kind of thing. I mean, that's often a manager's whole job. "tricks" is probably a bad word, because it sounds gimmicky and dismissive and underhanded, and these skills are good, respectable things to do. But it's not like the metric the company seems to be using here by default is the employee's fault! | |
| Oct 4, 2019 at 19:42 | comment | added | corsiKa | The best problem solvers write themselves out of a job. The best companies know to keep giving them jobs to do to obsolete them too. And if they don't, well, don't worry, the engineer will eventually land at a place that properly values them. | |
| Oct 4, 2019 at 11:28 | comment | added | Kate Gregory | I'm an engineer (literally, several engineering degrees) and very technical. Running a company means persuading people to buy our services, among other things, so I have some skills at that. I don't like the word "tricks" to describe this advice. Reminding people what you did, that you are good at your job, and why you're delivering what they need quickly is not a trick: it's honest and important. Without it, the firm might make bad choices and lose a good contributor. They need full information including how this worker is getting things done quickly because they are experienced. | |
| Oct 4, 2019 at 8:28 | comment | added | user32882 | Are you a sales or engineering person? | |
| Oct 4, 2019 at 3:18 | comment | added | Nav | @user32882: use Google search terms like "how to market your skills to boss" etc., until you find knowledge that you consider actionable. | |
| Oct 3, 2019 at 20:12 | comment | added | user32882 | @Nav im really intrigued by your comment that these are sales and marketing tricks. I too am an engineer and frequently face this sort of problem. How can I improve? | |
| Oct 3, 2019 at 13:43 | comment | added | IEatBagels | @Nav If you don't mind me asking, do you have a good resource an engineer should read regarding these tactics? | |
| Oct 3, 2019 at 11:53 | vote | accept | Green Baloon | ||
| Oct 3, 2019 at 11:16 | comment | added | Matthieu M. | @user3399: Also, if an issue is a recurring one, I would look into either at best (a) analyzing the root cause, to prevent it from happening in the first place or at least (b) automating detection and fix, to solve it summarily when it does happen. | |
| Oct 3, 2019 at 9:32 | comment | added | user3399 | this. If you fix an issue, you should always make sure to explain what you did, and why it works. As a dev, whenever I fix an issue, I make sure to explain what the issue is, and it's impact. What causes the issue. What I did to fix the issue, and why it fixes the issue. This has several benefits : nobody can undermine what you did, if you give enough details. And if somebody has a similar issue, they have something to learn from. | |
| Oct 3, 2019 at 8:37 | comment | added | Ralph Bolton | One other idea might be to take a holiday - while you're gone, someone will have to substitute for you, and they'll probably find the problems hard and slow to fix (or won't fix them at all, and things will stay broken until you return to much applause). | |
| Oct 3, 2019 at 8:18 | comment | added | SBI | I am this 'slow' co-worker, albeit in a different context. I would not say I am less productive, just more reserved. Our development relies heavily on quality control, and it is often more important to make the right fix in more time, than making the quick fix right away. Making the right trade-off, and selling it right, is often more important in my line of work. What I'm trying to say is: maybe keep your boss in the loop more tightly on the kind of trade-offs that you are making to show that your choices are the right ones, in addition to just selling yourself better anyway. | |
| Oct 3, 2019 at 6:26 | comment | added | Nav | These are basically sales and marketing tricks that Engineers need to learn. | |
| Oct 2, 2019 at 17:30 | comment | added | thursdaysgeek | Also, at least weekly let your boss know how many of those you've fixed, or make sure they are tracked in your bug tracking system. Boss needs to see that you've fixed 36 issues when co-worker fixed 4. | |
| Oct 2, 2019 at 16:34 | history | answered | Kate Gregory | CC BY-SA 4.0 |