How to handle conversations where I don't have authority to make decisions?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
5
down vote
favorite
I'm an engineer. When I talk to customers, I can sometimes make small promises like "I'll fix that bug for you" or "I'll change that color for you" but I can't promise anything that involves a time commitment or spending money -- my boss has to do that.
I'm starting to notice that my boss has a habit of asking me to talk to customers in situations where he knows the customer wants something I can't promise. I think his reasoning goes like this: say customer wants X, and X costs money. If the customer asks my boss for X, he has to say yes or no, but if the customer asks me for X, I can't answer so we have to discuss X Y and Z first and then give all the information to my boss so that he can make a decision. That way he gets to understand all the options before having to commit to one of them.
The problem for me is that this leads to a lot of awkward conversations. Sometimes the customer's position is that they need X or they will drop our business, but they don't like to say that to an engineer. People don't like to tell engineers that they're going to drop their product because they know the engineer is emotionally invested. So they begrudgingly go over Y and Z with me even though they don't really care. Other times customers will launch complaints at me about my boss, or try to get me to insert my own opinion about whether X is the right solution.
How do I manage these conversations professionally without either putting my boss in a bind by preempting his decision or appearing to be rude to the customer by resisting obvious or necessary solutions?
professionalism customer-service
suggest improvements |Â
up vote
5
down vote
favorite
I'm an engineer. When I talk to customers, I can sometimes make small promises like "I'll fix that bug for you" or "I'll change that color for you" but I can't promise anything that involves a time commitment or spending money -- my boss has to do that.
I'm starting to notice that my boss has a habit of asking me to talk to customers in situations where he knows the customer wants something I can't promise. I think his reasoning goes like this: say customer wants X, and X costs money. If the customer asks my boss for X, he has to say yes or no, but if the customer asks me for X, I can't answer so we have to discuss X Y and Z first and then give all the information to my boss so that he can make a decision. That way he gets to understand all the options before having to commit to one of them.
The problem for me is that this leads to a lot of awkward conversations. Sometimes the customer's position is that they need X or they will drop our business, but they don't like to say that to an engineer. People don't like to tell engineers that they're going to drop their product because they know the engineer is emotionally invested. So they begrudgingly go over Y and Z with me even though they don't really care. Other times customers will launch complaints at me about my boss, or try to get me to insert my own opinion about whether X is the right solution.
How do I manage these conversations professionally without either putting my boss in a bind by preempting his decision or appearing to be rude to the customer by resisting obvious or necessary solutions?
professionalism customer-service
Is it possible that your boss is trying to pass more responsibility to you and/or see how you perform in such tricky situations?
– Recct
Feb 26 '16 at 15:32
suggest improvements |Â
up vote
5
down vote
favorite
up vote
5
down vote
favorite
I'm an engineer. When I talk to customers, I can sometimes make small promises like "I'll fix that bug for you" or "I'll change that color for you" but I can't promise anything that involves a time commitment or spending money -- my boss has to do that.
I'm starting to notice that my boss has a habit of asking me to talk to customers in situations where he knows the customer wants something I can't promise. I think his reasoning goes like this: say customer wants X, and X costs money. If the customer asks my boss for X, he has to say yes or no, but if the customer asks me for X, I can't answer so we have to discuss X Y and Z first and then give all the information to my boss so that he can make a decision. That way he gets to understand all the options before having to commit to one of them.
The problem for me is that this leads to a lot of awkward conversations. Sometimes the customer's position is that they need X or they will drop our business, but they don't like to say that to an engineer. People don't like to tell engineers that they're going to drop their product because they know the engineer is emotionally invested. So they begrudgingly go over Y and Z with me even though they don't really care. Other times customers will launch complaints at me about my boss, or try to get me to insert my own opinion about whether X is the right solution.
How do I manage these conversations professionally without either putting my boss in a bind by preempting his decision or appearing to be rude to the customer by resisting obvious or necessary solutions?
professionalism customer-service
I'm an engineer. When I talk to customers, I can sometimes make small promises like "I'll fix that bug for you" or "I'll change that color for you" but I can't promise anything that involves a time commitment or spending money -- my boss has to do that.
I'm starting to notice that my boss has a habit of asking me to talk to customers in situations where he knows the customer wants something I can't promise. I think his reasoning goes like this: say customer wants X, and X costs money. If the customer asks my boss for X, he has to say yes or no, but if the customer asks me for X, I can't answer so we have to discuss X Y and Z first and then give all the information to my boss so that he can make a decision. That way he gets to understand all the options before having to commit to one of them.
The problem for me is that this leads to a lot of awkward conversations. Sometimes the customer's position is that they need X or they will drop our business, but they don't like to say that to an engineer. People don't like to tell engineers that they're going to drop their product because they know the engineer is emotionally invested. So they begrudgingly go over Y and Z with me even though they don't really care. Other times customers will launch complaints at me about my boss, or try to get me to insert my own opinion about whether X is the right solution.
How do I manage these conversations professionally without either putting my boss in a bind by preempting his decision or appearing to be rude to the customer by resisting obvious or necessary solutions?
professionalism customer-service
asked Feb 26 '16 at 6:04
Sollae
292
292
Is it possible that your boss is trying to pass more responsibility to you and/or see how you perform in such tricky situations?
– Recct
Feb 26 '16 at 15:32
suggest improvements |Â
Is it possible that your boss is trying to pass more responsibility to you and/or see how you perform in such tricky situations?
– Recct
Feb 26 '16 at 15:32
Is it possible that your boss is trying to pass more responsibility to you and/or see how you perform in such tricky situations?
– Recct
Feb 26 '16 at 15:32
Is it possible that your boss is trying to pass more responsibility to you and/or see how you perform in such tricky situations?
– Recct
Feb 26 '16 at 15:32
suggest improvements |Â
1 Answer
1
active
oldest
votes
up vote
8
down vote
More or less as you've said it, but perhaps worded something like:
Sorry, but I don't have the authority to discuss time frames on future feature sets. I can raise it with my boss when I get back to the office, and he will contact you presently.
It's something that can't really be challenged (you don't have the authority), yet it defers it back to the boss. If you see the same client again and they ask if you'd discussed it with your boss, you can truthfully answer:
I passed on your request. I'm sorry, you will have to contact my boss to see where it's at.
This last bit may seem silly, but if you have passed it on, and it's still important to the client, then they do need to talk to your boss. Just direct them back there after the initial deflection. From there it really has to be your boss's issue to deal with.
1
+1 for mentioning reverse delegation. Yep, kick it back up to the guy who ducked it!
– Richard U
Feb 26 '16 at 21:40
suggest improvements |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
More or less as you've said it, but perhaps worded something like:
Sorry, but I don't have the authority to discuss time frames on future feature sets. I can raise it with my boss when I get back to the office, and he will contact you presently.
It's something that can't really be challenged (you don't have the authority), yet it defers it back to the boss. If you see the same client again and they ask if you'd discussed it with your boss, you can truthfully answer:
I passed on your request. I'm sorry, you will have to contact my boss to see where it's at.
This last bit may seem silly, but if you have passed it on, and it's still important to the client, then they do need to talk to your boss. Just direct them back there after the initial deflection. From there it really has to be your boss's issue to deal with.
1
+1 for mentioning reverse delegation. Yep, kick it back up to the guy who ducked it!
– Richard U
Feb 26 '16 at 21:40
suggest improvements |Â
up vote
8
down vote
More or less as you've said it, but perhaps worded something like:
Sorry, but I don't have the authority to discuss time frames on future feature sets. I can raise it with my boss when I get back to the office, and he will contact you presently.
It's something that can't really be challenged (you don't have the authority), yet it defers it back to the boss. If you see the same client again and they ask if you'd discussed it with your boss, you can truthfully answer:
I passed on your request. I'm sorry, you will have to contact my boss to see where it's at.
This last bit may seem silly, but if you have passed it on, and it's still important to the client, then they do need to talk to your boss. Just direct them back there after the initial deflection. From there it really has to be your boss's issue to deal with.
1
+1 for mentioning reverse delegation. Yep, kick it back up to the guy who ducked it!
– Richard U
Feb 26 '16 at 21:40
suggest improvements |Â
up vote
8
down vote
up vote
8
down vote
More or less as you've said it, but perhaps worded something like:
Sorry, but I don't have the authority to discuss time frames on future feature sets. I can raise it with my boss when I get back to the office, and he will contact you presently.
It's something that can't really be challenged (you don't have the authority), yet it defers it back to the boss. If you see the same client again and they ask if you'd discussed it with your boss, you can truthfully answer:
I passed on your request. I'm sorry, you will have to contact my boss to see where it's at.
This last bit may seem silly, but if you have passed it on, and it's still important to the client, then they do need to talk to your boss. Just direct them back there after the initial deflection. From there it really has to be your boss's issue to deal with.
More or less as you've said it, but perhaps worded something like:
Sorry, but I don't have the authority to discuss time frames on future feature sets. I can raise it with my boss when I get back to the office, and he will contact you presently.
It's something that can't really be challenged (you don't have the authority), yet it defers it back to the boss. If you see the same client again and they ask if you'd discussed it with your boss, you can truthfully answer:
I passed on your request. I'm sorry, you will have to contact my boss to see where it's at.
This last bit may seem silly, but if you have passed it on, and it's still important to the client, then they do need to talk to your boss. Just direct them back there after the initial deflection. From there it really has to be your boss's issue to deal with.
answered Feb 26 '16 at 6:30


Jane S♦
40.8k17125159
40.8k17125159
1
+1 for mentioning reverse delegation. Yep, kick it back up to the guy who ducked it!
– Richard U
Feb 26 '16 at 21:40
suggest improvements |Â
1
+1 for mentioning reverse delegation. Yep, kick it back up to the guy who ducked it!
– Richard U
Feb 26 '16 at 21:40
1
1
+1 for mentioning reverse delegation. Yep, kick it back up to the guy who ducked it!
– Richard U
Feb 26 '16 at 21:40
+1 for mentioning reverse delegation. Yep, kick it back up to the guy who ducked it!
– Richard U
Feb 26 '16 at 21:40
suggest improvements |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f62670%2fhow-to-handle-conversations-where-i-dont-have-authority-to-make-decisions%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Is it possible that your boss is trying to pass more responsibility to you and/or see how you perform in such tricky situations?
– Recct
Feb 26 '16 at 15:32