How to deal with a senior coworker who sabotaged my work
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
4
down vote
favorite
I currently work on a team being led by a senior coworker with a title equivalent to tech lead in Agile, however I do not report to him. About 3-4 months ago he switched the process from exporting files from our team's repository to directly exporting them from the company software because "the repository did not always have the most up to date files". At the time I was not familiar enough with the software to realize the problems this caused.
Today the company software was down so I exported the files from the old repository (which is still being kept up to date). I realized that the files there are far more up to date than the ones in the system, e.g. version 1 and 2 vs version 6 and 7. I have been doing all the work to update files from early system versions to the current one redoing hundreds of changes that are easily accessible when I only needed to add a couple. I finished 4 tickets today when I had been averaging less than 3 a week.
How can I explain to my manager what has happened here? She thinks that I have been working extremely hard on this project and gave me a gift card for it not long ago. This is further complicated by the fact that she has told other coworkers that he saved the project.
I've lurked enough on this forum to know that you guys likely would recommend polishing the resume after a disaster like this, however I am starting a new position at the same company early next month. I have wasted hundreds of hours of time redoing already completed work and I feel terrible.
Edit1: This is the reason I’m not sure I want to say anything. The situation is confusing and I’ve probably left out important details as to make sure this is not identifiable. I have no concrete proof that he did this purposely, but other people and I have had problems with him in the past. When I first started on the team he was supposed to give us 10 two hour training sessions and he did 3 of them. Management wasn’t concerned either.
management conflict coworker
New contributor
|
show 6 more comments
up vote
4
down vote
favorite
I currently work on a team being led by a senior coworker with a title equivalent to tech lead in Agile, however I do not report to him. About 3-4 months ago he switched the process from exporting files from our team's repository to directly exporting them from the company software because "the repository did not always have the most up to date files". At the time I was not familiar enough with the software to realize the problems this caused.
Today the company software was down so I exported the files from the old repository (which is still being kept up to date). I realized that the files there are far more up to date than the ones in the system, e.g. version 1 and 2 vs version 6 and 7. I have been doing all the work to update files from early system versions to the current one redoing hundreds of changes that are easily accessible when I only needed to add a couple. I finished 4 tickets today when I had been averaging less than 3 a week.
How can I explain to my manager what has happened here? She thinks that I have been working extremely hard on this project and gave me a gift card for it not long ago. This is further complicated by the fact that she has told other coworkers that he saved the project.
I've lurked enough on this forum to know that you guys likely would recommend polishing the resume after a disaster like this, however I am starting a new position at the same company early next month. I have wasted hundreds of hours of time redoing already completed work and I feel terrible.
Edit1: This is the reason I’m not sure I want to say anything. The situation is confusing and I’ve probably left out important details as to make sure this is not identifiable. I have no concrete proof that he did this purposely, but other people and I have had problems with him in the past. When I first started on the team he was supposed to give us 10 two hour training sessions and he did 3 of them. Management wasn’t concerned either.
management conflict coworker
New contributor
3
Why can't you give the manager the facts?
– Kilisi
Nov 27 at 3:34
9
Some context is missing. "Sabotage" implies that you believe that the coworker did something intentional to cause your work to fail. Nothing that you've mentioned here seems to imply intent-- your coworker appears to have created an issue that affects you but it may have been unintentional. It's also not clear why you can't just ask the coworker about the problem his change seems to have created. Or why you can't tell your manager that the files were out of date. Or why the gift card was mentioned-- presumably, you have been working hard on the project.
– Justin Cave
Nov 27 at 4:56
Welcome new user. This question is a many times duplicate ("I'm a new programmer, and, surprisingly!, I've noticed software is an utter, total, complete shambles. What to do!")
– Fattie
Nov 27 at 6:08
I'm a little confused - how has nobody noticed that you've been working with outdated versions in the past?
– Erik
Nov 27 at 6:20
I'm going to agree with @JustinCave. This could be pure lack of awareness. Hanlon's Razor cuts deep and leaves scars. Don't attribute motive unless you can prove it.
– Wesley Long
Nov 27 at 7:58
|
show 6 more comments
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I currently work on a team being led by a senior coworker with a title equivalent to tech lead in Agile, however I do not report to him. About 3-4 months ago he switched the process from exporting files from our team's repository to directly exporting them from the company software because "the repository did not always have the most up to date files". At the time I was not familiar enough with the software to realize the problems this caused.
Today the company software was down so I exported the files from the old repository (which is still being kept up to date). I realized that the files there are far more up to date than the ones in the system, e.g. version 1 and 2 vs version 6 and 7. I have been doing all the work to update files from early system versions to the current one redoing hundreds of changes that are easily accessible when I only needed to add a couple. I finished 4 tickets today when I had been averaging less than 3 a week.
How can I explain to my manager what has happened here? She thinks that I have been working extremely hard on this project and gave me a gift card for it not long ago. This is further complicated by the fact that she has told other coworkers that he saved the project.
I've lurked enough on this forum to know that you guys likely would recommend polishing the resume after a disaster like this, however I am starting a new position at the same company early next month. I have wasted hundreds of hours of time redoing already completed work and I feel terrible.
Edit1: This is the reason I’m not sure I want to say anything. The situation is confusing and I’ve probably left out important details as to make sure this is not identifiable. I have no concrete proof that he did this purposely, but other people and I have had problems with him in the past. When I first started on the team he was supposed to give us 10 two hour training sessions and he did 3 of them. Management wasn’t concerned either.
management conflict coworker
New contributor
I currently work on a team being led by a senior coworker with a title equivalent to tech lead in Agile, however I do not report to him. About 3-4 months ago he switched the process from exporting files from our team's repository to directly exporting them from the company software because "the repository did not always have the most up to date files". At the time I was not familiar enough with the software to realize the problems this caused.
Today the company software was down so I exported the files from the old repository (which is still being kept up to date). I realized that the files there are far more up to date than the ones in the system, e.g. version 1 and 2 vs version 6 and 7. I have been doing all the work to update files from early system versions to the current one redoing hundreds of changes that are easily accessible when I only needed to add a couple. I finished 4 tickets today when I had been averaging less than 3 a week.
How can I explain to my manager what has happened here? She thinks that I have been working extremely hard on this project and gave me a gift card for it not long ago. This is further complicated by the fact that she has told other coworkers that he saved the project.
I've lurked enough on this forum to know that you guys likely would recommend polishing the resume after a disaster like this, however I am starting a new position at the same company early next month. I have wasted hundreds of hours of time redoing already completed work and I feel terrible.
Edit1: This is the reason I’m not sure I want to say anything. The situation is confusing and I’ve probably left out important details as to make sure this is not identifiable. I have no concrete proof that he did this purposely, but other people and I have had problems with him in the past. When I first started on the team he was supposed to give us 10 two hour training sessions and he did 3 of them. Management wasn’t concerned either.
management conflict coworker
management conflict coworker
New contributor
New contributor
edited Nov 27 at 14:57
New contributor
asked Nov 27 at 3:13
lordofsoup
295
295
New contributor
New contributor
3
Why can't you give the manager the facts?
– Kilisi
Nov 27 at 3:34
9
Some context is missing. "Sabotage" implies that you believe that the coworker did something intentional to cause your work to fail. Nothing that you've mentioned here seems to imply intent-- your coworker appears to have created an issue that affects you but it may have been unintentional. It's also not clear why you can't just ask the coworker about the problem his change seems to have created. Or why you can't tell your manager that the files were out of date. Or why the gift card was mentioned-- presumably, you have been working hard on the project.
– Justin Cave
Nov 27 at 4:56
Welcome new user. This question is a many times duplicate ("I'm a new programmer, and, surprisingly!, I've noticed software is an utter, total, complete shambles. What to do!")
– Fattie
Nov 27 at 6:08
I'm a little confused - how has nobody noticed that you've been working with outdated versions in the past?
– Erik
Nov 27 at 6:20
I'm going to agree with @JustinCave. This could be pure lack of awareness. Hanlon's Razor cuts deep and leaves scars. Don't attribute motive unless you can prove it.
– Wesley Long
Nov 27 at 7:58
|
show 6 more comments
3
Why can't you give the manager the facts?
– Kilisi
Nov 27 at 3:34
9
Some context is missing. "Sabotage" implies that you believe that the coworker did something intentional to cause your work to fail. Nothing that you've mentioned here seems to imply intent-- your coworker appears to have created an issue that affects you but it may have been unintentional. It's also not clear why you can't just ask the coworker about the problem his change seems to have created. Or why you can't tell your manager that the files were out of date. Or why the gift card was mentioned-- presumably, you have been working hard on the project.
– Justin Cave
Nov 27 at 4:56
Welcome new user. This question is a many times duplicate ("I'm a new programmer, and, surprisingly!, I've noticed software is an utter, total, complete shambles. What to do!")
– Fattie
Nov 27 at 6:08
I'm a little confused - how has nobody noticed that you've been working with outdated versions in the past?
– Erik
Nov 27 at 6:20
I'm going to agree with @JustinCave. This could be pure lack of awareness. Hanlon's Razor cuts deep and leaves scars. Don't attribute motive unless you can prove it.
– Wesley Long
Nov 27 at 7:58
3
3
Why can't you give the manager the facts?
– Kilisi
Nov 27 at 3:34
Why can't you give the manager the facts?
– Kilisi
Nov 27 at 3:34
9
9
Some context is missing. "Sabotage" implies that you believe that the coworker did something intentional to cause your work to fail. Nothing that you've mentioned here seems to imply intent-- your coworker appears to have created an issue that affects you but it may have been unintentional. It's also not clear why you can't just ask the coworker about the problem his change seems to have created. Or why you can't tell your manager that the files were out of date. Or why the gift card was mentioned-- presumably, you have been working hard on the project.
– Justin Cave
Nov 27 at 4:56
Some context is missing. "Sabotage" implies that you believe that the coworker did something intentional to cause your work to fail. Nothing that you've mentioned here seems to imply intent-- your coworker appears to have created an issue that affects you but it may have been unintentional. It's also not clear why you can't just ask the coworker about the problem his change seems to have created. Or why you can't tell your manager that the files were out of date. Or why the gift card was mentioned-- presumably, you have been working hard on the project.
– Justin Cave
Nov 27 at 4:56
Welcome new user. This question is a many times duplicate ("I'm a new programmer, and, surprisingly!, I've noticed software is an utter, total, complete shambles. What to do!")
– Fattie
Nov 27 at 6:08
Welcome new user. This question is a many times duplicate ("I'm a new programmer, and, surprisingly!, I've noticed software is an utter, total, complete shambles. What to do!")
– Fattie
Nov 27 at 6:08
I'm a little confused - how has nobody noticed that you've been working with outdated versions in the past?
– Erik
Nov 27 at 6:20
I'm a little confused - how has nobody noticed that you've been working with outdated versions in the past?
– Erik
Nov 27 at 6:20
I'm going to agree with @JustinCave. This could be pure lack of awareness. Hanlon's Razor cuts deep and leaves scars. Don't attribute motive unless you can prove it.
– Wesley Long
Nov 27 at 7:58
I'm going to agree with @JustinCave. This could be pure lack of awareness. Hanlon's Razor cuts deep and leaves scars. Don't attribute motive unless you can prove it.
– Wesley Long
Nov 27 at 7:58
|
show 6 more comments
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
How can I explain to my manager what has happened here?
Walk up to Manager and say:
"Hi Mrs Smith. I've just noticed that Version 7 is etc etc. Could be we're duplicating some work. What to do? Can you tell me what you think about this? How to proceed?"
The two relevant communication tips: (1) Never include any meta-language; state facts only. (2) Always finish with a question.
She thinks that I have been working extremely hard on this project [etc]
Totally irrelevant and a non-issue.
This is further complicated by the fact that she has told other coworkers that he saved the project.
There are no complications whatsoever.
All of what you describe is utterly normal in software.
Everything you say is, fortunately, a non-issue.
"It's not high school" - just speak up, then get right back to work.
Regarding the "senior worker". It's unclear what the point is. If you've noticed that version 7 is missing (or - whatever), just open mouth and state "Version 7 is missing". You can say that to both Manager and Senior Worker.
Note that if the manager (or, whoever) is telling you to do something that you feel is silly / wrong architecture / mistaken / etc, in software this is equivalent to noticing that you use a keyboard, or that you're breathing!
It's a total non-issue. The normal situation.
Just (A) do what you're told and (by all means) (B) feel free to simply and clearly state your opinion, while you are doing "A". (C) cash your massive paycheck every payday. Enjoy!
Comments are not for extended discussion; this conversation has been moved to chat.
– Jane S♦
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
How can I explain to my manager what has happened here?
Walk up to Manager and say:
"Hi Mrs Smith. I've just noticed that Version 7 is etc etc. Could be we're duplicating some work. What to do? Can you tell me what you think about this? How to proceed?"
The two relevant communication tips: (1) Never include any meta-language; state facts only. (2) Always finish with a question.
She thinks that I have been working extremely hard on this project [etc]
Totally irrelevant and a non-issue.
This is further complicated by the fact that she has told other coworkers that he saved the project.
There are no complications whatsoever.
All of what you describe is utterly normal in software.
Everything you say is, fortunately, a non-issue.
"It's not high school" - just speak up, then get right back to work.
Regarding the "senior worker". It's unclear what the point is. If you've noticed that version 7 is missing (or - whatever), just open mouth and state "Version 7 is missing". You can say that to both Manager and Senior Worker.
Note that if the manager (or, whoever) is telling you to do something that you feel is silly / wrong architecture / mistaken / etc, in software this is equivalent to noticing that you use a keyboard, or that you're breathing!
It's a total non-issue. The normal situation.
Just (A) do what you're told and (by all means) (B) feel free to simply and clearly state your opinion, while you are doing "A". (C) cash your massive paycheck every payday. Enjoy!
Comments are not for extended discussion; this conversation has been moved to chat.
– Jane S♦
2 days ago
add a comment |
up vote
5
down vote
accepted
How can I explain to my manager what has happened here?
Walk up to Manager and say:
"Hi Mrs Smith. I've just noticed that Version 7 is etc etc. Could be we're duplicating some work. What to do? Can you tell me what you think about this? How to proceed?"
The two relevant communication tips: (1) Never include any meta-language; state facts only. (2) Always finish with a question.
She thinks that I have been working extremely hard on this project [etc]
Totally irrelevant and a non-issue.
This is further complicated by the fact that she has told other coworkers that he saved the project.
There are no complications whatsoever.
All of what you describe is utterly normal in software.
Everything you say is, fortunately, a non-issue.
"It's not high school" - just speak up, then get right back to work.
Regarding the "senior worker". It's unclear what the point is. If you've noticed that version 7 is missing (or - whatever), just open mouth and state "Version 7 is missing". You can say that to both Manager and Senior Worker.
Note that if the manager (or, whoever) is telling you to do something that you feel is silly / wrong architecture / mistaken / etc, in software this is equivalent to noticing that you use a keyboard, or that you're breathing!
It's a total non-issue. The normal situation.
Just (A) do what you're told and (by all means) (B) feel free to simply and clearly state your opinion, while you are doing "A". (C) cash your massive paycheck every payday. Enjoy!
Comments are not for extended discussion; this conversation has been moved to chat.
– Jane S♦
2 days ago
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
How can I explain to my manager what has happened here?
Walk up to Manager and say:
"Hi Mrs Smith. I've just noticed that Version 7 is etc etc. Could be we're duplicating some work. What to do? Can you tell me what you think about this? How to proceed?"
The two relevant communication tips: (1) Never include any meta-language; state facts only. (2) Always finish with a question.
She thinks that I have been working extremely hard on this project [etc]
Totally irrelevant and a non-issue.
This is further complicated by the fact that she has told other coworkers that he saved the project.
There are no complications whatsoever.
All of what you describe is utterly normal in software.
Everything you say is, fortunately, a non-issue.
"It's not high school" - just speak up, then get right back to work.
Regarding the "senior worker". It's unclear what the point is. If you've noticed that version 7 is missing (or - whatever), just open mouth and state "Version 7 is missing". You can say that to both Manager and Senior Worker.
Note that if the manager (or, whoever) is telling you to do something that you feel is silly / wrong architecture / mistaken / etc, in software this is equivalent to noticing that you use a keyboard, or that you're breathing!
It's a total non-issue. The normal situation.
Just (A) do what you're told and (by all means) (B) feel free to simply and clearly state your opinion, while you are doing "A". (C) cash your massive paycheck every payday. Enjoy!
How can I explain to my manager what has happened here?
Walk up to Manager and say:
"Hi Mrs Smith. I've just noticed that Version 7 is etc etc. Could be we're duplicating some work. What to do? Can you tell me what you think about this? How to proceed?"
The two relevant communication tips: (1) Never include any meta-language; state facts only. (2) Always finish with a question.
She thinks that I have been working extremely hard on this project [etc]
Totally irrelevant and a non-issue.
This is further complicated by the fact that she has told other coworkers that he saved the project.
There are no complications whatsoever.
All of what you describe is utterly normal in software.
Everything you say is, fortunately, a non-issue.
"It's not high school" - just speak up, then get right back to work.
Regarding the "senior worker". It's unclear what the point is. If you've noticed that version 7 is missing (or - whatever), just open mouth and state "Version 7 is missing". You can say that to both Manager and Senior Worker.
Note that if the manager (or, whoever) is telling you to do something that you feel is silly / wrong architecture / mistaken / etc, in software this is equivalent to noticing that you use a keyboard, or that you're breathing!
It's a total non-issue. The normal situation.
Just (A) do what you're told and (by all means) (B) feel free to simply and clearly state your opinion, while you are doing "A". (C) cash your massive paycheck every payday. Enjoy!
edited Nov 27 at 10:49
answered Nov 27 at 6:07
Fattie
6,50531322
6,50531322
Comments are not for extended discussion; this conversation has been moved to chat.
– Jane S♦
2 days ago
add a comment |
Comments are not for extended discussion; this conversation has been moved to chat.
– Jane S♦
2 days ago
Comments are not for extended discussion; this conversation has been moved to chat.
– Jane S♦
2 days ago
Comments are not for extended discussion; this conversation has been moved to chat.
– Jane S♦
2 days ago
add a comment |
lordofsoup is a new contributor. Be nice, and check out our Code of Conduct.
lordofsoup is a new contributor. Be nice, and check out our Code of Conduct.
lordofsoup is a new contributor. Be nice, and check out our Code of Conduct.
lordofsoup is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f123469%2fhow-to-deal-with-a-senior-coworker-who-sabotaged-my-work%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
Why can't you give the manager the facts?
– Kilisi
Nov 27 at 3:34
9
Some context is missing. "Sabotage" implies that you believe that the coworker did something intentional to cause your work to fail. Nothing that you've mentioned here seems to imply intent-- your coworker appears to have created an issue that affects you but it may have been unintentional. It's also not clear why you can't just ask the coworker about the problem his change seems to have created. Or why you can't tell your manager that the files were out of date. Or why the gift card was mentioned-- presumably, you have been working hard on the project.
– Justin Cave
Nov 27 at 4:56
Welcome new user. This question is a many times duplicate ("I'm a new programmer, and, surprisingly!, I've noticed software is an utter, total, complete shambles. What to do!")
– Fattie
Nov 27 at 6:08
I'm a little confused - how has nobody noticed that you've been working with outdated versions in the past?
– Erik
Nov 27 at 6:20
I'm going to agree with @JustinCave. This could be pure lack of awareness. Hanlon's Razor cuts deep and leaves scars. Don't attribute motive unless you can prove it.
– Wesley Long
Nov 27 at 7:58