Boss setting expectations that subordinates can't meet
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
3
down vote
favorite
My grand boss has communicated out an unrealistic expectation to the board that we are unable to meet.
My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint.
The subordinate has a history of ignoring the chain of command and going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point and I asked my grand boss what could be done to help us meet the expectations set, such as overtime and mentoring. My grand boss agreed to both but said no matter what we have to deliver on the date said.
I told my grand boss that my subordinate had put a complaint in about my grand boss and my grand boss responded saying that this has happened one too many times and that he wants my subordinate gone.
After discussing what has gone on with my wife, she said to keep out of it.
If I do so, the pattern will continue to repeat itself. So I am looking for a list of actionable points I can take away to resolve this situation and prevent it happening again if at all possible.
management politics deadlines
add a comment |
up vote
3
down vote
favorite
My grand boss has communicated out an unrealistic expectation to the board that we are unable to meet.
My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint.
The subordinate has a history of ignoring the chain of command and going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point and I asked my grand boss what could be done to help us meet the expectations set, such as overtime and mentoring. My grand boss agreed to both but said no matter what we have to deliver on the date said.
I told my grand boss that my subordinate had put a complaint in about my grand boss and my grand boss responded saying that this has happened one too many times and that he wants my subordinate gone.
After discussing what has gone on with my wife, she said to keep out of it.
If I do so, the pattern will continue to repeat itself. So I am looking for a list of actionable points I can take away to resolve this situation and prevent it happening again if at all possible.
management politics deadlines
As conformed by "My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint" and "The subordinate has a history of ignoring the chain of command". Pink slip time. Show him the door. Give him the sack. Fire him. DTMFA.
– Mawg
Nov 27 at 9:31
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
My grand boss has communicated out an unrealistic expectation to the board that we are unable to meet.
My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint.
The subordinate has a history of ignoring the chain of command and going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point and I asked my grand boss what could be done to help us meet the expectations set, such as overtime and mentoring. My grand boss agreed to both but said no matter what we have to deliver on the date said.
I told my grand boss that my subordinate had put a complaint in about my grand boss and my grand boss responded saying that this has happened one too many times and that he wants my subordinate gone.
After discussing what has gone on with my wife, she said to keep out of it.
If I do so, the pattern will continue to repeat itself. So I am looking for a list of actionable points I can take away to resolve this situation and prevent it happening again if at all possible.
management politics deadlines
My grand boss has communicated out an unrealistic expectation to the board that we are unable to meet.
My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint.
The subordinate has a history of ignoring the chain of command and going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point and I asked my grand boss what could be done to help us meet the expectations set, such as overtime and mentoring. My grand boss agreed to both but said no matter what we have to deliver on the date said.
I told my grand boss that my subordinate had put a complaint in about my grand boss and my grand boss responded saying that this has happened one too many times and that he wants my subordinate gone.
After discussing what has gone on with my wife, she said to keep out of it.
If I do so, the pattern will continue to repeat itself. So I am looking for a list of actionable points I can take away to resolve this situation and prevent it happening again if at all possible.
management politics deadlines
management politics deadlines
asked Nov 26 at 19:09
professor of programming 웃
1,3911719
1,3911719
As conformed by "My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint" and "The subordinate has a history of ignoring the chain of command". Pink slip time. Show him the door. Give him the sack. Fire him. DTMFA.
– Mawg
Nov 27 at 9:31
add a comment |
As conformed by "My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint" and "The subordinate has a history of ignoring the chain of command". Pink slip time. Show him the door. Give him the sack. Fire him. DTMFA.
– Mawg
Nov 27 at 9:31
As conformed by "My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint" and "The subordinate has a history of ignoring the chain of command". Pink slip time. Show him the door. Give him the sack. Fire him. DTMFA.
– Mawg
Nov 27 at 9:31
As conformed by "My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint" and "The subordinate has a history of ignoring the chain of command". Pink slip time. Show him the door. Give him the sack. Fire him. DTMFA.
– Mawg
Nov 27 at 9:31
add a comment |
3 Answers
3
active
oldest
votes
up vote
7
down vote
I see two issues:
- The grand boss set an unrealistic deadline.
Take a look at the PM iron triangle. I've heard this paraphrased as "Features, Resources, Delivery Date - pick two". It means that if the boss has specified the delivery date and the resources (i.e., you can't hire 20 more people quickly enough), then the features delivered will be whatever they are.
Note that you can sometimes juggle features and quality - deliver 2 great features and 5 horrible ones, or deliver 7 terrible-but-not-quite-horrible features. Another option is 3 great features only - the others remain undone.
You'll need to negotiate with the grand boss on this and have him prioritize.
Whatever you do, just know that this is a separate issue that has nothing to do with the subordinate.
- Your subordinate has a history of ignoring company hierarchy.
This one's easy. As Joe Strazzere mentioned in a comment, fire the subordinate. Ignoring the hierarchy is extremely disrespectful much in the same way that throwing a brick at someone's face is considered impolite.
You should start the process by meeting with your grand boss and HR. Expect them to guide you through the process. They'll know exactly what documentation you'll need, what warnings you'll need to give, etc. The process may take a long time, but it will be worth it in the end.
I'm assuming (perhaps incorrectly) that you're in the US. Please let me know if I'm wrong
– Dan Pichelman
Nov 26 at 19:40
@JoeStrazzere in that case firing the subordinate may be more difficult but hopefully not impossible.
– Dan Pichelman
Nov 26 at 20:03
Firing the subordinate would be challenging, so would it be sensible to give a written warning first?
– professor of programming 웃
Nov 26 at 20:43
3
Talk to your grand boss and/or HR about giving written warnings. A badly composed written warning could cause a lot of the kind of trouble that HR exists to prevent.
– Dan Pichelman
Nov 26 at 20:55
@DanPichelman The grand boss doesn't want to participate in the actual firing. HR is the place to go.
– David Thornley
Nov 26 at 21:40
|
show 2 more comments
up vote
1
down vote
Your subordinate has a history of this behavior. Your grand boss verbatim told you this happened one too many times. You will be doing some fighting if you want to keep this person. I am assuming this issue was addressed before with the expectation it would not happen again. And yet it happened again.
So the question is do you want to fight for a subordinate that repeatedly goes behind your back and damages your reputation? I'd say you already tried and it did not work. There is not much you can do except to let your subordinate go.
Why would you want to keep someone who shows you so much disrespect?
– Mawg
Nov 27 at 9:41
add a comment |
up vote
1
down vote
TL;DR Fire the subordinate
The subordinate has a history of ignoring the chain of command and
going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point
The problem is that subordinate has "cried wolf" too many times to where their opinion is not valued anymore. It's likely the previous instances of jumping the chain of command were not warranted. Even though your subordinate may have a valid point, they've burn all of the credibility in the company, which makes their word worthless.
I recommend you fire the subordinate and work with the grand boss' on setting realistic deliverable without the subordinate's backing.
add a comment |
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();
}
}
});
});
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
I see two issues:
- The grand boss set an unrealistic deadline.
Take a look at the PM iron triangle. I've heard this paraphrased as "Features, Resources, Delivery Date - pick two". It means that if the boss has specified the delivery date and the resources (i.e., you can't hire 20 more people quickly enough), then the features delivered will be whatever they are.
Note that you can sometimes juggle features and quality - deliver 2 great features and 5 horrible ones, or deliver 7 terrible-but-not-quite-horrible features. Another option is 3 great features only - the others remain undone.
You'll need to negotiate with the grand boss on this and have him prioritize.
Whatever you do, just know that this is a separate issue that has nothing to do with the subordinate.
- Your subordinate has a history of ignoring company hierarchy.
This one's easy. As Joe Strazzere mentioned in a comment, fire the subordinate. Ignoring the hierarchy is extremely disrespectful much in the same way that throwing a brick at someone's face is considered impolite.
You should start the process by meeting with your grand boss and HR. Expect them to guide you through the process. They'll know exactly what documentation you'll need, what warnings you'll need to give, etc. The process may take a long time, but it will be worth it in the end.
I'm assuming (perhaps incorrectly) that you're in the US. Please let me know if I'm wrong
– Dan Pichelman
Nov 26 at 19:40
@JoeStrazzere in that case firing the subordinate may be more difficult but hopefully not impossible.
– Dan Pichelman
Nov 26 at 20:03
Firing the subordinate would be challenging, so would it be sensible to give a written warning first?
– professor of programming 웃
Nov 26 at 20:43
3
Talk to your grand boss and/or HR about giving written warnings. A badly composed written warning could cause a lot of the kind of trouble that HR exists to prevent.
– Dan Pichelman
Nov 26 at 20:55
@DanPichelman The grand boss doesn't want to participate in the actual firing. HR is the place to go.
– David Thornley
Nov 26 at 21:40
|
show 2 more comments
up vote
7
down vote
I see two issues:
- The grand boss set an unrealistic deadline.
Take a look at the PM iron triangle. I've heard this paraphrased as "Features, Resources, Delivery Date - pick two". It means that if the boss has specified the delivery date and the resources (i.e., you can't hire 20 more people quickly enough), then the features delivered will be whatever they are.
Note that you can sometimes juggle features and quality - deliver 2 great features and 5 horrible ones, or deliver 7 terrible-but-not-quite-horrible features. Another option is 3 great features only - the others remain undone.
You'll need to negotiate with the grand boss on this and have him prioritize.
Whatever you do, just know that this is a separate issue that has nothing to do with the subordinate.
- Your subordinate has a history of ignoring company hierarchy.
This one's easy. As Joe Strazzere mentioned in a comment, fire the subordinate. Ignoring the hierarchy is extremely disrespectful much in the same way that throwing a brick at someone's face is considered impolite.
You should start the process by meeting with your grand boss and HR. Expect them to guide you through the process. They'll know exactly what documentation you'll need, what warnings you'll need to give, etc. The process may take a long time, but it will be worth it in the end.
I'm assuming (perhaps incorrectly) that you're in the US. Please let me know if I'm wrong
– Dan Pichelman
Nov 26 at 19:40
@JoeStrazzere in that case firing the subordinate may be more difficult but hopefully not impossible.
– Dan Pichelman
Nov 26 at 20:03
Firing the subordinate would be challenging, so would it be sensible to give a written warning first?
– professor of programming 웃
Nov 26 at 20:43
3
Talk to your grand boss and/or HR about giving written warnings. A badly composed written warning could cause a lot of the kind of trouble that HR exists to prevent.
– Dan Pichelman
Nov 26 at 20:55
@DanPichelman The grand boss doesn't want to participate in the actual firing. HR is the place to go.
– David Thornley
Nov 26 at 21:40
|
show 2 more comments
up vote
7
down vote
up vote
7
down vote
I see two issues:
- The grand boss set an unrealistic deadline.
Take a look at the PM iron triangle. I've heard this paraphrased as "Features, Resources, Delivery Date - pick two". It means that if the boss has specified the delivery date and the resources (i.e., you can't hire 20 more people quickly enough), then the features delivered will be whatever they are.
Note that you can sometimes juggle features and quality - deliver 2 great features and 5 horrible ones, or deliver 7 terrible-but-not-quite-horrible features. Another option is 3 great features only - the others remain undone.
You'll need to negotiate with the grand boss on this and have him prioritize.
Whatever you do, just know that this is a separate issue that has nothing to do with the subordinate.
- Your subordinate has a history of ignoring company hierarchy.
This one's easy. As Joe Strazzere mentioned in a comment, fire the subordinate. Ignoring the hierarchy is extremely disrespectful much in the same way that throwing a brick at someone's face is considered impolite.
You should start the process by meeting with your grand boss and HR. Expect them to guide you through the process. They'll know exactly what documentation you'll need, what warnings you'll need to give, etc. The process may take a long time, but it will be worth it in the end.
I see two issues:
- The grand boss set an unrealistic deadline.
Take a look at the PM iron triangle. I've heard this paraphrased as "Features, Resources, Delivery Date - pick two". It means that if the boss has specified the delivery date and the resources (i.e., you can't hire 20 more people quickly enough), then the features delivered will be whatever they are.
Note that you can sometimes juggle features and quality - deliver 2 great features and 5 horrible ones, or deliver 7 terrible-but-not-quite-horrible features. Another option is 3 great features only - the others remain undone.
You'll need to negotiate with the grand boss on this and have him prioritize.
Whatever you do, just know that this is a separate issue that has nothing to do with the subordinate.
- Your subordinate has a history of ignoring company hierarchy.
This one's easy. As Joe Strazzere mentioned in a comment, fire the subordinate. Ignoring the hierarchy is extremely disrespectful much in the same way that throwing a brick at someone's face is considered impolite.
You should start the process by meeting with your grand boss and HR. Expect them to guide you through the process. They'll know exactly what documentation you'll need, what warnings you'll need to give, etc. The process may take a long time, but it will be worth it in the end.
edited Nov 26 at 20:53
answered Nov 26 at 19:40
Dan Pichelman
26.5k127487
26.5k127487
I'm assuming (perhaps incorrectly) that you're in the US. Please let me know if I'm wrong
– Dan Pichelman
Nov 26 at 19:40
@JoeStrazzere in that case firing the subordinate may be more difficult but hopefully not impossible.
– Dan Pichelman
Nov 26 at 20:03
Firing the subordinate would be challenging, so would it be sensible to give a written warning first?
– professor of programming 웃
Nov 26 at 20:43
3
Talk to your grand boss and/or HR about giving written warnings. A badly composed written warning could cause a lot of the kind of trouble that HR exists to prevent.
– Dan Pichelman
Nov 26 at 20:55
@DanPichelman The grand boss doesn't want to participate in the actual firing. HR is the place to go.
– David Thornley
Nov 26 at 21:40
|
show 2 more comments
I'm assuming (perhaps incorrectly) that you're in the US. Please let me know if I'm wrong
– Dan Pichelman
Nov 26 at 19:40
@JoeStrazzere in that case firing the subordinate may be more difficult but hopefully not impossible.
– Dan Pichelman
Nov 26 at 20:03
Firing the subordinate would be challenging, so would it be sensible to give a written warning first?
– professor of programming 웃
Nov 26 at 20:43
3
Talk to your grand boss and/or HR about giving written warnings. A badly composed written warning could cause a lot of the kind of trouble that HR exists to prevent.
– Dan Pichelman
Nov 26 at 20:55
@DanPichelman The grand boss doesn't want to participate in the actual firing. HR is the place to go.
– David Thornley
Nov 26 at 21:40
I'm assuming (perhaps incorrectly) that you're in the US. Please let me know if I'm wrong
– Dan Pichelman
Nov 26 at 19:40
I'm assuming (perhaps incorrectly) that you're in the US. Please let me know if I'm wrong
– Dan Pichelman
Nov 26 at 19:40
@JoeStrazzere in that case firing the subordinate may be more difficult but hopefully not impossible.
– Dan Pichelman
Nov 26 at 20:03
@JoeStrazzere in that case firing the subordinate may be more difficult but hopefully not impossible.
– Dan Pichelman
Nov 26 at 20:03
Firing the subordinate would be challenging, so would it be sensible to give a written warning first?
– professor of programming 웃
Nov 26 at 20:43
Firing the subordinate would be challenging, so would it be sensible to give a written warning first?
– professor of programming 웃
Nov 26 at 20:43
3
3
Talk to your grand boss and/or HR about giving written warnings. A badly composed written warning could cause a lot of the kind of trouble that HR exists to prevent.
– Dan Pichelman
Nov 26 at 20:55
Talk to your grand boss and/or HR about giving written warnings. A badly composed written warning could cause a lot of the kind of trouble that HR exists to prevent.
– Dan Pichelman
Nov 26 at 20:55
@DanPichelman The grand boss doesn't want to participate in the actual firing. HR is the place to go.
– David Thornley
Nov 26 at 21:40
@DanPichelman The grand boss doesn't want to participate in the actual firing. HR is the place to go.
– David Thornley
Nov 26 at 21:40
|
show 2 more comments
up vote
1
down vote
Your subordinate has a history of this behavior. Your grand boss verbatim told you this happened one too many times. You will be doing some fighting if you want to keep this person. I am assuming this issue was addressed before with the expectation it would not happen again. And yet it happened again.
So the question is do you want to fight for a subordinate that repeatedly goes behind your back and damages your reputation? I'd say you already tried and it did not work. There is not much you can do except to let your subordinate go.
Why would you want to keep someone who shows you so much disrespect?
– Mawg
Nov 27 at 9:41
add a comment |
up vote
1
down vote
Your subordinate has a history of this behavior. Your grand boss verbatim told you this happened one too many times. You will be doing some fighting if you want to keep this person. I am assuming this issue was addressed before with the expectation it would not happen again. And yet it happened again.
So the question is do you want to fight for a subordinate that repeatedly goes behind your back and damages your reputation? I'd say you already tried and it did not work. There is not much you can do except to let your subordinate go.
Why would you want to keep someone who shows you so much disrespect?
– Mawg
Nov 27 at 9:41
add a comment |
up vote
1
down vote
up vote
1
down vote
Your subordinate has a history of this behavior. Your grand boss verbatim told you this happened one too many times. You will be doing some fighting if you want to keep this person. I am assuming this issue was addressed before with the expectation it would not happen again. And yet it happened again.
So the question is do you want to fight for a subordinate that repeatedly goes behind your back and damages your reputation? I'd say you already tried and it did not work. There is not much you can do except to let your subordinate go.
Your subordinate has a history of this behavior. Your grand boss verbatim told you this happened one too many times. You will be doing some fighting if you want to keep this person. I am assuming this issue was addressed before with the expectation it would not happen again. And yet it happened again.
So the question is do you want to fight for a subordinate that repeatedly goes behind your back and damages your reputation? I'd say you already tried and it did not work. There is not much you can do except to let your subordinate go.
answered Nov 26 at 19:42
Victor S
1,17815
1,17815
Why would you want to keep someone who shows you so much disrespect?
– Mawg
Nov 27 at 9:41
add a comment |
Why would you want to keep someone who shows you so much disrespect?
– Mawg
Nov 27 at 9:41
Why would you want to keep someone who shows you so much disrespect?
– Mawg
Nov 27 at 9:41
Why would you want to keep someone who shows you so much disrespect?
– Mawg
Nov 27 at 9:41
add a comment |
up vote
1
down vote
TL;DR Fire the subordinate
The subordinate has a history of ignoring the chain of command and
going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point
The problem is that subordinate has "cried wolf" too many times to where their opinion is not valued anymore. It's likely the previous instances of jumping the chain of command were not warranted. Even though your subordinate may have a valid point, they've burn all of the credibility in the company, which makes their word worthless.
I recommend you fire the subordinate and work with the grand boss' on setting realistic deliverable without the subordinate's backing.
add a comment |
up vote
1
down vote
TL;DR Fire the subordinate
The subordinate has a history of ignoring the chain of command and
going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point
The problem is that subordinate has "cried wolf" too many times to where their opinion is not valued anymore. It's likely the previous instances of jumping the chain of command were not warranted. Even though your subordinate may have a valid point, they've burn all of the credibility in the company, which makes their word worthless.
I recommend you fire the subordinate and work with the grand boss' on setting realistic deliverable without the subordinate's backing.
add a comment |
up vote
1
down vote
up vote
1
down vote
TL;DR Fire the subordinate
The subordinate has a history of ignoring the chain of command and
going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point
The problem is that subordinate has "cried wolf" too many times to where their opinion is not valued anymore. It's likely the previous instances of jumping the chain of command were not warranted. Even though your subordinate may have a valid point, they've burn all of the credibility in the company, which makes their word worthless.
I recommend you fire the subordinate and work with the grand boss' on setting realistic deliverable without the subordinate's backing.
TL;DR Fire the subordinate
The subordinate has a history of ignoring the chain of command and
going straight to the top so his concerns are often ignored now.
However, in this case I think he has a valid point
The problem is that subordinate has "cried wolf" too many times to where their opinion is not valued anymore. It's likely the previous instances of jumping the chain of command were not warranted. Even though your subordinate may have a valid point, they've burn all of the credibility in the company, which makes their word worthless.
I recommend you fire the subordinate and work with the grand boss' on setting realistic deliverable without the subordinate's backing.
answered Nov 26 at 21:59
jcmack
6,55411036
6,55411036
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.
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%2f123441%2fboss-setting-expectations-that-subordinates-cant-meet%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
As conformed by "My subordinate has complained to the board about my grand bosses conduct but won't elaborate to me what he said in his complaint" and "The subordinate has a history of ignoring the chain of command". Pink slip time. Show him the door. Give him the sack. Fire him. DTMFA.
– Mawg
Nov 27 at 9:31