Should I tell my boss the work he did was worthless
So I have been handed a project that has been kicked around for 4 or 5 months with ~0 progress made. The project is to implement a new tool that was chosen before I got here. It seems like a good product, and the vendor is very helpful, but I don't really think it fits our needs or usecase. I made this clear to my boss and went forward after being told "I know, it's not great, but it's better than what we have now."
I recruited one of our part-time interns to help me out, as the front end of this project is going to include a lot of manual data entry and parsing from multiple sources. My boss asked for a status on this Friday night, and I told him that I was making slow, but steady progress. He offered that knowing the product better, he could do some work over the weekend. Knowing that his vision of this project didn't really match with what the vendor could supply or better business practices, I said that it might be better if I do it myself, as a learning opportunity. He dismissed this saying he wants the project to start moving and said he would do some work this weekend (I estimated another 12 hours worth of work).
Fast forward to 0900 this morning, my boss comes into the office announcing that he is done, and bragging that the work only took him an hour and a half. Full of trepidation, I open the Excel file I had been working on for two weeks, and which I had painstakingly laid out to be visually representative, and eventually parse-able by the accompanying script I am going to have to write. I was correct: my boss has compacted columns that should not have been, I have three different header row sections (Excel skills are not strong here), and he has partially or completely misunderstood the meaning and intent of a number of columns and key/value pairs.
Now, I have a backup of this file, and some of the data he added is actually very helpful, so he may have saved me some time/looking, but the spreadsheet as it sits isn't usable for its purpose, and is outright wrong in some respects. I probably have 10 hours of work now in stead of 12, so he saved the company a half hour of work for working over the weekend.
Questions:
- Should I tell my boss the work he gave me isn't usable, and why?
- How should I present this? He is something of a serial offender in this area, and while it didn't cost me more work this time, it easily could have.
TL;DR My boss claims to have finished a task he gave me in 1.5 hours that I projected would take 12 hours. I now have 10 hours of work to do to "fix" his work. Should I tell him and how?
Edit:
For some more background, my boss is the CEO of the company, and ~30 years my senior. We have a good working relationship, but I would say we are more acquaintances than friends. He is generally open to criticism, but quite headstrong, which is probably why he made these changes that I was trying to avoid. I have made it clear that what he wants to have happen is not possible without going back to vendor selection, which he has categorically ruled out. I am a senior manager of a ~50 person company located in the US.
manager project-management coworking
|
show 5 more comments
So I have been handed a project that has been kicked around for 4 or 5 months with ~0 progress made. The project is to implement a new tool that was chosen before I got here. It seems like a good product, and the vendor is very helpful, but I don't really think it fits our needs or usecase. I made this clear to my boss and went forward after being told "I know, it's not great, but it's better than what we have now."
I recruited one of our part-time interns to help me out, as the front end of this project is going to include a lot of manual data entry and parsing from multiple sources. My boss asked for a status on this Friday night, and I told him that I was making slow, but steady progress. He offered that knowing the product better, he could do some work over the weekend. Knowing that his vision of this project didn't really match with what the vendor could supply or better business practices, I said that it might be better if I do it myself, as a learning opportunity. He dismissed this saying he wants the project to start moving and said he would do some work this weekend (I estimated another 12 hours worth of work).
Fast forward to 0900 this morning, my boss comes into the office announcing that he is done, and bragging that the work only took him an hour and a half. Full of trepidation, I open the Excel file I had been working on for two weeks, and which I had painstakingly laid out to be visually representative, and eventually parse-able by the accompanying script I am going to have to write. I was correct: my boss has compacted columns that should not have been, I have three different header row sections (Excel skills are not strong here), and he has partially or completely misunderstood the meaning and intent of a number of columns and key/value pairs.
Now, I have a backup of this file, and some of the data he added is actually very helpful, so he may have saved me some time/looking, but the spreadsheet as it sits isn't usable for its purpose, and is outright wrong in some respects. I probably have 10 hours of work now in stead of 12, so he saved the company a half hour of work for working over the weekend.
Questions:
- Should I tell my boss the work he gave me isn't usable, and why?
- How should I present this? He is something of a serial offender in this area, and while it didn't cost me more work this time, it easily could have.
TL;DR My boss claims to have finished a task he gave me in 1.5 hours that I projected would take 12 hours. I now have 10 hours of work to do to "fix" his work. Should I tell him and how?
Edit:
For some more background, my boss is the CEO of the company, and ~30 years my senior. We have a good working relationship, but I would say we are more acquaintances than friends. He is generally open to criticism, but quite headstrong, which is probably why he made these changes that I was trying to avoid. I have made it clear that what he wants to have happen is not possible without going back to vendor selection, which he has categorically ruled out. I am a senior manager of a ~50 person company located in the US.
manager project-management coworking
2
"Should I tell my boss the work he gave me isn't usable" - what would be your goal in doing this?
– Joe Strazzere
2 hours ago
A lot of this question is going to depend on what sort of person your boss is and what your relationship with him is. Could you provide more data?
– Ben Barden
2 hours ago
1
@JoeStrazzere if you OP doesn't tell him anything, then they have about 10 ours of work left that they need to justify that the boss thinks is "done".
– Ben Barden
2 hours ago
4
@JoeStrazzere I guess there are three goals: 1) get him to not do this again 2) explain why I am spending a bunch of time on this thing that is “finished” 3) assumptively close on the final design of this project - as stated, what he wants and what he is going to get are not exactly the same at all.
– agentroadkill
2 hours ago
@agentroadkill yeah... we definitely need to know more about your boss's character and your relationship with him. Knowing which country this is wouldn't hurt.
– Ben Barden
2 hours ago
|
show 5 more comments
So I have been handed a project that has been kicked around for 4 or 5 months with ~0 progress made. The project is to implement a new tool that was chosen before I got here. It seems like a good product, and the vendor is very helpful, but I don't really think it fits our needs or usecase. I made this clear to my boss and went forward after being told "I know, it's not great, but it's better than what we have now."
I recruited one of our part-time interns to help me out, as the front end of this project is going to include a lot of manual data entry and parsing from multiple sources. My boss asked for a status on this Friday night, and I told him that I was making slow, but steady progress. He offered that knowing the product better, he could do some work over the weekend. Knowing that his vision of this project didn't really match with what the vendor could supply or better business practices, I said that it might be better if I do it myself, as a learning opportunity. He dismissed this saying he wants the project to start moving and said he would do some work this weekend (I estimated another 12 hours worth of work).
Fast forward to 0900 this morning, my boss comes into the office announcing that he is done, and bragging that the work only took him an hour and a half. Full of trepidation, I open the Excel file I had been working on for two weeks, and which I had painstakingly laid out to be visually representative, and eventually parse-able by the accompanying script I am going to have to write. I was correct: my boss has compacted columns that should not have been, I have three different header row sections (Excel skills are not strong here), and he has partially or completely misunderstood the meaning and intent of a number of columns and key/value pairs.
Now, I have a backup of this file, and some of the data he added is actually very helpful, so he may have saved me some time/looking, but the spreadsheet as it sits isn't usable for its purpose, and is outright wrong in some respects. I probably have 10 hours of work now in stead of 12, so he saved the company a half hour of work for working over the weekend.
Questions:
- Should I tell my boss the work he gave me isn't usable, and why?
- How should I present this? He is something of a serial offender in this area, and while it didn't cost me more work this time, it easily could have.
TL;DR My boss claims to have finished a task he gave me in 1.5 hours that I projected would take 12 hours. I now have 10 hours of work to do to "fix" his work. Should I tell him and how?
Edit:
For some more background, my boss is the CEO of the company, and ~30 years my senior. We have a good working relationship, but I would say we are more acquaintances than friends. He is generally open to criticism, but quite headstrong, which is probably why he made these changes that I was trying to avoid. I have made it clear that what he wants to have happen is not possible without going back to vendor selection, which he has categorically ruled out. I am a senior manager of a ~50 person company located in the US.
manager project-management coworking
So I have been handed a project that has been kicked around for 4 or 5 months with ~0 progress made. The project is to implement a new tool that was chosen before I got here. It seems like a good product, and the vendor is very helpful, but I don't really think it fits our needs or usecase. I made this clear to my boss and went forward after being told "I know, it's not great, but it's better than what we have now."
I recruited one of our part-time interns to help me out, as the front end of this project is going to include a lot of manual data entry and parsing from multiple sources. My boss asked for a status on this Friday night, and I told him that I was making slow, but steady progress. He offered that knowing the product better, he could do some work over the weekend. Knowing that his vision of this project didn't really match with what the vendor could supply or better business practices, I said that it might be better if I do it myself, as a learning opportunity. He dismissed this saying he wants the project to start moving and said he would do some work this weekend (I estimated another 12 hours worth of work).
Fast forward to 0900 this morning, my boss comes into the office announcing that he is done, and bragging that the work only took him an hour and a half. Full of trepidation, I open the Excel file I had been working on for two weeks, and which I had painstakingly laid out to be visually representative, and eventually parse-able by the accompanying script I am going to have to write. I was correct: my boss has compacted columns that should not have been, I have three different header row sections (Excel skills are not strong here), and he has partially or completely misunderstood the meaning and intent of a number of columns and key/value pairs.
Now, I have a backup of this file, and some of the data he added is actually very helpful, so he may have saved me some time/looking, but the spreadsheet as it sits isn't usable for its purpose, and is outright wrong in some respects. I probably have 10 hours of work now in stead of 12, so he saved the company a half hour of work for working over the weekend.
Questions:
- Should I tell my boss the work he gave me isn't usable, and why?
- How should I present this? He is something of a serial offender in this area, and while it didn't cost me more work this time, it easily could have.
TL;DR My boss claims to have finished a task he gave me in 1.5 hours that I projected would take 12 hours. I now have 10 hours of work to do to "fix" his work. Should I tell him and how?
Edit:
For some more background, my boss is the CEO of the company, and ~30 years my senior. We have a good working relationship, but I would say we are more acquaintances than friends. He is generally open to criticism, but quite headstrong, which is probably why he made these changes that I was trying to avoid. I have made it clear that what he wants to have happen is not possible without going back to vendor selection, which he has categorically ruled out. I am a senior manager of a ~50 person company located in the US.
manager project-management coworking
manager project-management coworking
edited 1 hour ago
agentroadkill
asked 2 hours ago
agentroadkillagentroadkill
1,3161816
1,3161816
2
"Should I tell my boss the work he gave me isn't usable" - what would be your goal in doing this?
– Joe Strazzere
2 hours ago
A lot of this question is going to depend on what sort of person your boss is and what your relationship with him is. Could you provide more data?
– Ben Barden
2 hours ago
1
@JoeStrazzere if you OP doesn't tell him anything, then they have about 10 ours of work left that they need to justify that the boss thinks is "done".
– Ben Barden
2 hours ago
4
@JoeStrazzere I guess there are three goals: 1) get him to not do this again 2) explain why I am spending a bunch of time on this thing that is “finished” 3) assumptively close on the final design of this project - as stated, what he wants and what he is going to get are not exactly the same at all.
– agentroadkill
2 hours ago
@agentroadkill yeah... we definitely need to know more about your boss's character and your relationship with him. Knowing which country this is wouldn't hurt.
– Ben Barden
2 hours ago
|
show 5 more comments
2
"Should I tell my boss the work he gave me isn't usable" - what would be your goal in doing this?
– Joe Strazzere
2 hours ago
A lot of this question is going to depend on what sort of person your boss is and what your relationship with him is. Could you provide more data?
– Ben Barden
2 hours ago
1
@JoeStrazzere if you OP doesn't tell him anything, then they have about 10 ours of work left that they need to justify that the boss thinks is "done".
– Ben Barden
2 hours ago
4
@JoeStrazzere I guess there are three goals: 1) get him to not do this again 2) explain why I am spending a bunch of time on this thing that is “finished” 3) assumptively close on the final design of this project - as stated, what he wants and what he is going to get are not exactly the same at all.
– agentroadkill
2 hours ago
@agentroadkill yeah... we definitely need to know more about your boss's character and your relationship with him. Knowing which country this is wouldn't hurt.
– Ben Barden
2 hours ago
2
2
"Should I tell my boss the work he gave me isn't usable" - what would be your goal in doing this?
– Joe Strazzere
2 hours ago
"Should I tell my boss the work he gave me isn't usable" - what would be your goal in doing this?
– Joe Strazzere
2 hours ago
A lot of this question is going to depend on what sort of person your boss is and what your relationship with him is. Could you provide more data?
– Ben Barden
2 hours ago
A lot of this question is going to depend on what sort of person your boss is and what your relationship with him is. Could you provide more data?
– Ben Barden
2 hours ago
1
1
@JoeStrazzere if you OP doesn't tell him anything, then they have about 10 ours of work left that they need to justify that the boss thinks is "done".
– Ben Barden
2 hours ago
@JoeStrazzere if you OP doesn't tell him anything, then they have about 10 ours of work left that they need to justify that the boss thinks is "done".
– Ben Barden
2 hours ago
4
4
@JoeStrazzere I guess there are three goals: 1) get him to not do this again 2) explain why I am spending a bunch of time on this thing that is “finished” 3) assumptively close on the final design of this project - as stated, what he wants and what he is going to get are not exactly the same at all.
– agentroadkill
2 hours ago
@JoeStrazzere I guess there are three goals: 1) get him to not do this again 2) explain why I am spending a bunch of time on this thing that is “finished” 3) assumptively close on the final design of this project - as stated, what he wants and what he is going to get are not exactly the same at all.
– agentroadkill
2 hours ago
@agentroadkill yeah... we definitely need to know more about your boss's character and your relationship with him. Knowing which country this is wouldn't hurt.
– Ben Barden
2 hours ago
@agentroadkill yeah... we definitely need to know more about your boss's character and your relationship with him. Knowing which country this is wouldn't hurt.
– Ben Barden
2 hours ago
|
show 5 more comments
5 Answers
5
active
oldest
votes
The short answer: No, you should not tell your boss that his work was worthless. Instead, express that it's not what you need.
My rationale is that worthless is emotionally charged, maximally judgmental, and very much subjectively based. Worthless implies that there is literally zero underlying value to the way your boss arranged the information, and further suggests that your boss is foolish for having done such a bad job, and foolish again for failing to realize what a bad job it was (despite his not being involved with, or possibly even qualified to fully understand, the next phases of the project).
It's not generally a great professional move to demean and degrade, and in this specific case I don't see much upside to your boss knowing that you think so little of him (even if that's too strong to describe your actual feelings, it's a plausible message for someone to draw from being told that the work was worthless).
But critically, your assessment of the work is not really necessary here. That the work was bad, full stop, provides very little useful information to anybody. That the work is not what you need it to be for the project to continue, on the other hand, is valuable information both as an update for the project's current status and as a comment on what your boss did. It's also entirely defensible-- if your boss wants to be a cheerleader for his work, he will have to explain how it will meet your needs. If he can do so, then you've avoided making an inflammatory claim that isn't true. If he can't, your point is made but there are some face-saving ways out for your boss.
Saying that you need something other than what your boss produced places the emphasis on the work requirements you're facing (rather than the skill or quality of any particular person), describes what you will be working on next (despite the "complete" work your boss provided), puts the project timeline into clearer focus (your boss saved you little time or effort here), and reiterates what all of this effort is for (you're not nitpicking something with your boss for some petty reason, you're just focusing on the functional requirements of the job).
You are, of course correct. Diplomacy counts.
– agentroadkill
49 mins ago
add a comment |
Your boss worked over the weekend with the intent to help. Unfortunately, his work does not fulfill all the project requirements. Be grateful for his willingness to help, but be clear about how his work does not suit the project requirements.
I would send the boss a quick email stating precisely which which requirements are not fulfilled. This will keep the discussion objective and business-focused, so that you and your boss can stay on the same team. Remember, you both have the same goal here.
Hey boss, thanks for your help with the XY project. It looks like there's a little more work to be done: combining columns A and B means that we can no longer distinguish which customers have cancelled their orders. And we still need to implement a "Submit" button. I'll work on adding those features. I expect to have a new version for your review tomorrow afternoon.
Just don't call his work "worthless." Harsh words like that can severely damage your relationship.
7
It would also be good to mention what work was helpful. - "some of the data he added is actually very helpful, so he may have saved me some time/looking"
– David K
2 hours ago
Based on OP's statement, "his vision of this project didn't really match with what the vendor could supply or better business practices", I'm curious who is setting the requirements? If it's the boss, perhaps OP is missing them.
– zarose
35 mins ago
add a comment |
You should go over the requirements, point by point. Highly emphasize the things he did that helped, and downplay the things that did not. Give him an opportunity to save face by writing them off as misunderstanding's and miscommunications.
Then, go over what needs to be done, and show him. He did what most people wouldn't which is jump in to help, and he did save you SOME time. Be grateful, thank him for his help, show him some details of the complete fix, and if he jumps in to help in the future, he will be more valuable.
Considering that most people complain about how their bosses are no help at all, this manager is a rare find, do all that you can to cultivate a healthy relationship with him.
- Praise his strengths
- Thank him for his input
- Minimize his faults
add a comment |
If he reduced to work to be done from 12 hours to 10 hours, and he did that in 1.5 hours, it's certainly not worthless. In fact, it's more than you could have done in 1.5 hours.
10 hours of work seems to be too trivial to make a fuss about. I suggest you thank your boss for his work, and spend the 10 hours fixing "the loose ends". Document in the ticket (you do have tickets to keep track of what you do, don't you?) the steps required to finish the task. That way, you can point to them when asked about them.
"you have tickets to keep track of what you do" cry laughs on floor
– agentroadkill
19 mins ago
add a comment |
Should I tell him and how?
Most definitely, if you don't then the work will either not be done or your boss will be wondering what you're spending your time doing since he believes the task is complete.
How?
Just tell him how it is without giving any form of "I told you so". Hi x, the work you've given me isn't usable. This is why...
Then say that you will get to work on redoing it immediately, should only take about 10 hours. If he has any objections to this and thinks he can do it quicker again then let him get on with it.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: false,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f131309%2fshould-i-tell-my-boss-the-work-he-did-was-worthless%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
StackExchange.ready(function () {
$("#show-editor-button input, #show-editor-button button").click(function () {
var showEditor = function() {
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
};
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True') {
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup({
url: '/post/self-answer-popup',
loaded: function(popup) {
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
}
})
} else{
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true) {
showEditor();
}
}
});
});
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
The short answer: No, you should not tell your boss that his work was worthless. Instead, express that it's not what you need.
My rationale is that worthless is emotionally charged, maximally judgmental, and very much subjectively based. Worthless implies that there is literally zero underlying value to the way your boss arranged the information, and further suggests that your boss is foolish for having done such a bad job, and foolish again for failing to realize what a bad job it was (despite his not being involved with, or possibly even qualified to fully understand, the next phases of the project).
It's not generally a great professional move to demean and degrade, and in this specific case I don't see much upside to your boss knowing that you think so little of him (even if that's too strong to describe your actual feelings, it's a plausible message for someone to draw from being told that the work was worthless).
But critically, your assessment of the work is not really necessary here. That the work was bad, full stop, provides very little useful information to anybody. That the work is not what you need it to be for the project to continue, on the other hand, is valuable information both as an update for the project's current status and as a comment on what your boss did. It's also entirely defensible-- if your boss wants to be a cheerleader for his work, he will have to explain how it will meet your needs. If he can do so, then you've avoided making an inflammatory claim that isn't true. If he can't, your point is made but there are some face-saving ways out for your boss.
Saying that you need something other than what your boss produced places the emphasis on the work requirements you're facing (rather than the skill or quality of any particular person), describes what you will be working on next (despite the "complete" work your boss provided), puts the project timeline into clearer focus (your boss saved you little time or effort here), and reiterates what all of this effort is for (you're not nitpicking something with your boss for some petty reason, you're just focusing on the functional requirements of the job).
You are, of course correct. Diplomacy counts.
– agentroadkill
49 mins ago
add a comment |
The short answer: No, you should not tell your boss that his work was worthless. Instead, express that it's not what you need.
My rationale is that worthless is emotionally charged, maximally judgmental, and very much subjectively based. Worthless implies that there is literally zero underlying value to the way your boss arranged the information, and further suggests that your boss is foolish for having done such a bad job, and foolish again for failing to realize what a bad job it was (despite his not being involved with, or possibly even qualified to fully understand, the next phases of the project).
It's not generally a great professional move to demean and degrade, and in this specific case I don't see much upside to your boss knowing that you think so little of him (even if that's too strong to describe your actual feelings, it's a plausible message for someone to draw from being told that the work was worthless).
But critically, your assessment of the work is not really necessary here. That the work was bad, full stop, provides very little useful information to anybody. That the work is not what you need it to be for the project to continue, on the other hand, is valuable information both as an update for the project's current status and as a comment on what your boss did. It's also entirely defensible-- if your boss wants to be a cheerleader for his work, he will have to explain how it will meet your needs. If he can do so, then you've avoided making an inflammatory claim that isn't true. If he can't, your point is made but there are some face-saving ways out for your boss.
Saying that you need something other than what your boss produced places the emphasis on the work requirements you're facing (rather than the skill or quality of any particular person), describes what you will be working on next (despite the "complete" work your boss provided), puts the project timeline into clearer focus (your boss saved you little time or effort here), and reiterates what all of this effort is for (you're not nitpicking something with your boss for some petty reason, you're just focusing on the functional requirements of the job).
You are, of course correct. Diplomacy counts.
– agentroadkill
49 mins ago
add a comment |
The short answer: No, you should not tell your boss that his work was worthless. Instead, express that it's not what you need.
My rationale is that worthless is emotionally charged, maximally judgmental, and very much subjectively based. Worthless implies that there is literally zero underlying value to the way your boss arranged the information, and further suggests that your boss is foolish for having done such a bad job, and foolish again for failing to realize what a bad job it was (despite his not being involved with, or possibly even qualified to fully understand, the next phases of the project).
It's not generally a great professional move to demean and degrade, and in this specific case I don't see much upside to your boss knowing that you think so little of him (even if that's too strong to describe your actual feelings, it's a plausible message for someone to draw from being told that the work was worthless).
But critically, your assessment of the work is not really necessary here. That the work was bad, full stop, provides very little useful information to anybody. That the work is not what you need it to be for the project to continue, on the other hand, is valuable information both as an update for the project's current status and as a comment on what your boss did. It's also entirely defensible-- if your boss wants to be a cheerleader for his work, he will have to explain how it will meet your needs. If he can do so, then you've avoided making an inflammatory claim that isn't true. If he can't, your point is made but there are some face-saving ways out for your boss.
Saying that you need something other than what your boss produced places the emphasis on the work requirements you're facing (rather than the skill or quality of any particular person), describes what you will be working on next (despite the "complete" work your boss provided), puts the project timeline into clearer focus (your boss saved you little time or effort here), and reiterates what all of this effort is for (you're not nitpicking something with your boss for some petty reason, you're just focusing on the functional requirements of the job).
The short answer: No, you should not tell your boss that his work was worthless. Instead, express that it's not what you need.
My rationale is that worthless is emotionally charged, maximally judgmental, and very much subjectively based. Worthless implies that there is literally zero underlying value to the way your boss arranged the information, and further suggests that your boss is foolish for having done such a bad job, and foolish again for failing to realize what a bad job it was (despite his not being involved with, or possibly even qualified to fully understand, the next phases of the project).
It's not generally a great professional move to demean and degrade, and in this specific case I don't see much upside to your boss knowing that you think so little of him (even if that's too strong to describe your actual feelings, it's a plausible message for someone to draw from being told that the work was worthless).
But critically, your assessment of the work is not really necessary here. That the work was bad, full stop, provides very little useful information to anybody. That the work is not what you need it to be for the project to continue, on the other hand, is valuable information both as an update for the project's current status and as a comment on what your boss did. It's also entirely defensible-- if your boss wants to be a cheerleader for his work, he will have to explain how it will meet your needs. If he can do so, then you've avoided making an inflammatory claim that isn't true. If he can't, your point is made but there are some face-saving ways out for your boss.
Saying that you need something other than what your boss produced places the emphasis on the work requirements you're facing (rather than the skill or quality of any particular person), describes what you will be working on next (despite the "complete" work your boss provided), puts the project timeline into clearer focus (your boss saved you little time or effort here), and reiterates what all of this effort is for (you're not nitpicking something with your boss for some petty reason, you're just focusing on the functional requirements of the job).
answered 1 hour ago
Upper_CaseUpper_Case
1,455311
1,455311
You are, of course correct. Diplomacy counts.
– agentroadkill
49 mins ago
add a comment |
You are, of course correct. Diplomacy counts.
– agentroadkill
49 mins ago
You are, of course correct. Diplomacy counts.
– agentroadkill
49 mins ago
You are, of course correct. Diplomacy counts.
– agentroadkill
49 mins ago
add a comment |
Your boss worked over the weekend with the intent to help. Unfortunately, his work does not fulfill all the project requirements. Be grateful for his willingness to help, but be clear about how his work does not suit the project requirements.
I would send the boss a quick email stating precisely which which requirements are not fulfilled. This will keep the discussion objective and business-focused, so that you and your boss can stay on the same team. Remember, you both have the same goal here.
Hey boss, thanks for your help with the XY project. It looks like there's a little more work to be done: combining columns A and B means that we can no longer distinguish which customers have cancelled their orders. And we still need to implement a "Submit" button. I'll work on adding those features. I expect to have a new version for your review tomorrow afternoon.
Just don't call his work "worthless." Harsh words like that can severely damage your relationship.
7
It would also be good to mention what work was helpful. - "some of the data he added is actually very helpful, so he may have saved me some time/looking"
– David K
2 hours ago
Based on OP's statement, "his vision of this project didn't really match with what the vendor could supply or better business practices", I'm curious who is setting the requirements? If it's the boss, perhaps OP is missing them.
– zarose
35 mins ago
add a comment |
Your boss worked over the weekend with the intent to help. Unfortunately, his work does not fulfill all the project requirements. Be grateful for his willingness to help, but be clear about how his work does not suit the project requirements.
I would send the boss a quick email stating precisely which which requirements are not fulfilled. This will keep the discussion objective and business-focused, so that you and your boss can stay on the same team. Remember, you both have the same goal here.
Hey boss, thanks for your help with the XY project. It looks like there's a little more work to be done: combining columns A and B means that we can no longer distinguish which customers have cancelled their orders. And we still need to implement a "Submit" button. I'll work on adding those features. I expect to have a new version for your review tomorrow afternoon.
Just don't call his work "worthless." Harsh words like that can severely damage your relationship.
7
It would also be good to mention what work was helpful. - "some of the data he added is actually very helpful, so he may have saved me some time/looking"
– David K
2 hours ago
Based on OP's statement, "his vision of this project didn't really match with what the vendor could supply or better business practices", I'm curious who is setting the requirements? If it's the boss, perhaps OP is missing them.
– zarose
35 mins ago
add a comment |
Your boss worked over the weekend with the intent to help. Unfortunately, his work does not fulfill all the project requirements. Be grateful for his willingness to help, but be clear about how his work does not suit the project requirements.
I would send the boss a quick email stating precisely which which requirements are not fulfilled. This will keep the discussion objective and business-focused, so that you and your boss can stay on the same team. Remember, you both have the same goal here.
Hey boss, thanks for your help with the XY project. It looks like there's a little more work to be done: combining columns A and B means that we can no longer distinguish which customers have cancelled their orders. And we still need to implement a "Submit" button. I'll work on adding those features. I expect to have a new version for your review tomorrow afternoon.
Just don't call his work "worthless." Harsh words like that can severely damage your relationship.
Your boss worked over the weekend with the intent to help. Unfortunately, his work does not fulfill all the project requirements. Be grateful for his willingness to help, but be clear about how his work does not suit the project requirements.
I would send the boss a quick email stating precisely which which requirements are not fulfilled. This will keep the discussion objective and business-focused, so that you and your boss can stay on the same team. Remember, you both have the same goal here.
Hey boss, thanks for your help with the XY project. It looks like there's a little more work to be done: combining columns A and B means that we can no longer distinguish which customers have cancelled their orders. And we still need to implement a "Submit" button. I'll work on adding those features. I expect to have a new version for your review tomorrow afternoon.
Just don't call his work "worthless." Harsh words like that can severely damage your relationship.
answered 2 hours ago
Greg EdelstonGreg Edelston
32416
32416
7
It would also be good to mention what work was helpful. - "some of the data he added is actually very helpful, so he may have saved me some time/looking"
– David K
2 hours ago
Based on OP's statement, "his vision of this project didn't really match with what the vendor could supply or better business practices", I'm curious who is setting the requirements? If it's the boss, perhaps OP is missing them.
– zarose
35 mins ago
add a comment |
7
It would also be good to mention what work was helpful. - "some of the data he added is actually very helpful, so he may have saved me some time/looking"
– David K
2 hours ago
Based on OP's statement, "his vision of this project didn't really match with what the vendor could supply or better business practices", I'm curious who is setting the requirements? If it's the boss, perhaps OP is missing them.
– zarose
35 mins ago
7
7
It would also be good to mention what work was helpful. - "some of the data he added is actually very helpful, so he may have saved me some time/looking"
– David K
2 hours ago
It would also be good to mention what work was helpful. - "some of the data he added is actually very helpful, so he may have saved me some time/looking"
– David K
2 hours ago
Based on OP's statement, "his vision of this project didn't really match with what the vendor could supply or better business practices", I'm curious who is setting the requirements? If it's the boss, perhaps OP is missing them.
– zarose
35 mins ago
Based on OP's statement, "his vision of this project didn't really match with what the vendor could supply or better business practices", I'm curious who is setting the requirements? If it's the boss, perhaps OP is missing them.
– zarose
35 mins ago
add a comment |
You should go over the requirements, point by point. Highly emphasize the things he did that helped, and downplay the things that did not. Give him an opportunity to save face by writing them off as misunderstanding's and miscommunications.
Then, go over what needs to be done, and show him. He did what most people wouldn't which is jump in to help, and he did save you SOME time. Be grateful, thank him for his help, show him some details of the complete fix, and if he jumps in to help in the future, he will be more valuable.
Considering that most people complain about how their bosses are no help at all, this manager is a rare find, do all that you can to cultivate a healthy relationship with him.
- Praise his strengths
- Thank him for his input
- Minimize his faults
add a comment |
You should go over the requirements, point by point. Highly emphasize the things he did that helped, and downplay the things that did not. Give him an opportunity to save face by writing them off as misunderstanding's and miscommunications.
Then, go over what needs to be done, and show him. He did what most people wouldn't which is jump in to help, and he did save you SOME time. Be grateful, thank him for his help, show him some details of the complete fix, and if he jumps in to help in the future, he will be more valuable.
Considering that most people complain about how their bosses are no help at all, this manager is a rare find, do all that you can to cultivate a healthy relationship with him.
- Praise his strengths
- Thank him for his input
- Minimize his faults
add a comment |
You should go over the requirements, point by point. Highly emphasize the things he did that helped, and downplay the things that did not. Give him an opportunity to save face by writing them off as misunderstanding's and miscommunications.
Then, go over what needs to be done, and show him. He did what most people wouldn't which is jump in to help, and he did save you SOME time. Be grateful, thank him for his help, show him some details of the complete fix, and if he jumps in to help in the future, he will be more valuable.
Considering that most people complain about how their bosses are no help at all, this manager is a rare find, do all that you can to cultivate a healthy relationship with him.
- Praise his strengths
- Thank him for his input
- Minimize his faults
You should go over the requirements, point by point. Highly emphasize the things he did that helped, and downplay the things that did not. Give him an opportunity to save face by writing them off as misunderstanding's and miscommunications.
Then, go over what needs to be done, and show him. He did what most people wouldn't which is jump in to help, and he did save you SOME time. Be grateful, thank him for his help, show him some details of the complete fix, and if he jumps in to help in the future, he will be more valuable.
Considering that most people complain about how their bosses are no help at all, this manager is a rare find, do all that you can to cultivate a healthy relationship with him.
- Praise his strengths
- Thank him for his input
- Minimize his faults
answered 1 hour ago
Richard URichard U
99.6k73269396
99.6k73269396
add a comment |
add a comment |
If he reduced to work to be done from 12 hours to 10 hours, and he did that in 1.5 hours, it's certainly not worthless. In fact, it's more than you could have done in 1.5 hours.
10 hours of work seems to be too trivial to make a fuss about. I suggest you thank your boss for his work, and spend the 10 hours fixing "the loose ends". Document in the ticket (you do have tickets to keep track of what you do, don't you?) the steps required to finish the task. That way, you can point to them when asked about them.
"you have tickets to keep track of what you do" cry laughs on floor
– agentroadkill
19 mins ago
add a comment |
If he reduced to work to be done from 12 hours to 10 hours, and he did that in 1.5 hours, it's certainly not worthless. In fact, it's more than you could have done in 1.5 hours.
10 hours of work seems to be too trivial to make a fuss about. I suggest you thank your boss for his work, and spend the 10 hours fixing "the loose ends". Document in the ticket (you do have tickets to keep track of what you do, don't you?) the steps required to finish the task. That way, you can point to them when asked about them.
"you have tickets to keep track of what you do" cry laughs on floor
– agentroadkill
19 mins ago
add a comment |
If he reduced to work to be done from 12 hours to 10 hours, and he did that in 1.5 hours, it's certainly not worthless. In fact, it's more than you could have done in 1.5 hours.
10 hours of work seems to be too trivial to make a fuss about. I suggest you thank your boss for his work, and spend the 10 hours fixing "the loose ends". Document in the ticket (you do have tickets to keep track of what you do, don't you?) the steps required to finish the task. That way, you can point to them when asked about them.
If he reduced to work to be done from 12 hours to 10 hours, and he did that in 1.5 hours, it's certainly not worthless. In fact, it's more than you could have done in 1.5 hours.
10 hours of work seems to be too trivial to make a fuss about. I suggest you thank your boss for his work, and spend the 10 hours fixing "the loose ends". Document in the ticket (you do have tickets to keep track of what you do, don't you?) the steps required to finish the task. That way, you can point to them when asked about them.
answered 23 mins ago
AbigailAbigail
3,70021120
3,70021120
"you have tickets to keep track of what you do" cry laughs on floor
– agentroadkill
19 mins ago
add a comment |
"you have tickets to keep track of what you do" cry laughs on floor
– agentroadkill
19 mins ago
"you have tickets to keep track of what you do" cry laughs on floor
– agentroadkill
19 mins ago
"you have tickets to keep track of what you do" cry laughs on floor
– agentroadkill
19 mins ago
add a comment |
Should I tell him and how?
Most definitely, if you don't then the work will either not be done or your boss will be wondering what you're spending your time doing since he believes the task is complete.
How?
Just tell him how it is without giving any form of "I told you so". Hi x, the work you've given me isn't usable. This is why...
Then say that you will get to work on redoing it immediately, should only take about 10 hours. If he has any objections to this and thinks he can do it quicker again then let him get on with it.
add a comment |
Should I tell him and how?
Most definitely, if you don't then the work will either not be done or your boss will be wondering what you're spending your time doing since he believes the task is complete.
How?
Just tell him how it is without giving any form of "I told you so". Hi x, the work you've given me isn't usable. This is why...
Then say that you will get to work on redoing it immediately, should only take about 10 hours. If he has any objections to this and thinks he can do it quicker again then let him get on with it.
add a comment |
Should I tell him and how?
Most definitely, if you don't then the work will either not be done or your boss will be wondering what you're spending your time doing since he believes the task is complete.
How?
Just tell him how it is without giving any form of "I told you so". Hi x, the work you've given me isn't usable. This is why...
Then say that you will get to work on redoing it immediately, should only take about 10 hours. If he has any objections to this and thinks he can do it quicker again then let him get on with it.
Should I tell him and how?
Most definitely, if you don't then the work will either not be done or your boss will be wondering what you're spending your time doing since he believes the task is complete.
How?
Just tell him how it is without giving any form of "I told you so". Hi x, the work you've given me isn't usable. This is why...
Then say that you will get to work on redoing it immediately, should only take about 10 hours. If he has any objections to this and thinks he can do it quicker again then let him get on with it.
answered 2 hours ago
TwyxzTwyxz
12.8k103879
12.8k103879
add a comment |
add a comment |
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.
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%2f131309%2fshould-i-tell-my-boss-the-work-he-did-was-worthless%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
2
"Should I tell my boss the work he gave me isn't usable" - what would be your goal in doing this?
– Joe Strazzere
2 hours ago
A lot of this question is going to depend on what sort of person your boss is and what your relationship with him is. Could you provide more data?
– Ben Barden
2 hours ago
1
@JoeStrazzere if you OP doesn't tell him anything, then they have about 10 ours of work left that they need to justify that the boss thinks is "done".
– Ben Barden
2 hours ago
4
@JoeStrazzere I guess there are three goals: 1) get him to not do this again 2) explain why I am spending a bunch of time on this thing that is “finished” 3) assumptively close on the final design of this project - as stated, what he wants and what he is going to get are not exactly the same at all.
– agentroadkill
2 hours ago
@agentroadkill yeah... we definitely need to know more about your boss's character and your relationship with him. Knowing which country this is wouldn't hurt.
– Ben Barden
2 hours ago