How to make sure I'm assertive enough in contact with subordinates?How to convince colleagues about my point...
Are angels creatures (Mark 16:15) and can they repent (Rev 2:5 and Rom 8:21)
Did Amazon pay $0 in taxes last year?
3.5% Interest Student Loan or use all of my savings on Tuition?
What is "desert glass" and what does it do to the PCs?
“I had a flat in the centre of town, but I didn’t like living there, so …”
Can inspiration allow the Rogue to make a Sneak Attack?
Named nets not connected in Eagle board design
Convert an array of objects to array of the objects' values
Ultrafilters as a double dual
Is divide-by-zero a security vulnerability?
The past tense for the quoting particle って
What is Tony Stark injecting into himself in Iron Man 3?
What is better: yes / no radio, or simple checkbox?
Calculate total length of edges in select Voronoi diagram
School performs periodic password audits. Is my password compromised?
Can a Mexican citizen living in US under DACA drive to Canada?
Why dativ case for the verb widerspricht?
Are Wave equations equivalent to Maxwell equations in free space?
How to make sure I'm assertive enough in contact with subordinates?
Align equations with text before one of them
Should we avoid writing fiction about historical events without extensive research?
How do you make a gun that shoots melee weapons and/or swords?
Linear Combination of Atomic Orbitals
A bug in Excel? Conditional formatting for marking duplicates also highlights unique value
How to make sure I'm assertive enough in contact with subordinates?
How to convince colleagues about my point of view in a meeting?Is this wrongful firing? How can I make sure that I get my unemployment benefits?How can I make meetings more interesting?How to be more assertive within a senior teamJob interview: Contact with interview officer.Cannot accomplish a task I'm given - not skilled enoughAs a new teamlead, how to bring a subordinate's misconducts to attention of your managerHow to make sure a part time SysAdmin does not caught up in projects?Dealing with a colleague that talks too muchManager is upset because I asked HR to clarify a company policy after he had explained it to me
I'm a first-time manager and sometimes have difficulties judging whether my expectations towards my subordinates are realistic or not.
How assertive/ cooperative should I be in the following situation:
You work on a project with your subordinate, discuss it thoroughly. Then you meet a client (one you know very well but still, it's a client) and present the results together. After you presented a proposal, your colleague tells the client he doesn't agree that the proposal you just presented is the best one and goes on to discuss a different one.
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Btw, it's not the first time this happened.
communication management meetings
New contributor
add a comment |
I'm a first-time manager and sometimes have difficulties judging whether my expectations towards my subordinates are realistic or not.
How assertive/ cooperative should I be in the following situation:
You work on a project with your subordinate, discuss it thoroughly. Then you meet a client (one you know very well but still, it's a client) and present the results together. After you presented a proposal, your colleague tells the client he doesn't agree that the proposal you just presented is the best one and goes on to discuss a different one.
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Btw, it's not the first time this happened.
communication management meetings
New contributor
4
Before meeting with the client, did you discuss multiple proposals or just one? If multiple did you both agree to only present one to the client?
– sf02
6 hours ago
@sf02, we discussed several proposals, I welcomed their input. The proposals were... Almost equally good. But I had good reasons to recommend A, which I mentioned to them.
– user4214
6 hours ago
11
Perhaps the next time you need to make it clear to your subordinate that you are recommending proposal X and only X, but regardless let your subordinate know that the time for discussions is not when the client is present
– sf02
6 hours ago
2
The proposal should have been decided on prior to the meeting with the client. Discussions for or against a particular proposal need to be hashed out and decided beforehand and then presented to the client as a unified message.
– joeqwerty
5 hours ago
add a comment |
I'm a first-time manager and sometimes have difficulties judging whether my expectations towards my subordinates are realistic or not.
How assertive/ cooperative should I be in the following situation:
You work on a project with your subordinate, discuss it thoroughly. Then you meet a client (one you know very well but still, it's a client) and present the results together. After you presented a proposal, your colleague tells the client he doesn't agree that the proposal you just presented is the best one and goes on to discuss a different one.
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Btw, it's not the first time this happened.
communication management meetings
New contributor
I'm a first-time manager and sometimes have difficulties judging whether my expectations towards my subordinates are realistic or not.
How assertive/ cooperative should I be in the following situation:
You work on a project with your subordinate, discuss it thoroughly. Then you meet a client (one you know very well but still, it's a client) and present the results together. After you presented a proposal, your colleague tells the client he doesn't agree that the proposal you just presented is the best one and goes on to discuss a different one.
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Btw, it's not the first time this happened.
communication management meetings
communication management meetings
New contributor
New contributor
edited 6 hours ago
DarkCygnus
38.1k1883163
38.1k1883163
New contributor
asked 6 hours ago
user4214user4214
493
493
New contributor
New contributor
4
Before meeting with the client, did you discuss multiple proposals or just one? If multiple did you both agree to only present one to the client?
– sf02
6 hours ago
@sf02, we discussed several proposals, I welcomed their input. The proposals were... Almost equally good. But I had good reasons to recommend A, which I mentioned to them.
– user4214
6 hours ago
11
Perhaps the next time you need to make it clear to your subordinate that you are recommending proposal X and only X, but regardless let your subordinate know that the time for discussions is not when the client is present
– sf02
6 hours ago
2
The proposal should have been decided on prior to the meeting with the client. Discussions for or against a particular proposal need to be hashed out and decided beforehand and then presented to the client as a unified message.
– joeqwerty
5 hours ago
add a comment |
4
Before meeting with the client, did you discuss multiple proposals or just one? If multiple did you both agree to only present one to the client?
– sf02
6 hours ago
@sf02, we discussed several proposals, I welcomed their input. The proposals were... Almost equally good. But I had good reasons to recommend A, which I mentioned to them.
– user4214
6 hours ago
11
Perhaps the next time you need to make it clear to your subordinate that you are recommending proposal X and only X, but regardless let your subordinate know that the time for discussions is not when the client is present
– sf02
6 hours ago
2
The proposal should have been decided on prior to the meeting with the client. Discussions for or against a particular proposal need to be hashed out and decided beforehand and then presented to the client as a unified message.
– joeqwerty
5 hours ago
4
4
Before meeting with the client, did you discuss multiple proposals or just one? If multiple did you both agree to only present one to the client?
– sf02
6 hours ago
Before meeting with the client, did you discuss multiple proposals or just one? If multiple did you both agree to only present one to the client?
– sf02
6 hours ago
@sf02, we discussed several proposals, I welcomed their input. The proposals were... Almost equally good. But I had good reasons to recommend A, which I mentioned to them.
– user4214
6 hours ago
@sf02, we discussed several proposals, I welcomed their input. The proposals were... Almost equally good. But I had good reasons to recommend A, which I mentioned to them.
– user4214
6 hours ago
11
11
Perhaps the next time you need to make it clear to your subordinate that you are recommending proposal X and only X, but regardless let your subordinate know that the time for discussions is not when the client is present
– sf02
6 hours ago
Perhaps the next time you need to make it clear to your subordinate that you are recommending proposal X and only X, but regardless let your subordinate know that the time for discussions is not when the client is present
– sf02
6 hours ago
2
2
The proposal should have been decided on prior to the meeting with the client. Discussions for or against a particular proposal need to be hashed out and decided beforehand and then presented to the client as a unified message.
– joeqwerty
5 hours ago
The proposal should have been decided on prior to the meeting with the client. Discussions for or against a particular proposal need to be hashed out and decided beforehand and then presented to the client as a unified message.
– joeqwerty
5 hours ago
add a comment |
6 Answers
6
active
oldest
votes
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Yes, I would say that a one-on-one conversation is in place here, where you explain to your subordinate that improvising or deviating from the plan during meetings is not acceptable.
You say this is not the first time this happens, but perhaps it's the first time it happens to you as a manager, and it is important to set things straight now to avoid this from happening again.
Be firm, yet respectful, and make sure to stress that this is not acceptable behavior and that they should stick to what planned for meetings, and that they should pitch with you any ideas or suggestions for meetings before actually doing them.
add a comment |
First of all, this is worth establishing:
- We're all in this boat together.
This statement requires both of you to operate as a team. Free discussion is something that is quite desirable when the team is together and deciding execution options, but the Client should only see the final result of this discussion - an united front. Which takes us to the second statement:
- It's way better if the boat gets to the destination.
The Client may perceive this lack of well-defined roles as disorganization. This is dangerous - this affects their perception on how successful this project can be.
So we need clear roles:
- As Project Manager, you're the Mediator.
You're the one in direct contact with the client. You listen to the Client's woes, discuss with your team, and offer the Client the proposed Solution.
- Your colleague is the Specialist.
They're qualified to evaluate the scenario and offer possible outcomes.
So discuss all you want before the meeting. Raise possible scenarios and implementation options. If called upon at the Mediator's discretion the Specialist may chime in and freely discuss during a live meeting.
But no conflict of roles should transpire at a meeting with the client, at the risk of weakening the Client's reliance on the capability of your team to deliver.
Finally, answering your question:
If the best solution is to discuss it, how should I frame it?
I agree that this needs to be addressed. Show your colleague the importance of projecting an image of functional, coherent team to a client.
add a comment |
You don't need to be "bossy", but you certainly need to inform that employee of a few things:
Such behavior is a major signal to the client that your business doesn't know what it's doing. You will either not win bids, or will get fired by the client. You will have a bad reputation with that client, which will spread to any other potential clients that they talk to. This has the potential of doing major financial damage to your company and risking the livelihoods of all of you. This behavior is not acceptable and the employee must find a different way to handle the situation.
Reservations about the solution must be brought up and addressed before presentation day. At the presentation, your company must show a united front, even if there are reservations or disagreements internally.
What can you learn on your end?
Are the alternative solutions actually better, even in part?
Which solutions do the clients prefer?
Make sure everyone involved (especially everyone presenting to the client) has plenty of time to give input on the project and the presentation before final decisions are made.
Could you officially present multiple proposals with compare/contrast and cost/benefit analysis, and let the client choose which to implement?
Don't involve unnecessary personnel in presentations to clients.
New contributor
1
With regard to "don't involve unnecessary personnel" one could also stress "don't have managers relaying messages between technical teams" as this easily degrades into the party game called "telephone"
– Chris Stratton
3 hours ago
There is a definite difference between being bossy, and being the boss. And in this case the OP was not the boss, a bit of compensating bossiness would probably be useful in preventing a recurrence of such an embarrassment.
– George M
2 hours ago
add a comment |
They're not your subordinates, they're still your coworkers. If you go around thinking your better then them or that your thoughts are more valid, you're going to fail miserably. Managers aren't there to exercise tyrannical control or look good. Managers are there to make sure everyone is doing things that make the company money or otherwise meet it's goals. Suggesting that a potential solution doesn't go against that. It actually helps you reach your goal by helping you make a better decision.
Bottom line: Good managers listen to their coworkers.
add a comment |
Speaking like a boss is similar to convince the subordinates with words. Sometimes, rhetorical skills are defined as the result from training and a certain volume in the voice. But in reality it's much easier. Rhetorical skills are equal to educate the other side. If somebody is able to provide sense to a group, then the group will do what is necessary. A good boss looks like a teacher. He doesn't simple give orders, but he educates the other side.
A typical behavior of a failed communication with subordinates is, if they are trying to invert the social roles. That means, sometimes a subordinate is trying to educate the boss. There are two options available. Either the boss is smart enough to detect such behavior and is capable to integrate the subversive communication pattern, or he fails and will loose his authority to the other side. Then the boss has to ask himself, if he is trained enough in the subject.
add a comment |
Turn the Problem into a Solution
It's not really possible to know from the information presented if the sense that the manager and technical worker were in agreement was mistaken, if the technical worker thought the manager had confused the message in presenting it and that they were providing critical clarification, if it seemed the client's needs had changed, or if the technical worker specifically set out to undermine the manager in bad faith.
But rather than delve into that, perhaps it's more productive to focus on achieving a better presentation next time.
After discussion of the next project phase, the manager could assign the technical worker to the be the one to write up a specific proposal, which the manager will then approve (possibly after alterations) before the technical worker verbally presents it to the client in a joint meeting at which the written copy is also handed over.
While there is still a little room to stress differing interpretation of the words on the page, for the good faith considerations it's far more likely that the technical worker can feel that the key points have been made when they have been made in their own words. And for any bad faith concerns, there's much less room to undermine their own words.
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
});
}
});
user4214 is a new contributor. Be nice, and check out our Code of Conduct.
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%2f131097%2fhow-to-make-sure-im-assertive-enough-in-contact-with-subordinates%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();
}
}
});
});
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Yes, I would say that a one-on-one conversation is in place here, where you explain to your subordinate that improvising or deviating from the plan during meetings is not acceptable.
You say this is not the first time this happens, but perhaps it's the first time it happens to you as a manager, and it is important to set things straight now to avoid this from happening again.
Be firm, yet respectful, and make sure to stress that this is not acceptable behavior and that they should stick to what planned for meetings, and that they should pitch with you any ideas or suggestions for meetings before actually doing them.
add a comment |
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Yes, I would say that a one-on-one conversation is in place here, where you explain to your subordinate that improvising or deviating from the plan during meetings is not acceptable.
You say this is not the first time this happens, but perhaps it's the first time it happens to you as a manager, and it is important to set things straight now to avoid this from happening again.
Be firm, yet respectful, and make sure to stress that this is not acceptable behavior and that they should stick to what planned for meetings, and that they should pitch with you any ideas or suggestions for meetings before actually doing them.
add a comment |
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Yes, I would say that a one-on-one conversation is in place here, where you explain to your subordinate that improvising or deviating from the plan during meetings is not acceptable.
You say this is not the first time this happens, but perhaps it's the first time it happens to you as a manager, and it is important to set things straight now to avoid this from happening again.
Be firm, yet respectful, and make sure to stress that this is not acceptable behavior and that they should stick to what planned for meetings, and that they should pitch with you any ideas or suggestions for meetings before actually doing them.
Now, my first reaction is to have a quite serious conversation with the colleague asserting that this behavior is unacceptable. Are there any better options? If the best solution is to discuss it, how should I frame it?
Yes, I would say that a one-on-one conversation is in place here, where you explain to your subordinate that improvising or deviating from the plan during meetings is not acceptable.
You say this is not the first time this happens, but perhaps it's the first time it happens to you as a manager, and it is important to set things straight now to avoid this from happening again.
Be firm, yet respectful, and make sure to stress that this is not acceptable behavior and that they should stick to what planned for meetings, and that they should pitch with you any ideas or suggestions for meetings before actually doing them.
answered 6 hours ago
DarkCygnusDarkCygnus
38.1k1883163
38.1k1883163
add a comment |
add a comment |
First of all, this is worth establishing:
- We're all in this boat together.
This statement requires both of you to operate as a team. Free discussion is something that is quite desirable when the team is together and deciding execution options, but the Client should only see the final result of this discussion - an united front. Which takes us to the second statement:
- It's way better if the boat gets to the destination.
The Client may perceive this lack of well-defined roles as disorganization. This is dangerous - this affects their perception on how successful this project can be.
So we need clear roles:
- As Project Manager, you're the Mediator.
You're the one in direct contact with the client. You listen to the Client's woes, discuss with your team, and offer the Client the proposed Solution.
- Your colleague is the Specialist.
They're qualified to evaluate the scenario and offer possible outcomes.
So discuss all you want before the meeting. Raise possible scenarios and implementation options. If called upon at the Mediator's discretion the Specialist may chime in and freely discuss during a live meeting.
But no conflict of roles should transpire at a meeting with the client, at the risk of weakening the Client's reliance on the capability of your team to deliver.
Finally, answering your question:
If the best solution is to discuss it, how should I frame it?
I agree that this needs to be addressed. Show your colleague the importance of projecting an image of functional, coherent team to a client.
add a comment |
First of all, this is worth establishing:
- We're all in this boat together.
This statement requires both of you to operate as a team. Free discussion is something that is quite desirable when the team is together and deciding execution options, but the Client should only see the final result of this discussion - an united front. Which takes us to the second statement:
- It's way better if the boat gets to the destination.
The Client may perceive this lack of well-defined roles as disorganization. This is dangerous - this affects their perception on how successful this project can be.
So we need clear roles:
- As Project Manager, you're the Mediator.
You're the one in direct contact with the client. You listen to the Client's woes, discuss with your team, and offer the Client the proposed Solution.
- Your colleague is the Specialist.
They're qualified to evaluate the scenario and offer possible outcomes.
So discuss all you want before the meeting. Raise possible scenarios and implementation options. If called upon at the Mediator's discretion the Specialist may chime in and freely discuss during a live meeting.
But no conflict of roles should transpire at a meeting with the client, at the risk of weakening the Client's reliance on the capability of your team to deliver.
Finally, answering your question:
If the best solution is to discuss it, how should I frame it?
I agree that this needs to be addressed. Show your colleague the importance of projecting an image of functional, coherent team to a client.
add a comment |
First of all, this is worth establishing:
- We're all in this boat together.
This statement requires both of you to operate as a team. Free discussion is something that is quite desirable when the team is together and deciding execution options, but the Client should only see the final result of this discussion - an united front. Which takes us to the second statement:
- It's way better if the boat gets to the destination.
The Client may perceive this lack of well-defined roles as disorganization. This is dangerous - this affects their perception on how successful this project can be.
So we need clear roles:
- As Project Manager, you're the Mediator.
You're the one in direct contact with the client. You listen to the Client's woes, discuss with your team, and offer the Client the proposed Solution.
- Your colleague is the Specialist.
They're qualified to evaluate the scenario and offer possible outcomes.
So discuss all you want before the meeting. Raise possible scenarios and implementation options. If called upon at the Mediator's discretion the Specialist may chime in and freely discuss during a live meeting.
But no conflict of roles should transpire at a meeting with the client, at the risk of weakening the Client's reliance on the capability of your team to deliver.
Finally, answering your question:
If the best solution is to discuss it, how should I frame it?
I agree that this needs to be addressed. Show your colleague the importance of projecting an image of functional, coherent team to a client.
First of all, this is worth establishing:
- We're all in this boat together.
This statement requires both of you to operate as a team. Free discussion is something that is quite desirable when the team is together and deciding execution options, but the Client should only see the final result of this discussion - an united front. Which takes us to the second statement:
- It's way better if the boat gets to the destination.
The Client may perceive this lack of well-defined roles as disorganization. This is dangerous - this affects their perception on how successful this project can be.
So we need clear roles:
- As Project Manager, you're the Mediator.
You're the one in direct contact with the client. You listen to the Client's woes, discuss with your team, and offer the Client the proposed Solution.
- Your colleague is the Specialist.
They're qualified to evaluate the scenario and offer possible outcomes.
So discuss all you want before the meeting. Raise possible scenarios and implementation options. If called upon at the Mediator's discretion the Specialist may chime in and freely discuss during a live meeting.
But no conflict of roles should transpire at a meeting with the client, at the risk of weakening the Client's reliance on the capability of your team to deliver.
Finally, answering your question:
If the best solution is to discuss it, how should I frame it?
I agree that this needs to be addressed. Show your colleague the importance of projecting an image of functional, coherent team to a client.
edited 6 hours ago
answered 6 hours ago
OnoSendaiOnoSendai
4,00731515
4,00731515
add a comment |
add a comment |
You don't need to be "bossy", but you certainly need to inform that employee of a few things:
Such behavior is a major signal to the client that your business doesn't know what it's doing. You will either not win bids, or will get fired by the client. You will have a bad reputation with that client, which will spread to any other potential clients that they talk to. This has the potential of doing major financial damage to your company and risking the livelihoods of all of you. This behavior is not acceptable and the employee must find a different way to handle the situation.
Reservations about the solution must be brought up and addressed before presentation day. At the presentation, your company must show a united front, even if there are reservations or disagreements internally.
What can you learn on your end?
Are the alternative solutions actually better, even in part?
Which solutions do the clients prefer?
Make sure everyone involved (especially everyone presenting to the client) has plenty of time to give input on the project and the presentation before final decisions are made.
Could you officially present multiple proposals with compare/contrast and cost/benefit analysis, and let the client choose which to implement?
Don't involve unnecessary personnel in presentations to clients.
New contributor
1
With regard to "don't involve unnecessary personnel" one could also stress "don't have managers relaying messages between technical teams" as this easily degrades into the party game called "telephone"
– Chris Stratton
3 hours ago
There is a definite difference between being bossy, and being the boss. And in this case the OP was not the boss, a bit of compensating bossiness would probably be useful in preventing a recurrence of such an embarrassment.
– George M
2 hours ago
add a comment |
You don't need to be "bossy", but you certainly need to inform that employee of a few things:
Such behavior is a major signal to the client that your business doesn't know what it's doing. You will either not win bids, or will get fired by the client. You will have a bad reputation with that client, which will spread to any other potential clients that they talk to. This has the potential of doing major financial damage to your company and risking the livelihoods of all of you. This behavior is not acceptable and the employee must find a different way to handle the situation.
Reservations about the solution must be brought up and addressed before presentation day. At the presentation, your company must show a united front, even if there are reservations or disagreements internally.
What can you learn on your end?
Are the alternative solutions actually better, even in part?
Which solutions do the clients prefer?
Make sure everyone involved (especially everyone presenting to the client) has plenty of time to give input on the project and the presentation before final decisions are made.
Could you officially present multiple proposals with compare/contrast and cost/benefit analysis, and let the client choose which to implement?
Don't involve unnecessary personnel in presentations to clients.
New contributor
1
With regard to "don't involve unnecessary personnel" one could also stress "don't have managers relaying messages between technical teams" as this easily degrades into the party game called "telephone"
– Chris Stratton
3 hours ago
There is a definite difference between being bossy, and being the boss. And in this case the OP was not the boss, a bit of compensating bossiness would probably be useful in preventing a recurrence of such an embarrassment.
– George M
2 hours ago
add a comment |
You don't need to be "bossy", but you certainly need to inform that employee of a few things:
Such behavior is a major signal to the client that your business doesn't know what it's doing. You will either not win bids, or will get fired by the client. You will have a bad reputation with that client, which will spread to any other potential clients that they talk to. This has the potential of doing major financial damage to your company and risking the livelihoods of all of you. This behavior is not acceptable and the employee must find a different way to handle the situation.
Reservations about the solution must be brought up and addressed before presentation day. At the presentation, your company must show a united front, even if there are reservations or disagreements internally.
What can you learn on your end?
Are the alternative solutions actually better, even in part?
Which solutions do the clients prefer?
Make sure everyone involved (especially everyone presenting to the client) has plenty of time to give input on the project and the presentation before final decisions are made.
Could you officially present multiple proposals with compare/contrast and cost/benefit analysis, and let the client choose which to implement?
Don't involve unnecessary personnel in presentations to clients.
New contributor
You don't need to be "bossy", but you certainly need to inform that employee of a few things:
Such behavior is a major signal to the client that your business doesn't know what it's doing. You will either not win bids, or will get fired by the client. You will have a bad reputation with that client, which will spread to any other potential clients that they talk to. This has the potential of doing major financial damage to your company and risking the livelihoods of all of you. This behavior is not acceptable and the employee must find a different way to handle the situation.
Reservations about the solution must be brought up and addressed before presentation day. At the presentation, your company must show a united front, even if there are reservations or disagreements internally.
What can you learn on your end?
Are the alternative solutions actually better, even in part?
Which solutions do the clients prefer?
Make sure everyone involved (especially everyone presenting to the client) has plenty of time to give input on the project and the presentation before final decisions are made.
Could you officially present multiple proposals with compare/contrast and cost/benefit analysis, and let the client choose which to implement?
Don't involve unnecessary personnel in presentations to clients.
New contributor
New contributor
answered 4 hours ago
TimTim
611
611
New contributor
New contributor
1
With regard to "don't involve unnecessary personnel" one could also stress "don't have managers relaying messages between technical teams" as this easily degrades into the party game called "telephone"
– Chris Stratton
3 hours ago
There is a definite difference between being bossy, and being the boss. And in this case the OP was not the boss, a bit of compensating bossiness would probably be useful in preventing a recurrence of such an embarrassment.
– George M
2 hours ago
add a comment |
1
With regard to "don't involve unnecessary personnel" one could also stress "don't have managers relaying messages between technical teams" as this easily degrades into the party game called "telephone"
– Chris Stratton
3 hours ago
There is a definite difference between being bossy, and being the boss. And in this case the OP was not the boss, a bit of compensating bossiness would probably be useful in preventing a recurrence of such an embarrassment.
– George M
2 hours ago
1
1
With regard to "don't involve unnecessary personnel" one could also stress "don't have managers relaying messages between technical teams" as this easily degrades into the party game called "telephone"
– Chris Stratton
3 hours ago
With regard to "don't involve unnecessary personnel" one could also stress "don't have managers relaying messages between technical teams" as this easily degrades into the party game called "telephone"
– Chris Stratton
3 hours ago
There is a definite difference between being bossy, and being the boss. And in this case the OP was not the boss, a bit of compensating bossiness would probably be useful in preventing a recurrence of such an embarrassment.
– George M
2 hours ago
There is a definite difference between being bossy, and being the boss. And in this case the OP was not the boss, a bit of compensating bossiness would probably be useful in preventing a recurrence of such an embarrassment.
– George M
2 hours ago
add a comment |
They're not your subordinates, they're still your coworkers. If you go around thinking your better then them or that your thoughts are more valid, you're going to fail miserably. Managers aren't there to exercise tyrannical control or look good. Managers are there to make sure everyone is doing things that make the company money or otherwise meet it's goals. Suggesting that a potential solution doesn't go against that. It actually helps you reach your goal by helping you make a better decision.
Bottom line: Good managers listen to their coworkers.
add a comment |
They're not your subordinates, they're still your coworkers. If you go around thinking your better then them or that your thoughts are more valid, you're going to fail miserably. Managers aren't there to exercise tyrannical control or look good. Managers are there to make sure everyone is doing things that make the company money or otherwise meet it's goals. Suggesting that a potential solution doesn't go against that. It actually helps you reach your goal by helping you make a better decision.
Bottom line: Good managers listen to their coworkers.
add a comment |
They're not your subordinates, they're still your coworkers. If you go around thinking your better then them or that your thoughts are more valid, you're going to fail miserably. Managers aren't there to exercise tyrannical control or look good. Managers are there to make sure everyone is doing things that make the company money or otherwise meet it's goals. Suggesting that a potential solution doesn't go against that. It actually helps you reach your goal by helping you make a better decision.
Bottom line: Good managers listen to their coworkers.
They're not your subordinates, they're still your coworkers. If you go around thinking your better then them or that your thoughts are more valid, you're going to fail miserably. Managers aren't there to exercise tyrannical control or look good. Managers are there to make sure everyone is doing things that make the company money or otherwise meet it's goals. Suggesting that a potential solution doesn't go against that. It actually helps you reach your goal by helping you make a better decision.
Bottom line: Good managers listen to their coworkers.
answered 1 hour ago
SteveSteve
3,053618
3,053618
add a comment |
add a comment |
Speaking like a boss is similar to convince the subordinates with words. Sometimes, rhetorical skills are defined as the result from training and a certain volume in the voice. But in reality it's much easier. Rhetorical skills are equal to educate the other side. If somebody is able to provide sense to a group, then the group will do what is necessary. A good boss looks like a teacher. He doesn't simple give orders, but he educates the other side.
A typical behavior of a failed communication with subordinates is, if they are trying to invert the social roles. That means, sometimes a subordinate is trying to educate the boss. There are two options available. Either the boss is smart enough to detect such behavior and is capable to integrate the subversive communication pattern, or he fails and will loose his authority to the other side. Then the boss has to ask himself, if he is trained enough in the subject.
add a comment |
Speaking like a boss is similar to convince the subordinates with words. Sometimes, rhetorical skills are defined as the result from training and a certain volume in the voice. But in reality it's much easier. Rhetorical skills are equal to educate the other side. If somebody is able to provide sense to a group, then the group will do what is necessary. A good boss looks like a teacher. He doesn't simple give orders, but he educates the other side.
A typical behavior of a failed communication with subordinates is, if they are trying to invert the social roles. That means, sometimes a subordinate is trying to educate the boss. There are two options available. Either the boss is smart enough to detect such behavior and is capable to integrate the subversive communication pattern, or he fails and will loose his authority to the other side. Then the boss has to ask himself, if he is trained enough in the subject.
add a comment |
Speaking like a boss is similar to convince the subordinates with words. Sometimes, rhetorical skills are defined as the result from training and a certain volume in the voice. But in reality it's much easier. Rhetorical skills are equal to educate the other side. If somebody is able to provide sense to a group, then the group will do what is necessary. A good boss looks like a teacher. He doesn't simple give orders, but he educates the other side.
A typical behavior of a failed communication with subordinates is, if they are trying to invert the social roles. That means, sometimes a subordinate is trying to educate the boss. There are two options available. Either the boss is smart enough to detect such behavior and is capable to integrate the subversive communication pattern, or he fails and will loose his authority to the other side. Then the boss has to ask himself, if he is trained enough in the subject.
Speaking like a boss is similar to convince the subordinates with words. Sometimes, rhetorical skills are defined as the result from training and a certain volume in the voice. But in reality it's much easier. Rhetorical skills are equal to educate the other side. If somebody is able to provide sense to a group, then the group will do what is necessary. A good boss looks like a teacher. He doesn't simple give orders, but he educates the other side.
A typical behavior of a failed communication with subordinates is, if they are trying to invert the social roles. That means, sometimes a subordinate is trying to educate the boss. There are two options available. Either the boss is smart enough to detect such behavior and is capable to integrate the subversive communication pattern, or he fails and will loose his authority to the other side. Then the boss has to ask himself, if he is trained enough in the subject.
answered 2 hours ago
Manuel RodriguezManuel Rodriguez
1195
1195
add a comment |
add a comment |
Turn the Problem into a Solution
It's not really possible to know from the information presented if the sense that the manager and technical worker were in agreement was mistaken, if the technical worker thought the manager had confused the message in presenting it and that they were providing critical clarification, if it seemed the client's needs had changed, or if the technical worker specifically set out to undermine the manager in bad faith.
But rather than delve into that, perhaps it's more productive to focus on achieving a better presentation next time.
After discussion of the next project phase, the manager could assign the technical worker to the be the one to write up a specific proposal, which the manager will then approve (possibly after alterations) before the technical worker verbally presents it to the client in a joint meeting at which the written copy is also handed over.
While there is still a little room to stress differing interpretation of the words on the page, for the good faith considerations it's far more likely that the technical worker can feel that the key points have been made when they have been made in their own words. And for any bad faith concerns, there's much less room to undermine their own words.
add a comment |
Turn the Problem into a Solution
It's not really possible to know from the information presented if the sense that the manager and technical worker were in agreement was mistaken, if the technical worker thought the manager had confused the message in presenting it and that they were providing critical clarification, if it seemed the client's needs had changed, or if the technical worker specifically set out to undermine the manager in bad faith.
But rather than delve into that, perhaps it's more productive to focus on achieving a better presentation next time.
After discussion of the next project phase, the manager could assign the technical worker to the be the one to write up a specific proposal, which the manager will then approve (possibly after alterations) before the technical worker verbally presents it to the client in a joint meeting at which the written copy is also handed over.
While there is still a little room to stress differing interpretation of the words on the page, for the good faith considerations it's far more likely that the technical worker can feel that the key points have been made when they have been made in their own words. And for any bad faith concerns, there's much less room to undermine their own words.
add a comment |
Turn the Problem into a Solution
It's not really possible to know from the information presented if the sense that the manager and technical worker were in agreement was mistaken, if the technical worker thought the manager had confused the message in presenting it and that they were providing critical clarification, if it seemed the client's needs had changed, or if the technical worker specifically set out to undermine the manager in bad faith.
But rather than delve into that, perhaps it's more productive to focus on achieving a better presentation next time.
After discussion of the next project phase, the manager could assign the technical worker to the be the one to write up a specific proposal, which the manager will then approve (possibly after alterations) before the technical worker verbally presents it to the client in a joint meeting at which the written copy is also handed over.
While there is still a little room to stress differing interpretation of the words on the page, for the good faith considerations it's far more likely that the technical worker can feel that the key points have been made when they have been made in their own words. And for any bad faith concerns, there's much less room to undermine their own words.
Turn the Problem into a Solution
It's not really possible to know from the information presented if the sense that the manager and technical worker were in agreement was mistaken, if the technical worker thought the manager had confused the message in presenting it and that they were providing critical clarification, if it seemed the client's needs had changed, or if the technical worker specifically set out to undermine the manager in bad faith.
But rather than delve into that, perhaps it's more productive to focus on achieving a better presentation next time.
After discussion of the next project phase, the manager could assign the technical worker to the be the one to write up a specific proposal, which the manager will then approve (possibly after alterations) before the technical worker verbally presents it to the client in a joint meeting at which the written copy is also handed over.
While there is still a little room to stress differing interpretation of the words on the page, for the good faith considerations it's far more likely that the technical worker can feel that the key points have been made when they have been made in their own words. And for any bad faith concerns, there's much less room to undermine their own words.
edited 2 hours ago
answered 3 hours ago
Chris StrattonChris Stratton
576510
576510
add a comment |
add a comment |
user4214 is a new contributor. Be nice, and check out our Code of Conduct.
user4214 is a new contributor. Be nice, and check out our Code of Conduct.
user4214 is a new contributor. Be nice, and check out our Code of Conduct.
user4214 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.
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%2f131097%2fhow-to-make-sure-im-assertive-enough-in-contact-with-subordinates%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
4
Before meeting with the client, did you discuss multiple proposals or just one? If multiple did you both agree to only present one to the client?
– sf02
6 hours ago
@sf02, we discussed several proposals, I welcomed their input. The proposals were... Almost equally good. But I had good reasons to recommend A, which I mentioned to them.
– user4214
6 hours ago
11
Perhaps the next time you need to make it clear to your subordinate that you are recommending proposal X and only X, but regardless let your subordinate know that the time for discussions is not when the client is present
– sf02
6 hours ago
2
The proposal should have been decided on prior to the meeting with the client. Discussions for or against a particular proposal need to be hashed out and decided beforehand and then presented to the client as a unified message.
– joeqwerty
5 hours ago