Timeline for How to make sure I'm assertive enough in contact with subordinates?
Current License: CC BY-SA 4.0
26 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2019 at 21:12 | comment | added | aaaaa says reinstate Monica | @StianYttervik please post answers in the answer and use comments to ask improvements/clarification on the question | |
| Mar 9, 2019 at 21:11 | comment | added | aaaaa says reinstate Monica | please replace "colleague" with "subordinate", right now it might seem there are 3 people involved (you, subordinate, and colleague) | |
| Mar 8, 2019 at 17:37 | comment | added | JimmyJames | @StianYttervik "This is insubordination." Agreed. I think a lot of people don't realize that insubordination is always cause for dismissal (at least in the US.) It's very foolish behavior because it can invalidate most any claim you have for wrongful dismissal. It might be worth explaining this to the subordinate. | |
| Mar 8, 2019 at 17:17 | answer | added | ventsyv | timeline score: -1 | |
| Mar 8, 2019 at 13:08 | comment | added | Stian | This is insubordination. At best it can be constructed as a failed attempt at presenting the client with options, but what a mistake to do it like that. This calls for an immediate 4-eye chat after the meeting has concluded, the contents of which are roughly: "Totally unacceptable to jeopardize our client and supplier contact by presenting a view that we are unable to police ourselves as a team and unsure about what the terms of delivery are. We discuss those issues as a team and present the chosen solution with loyalty. Don't do that again." | |
| Mar 8, 2019 at 11:40 | comment | added | jean | Some guys think this kind of behavior makes them looks smarter than the rest of the team and don't realize is sabotages the team image. I was once on your skin (first time leading in a managerial role). My mistake was not firing the guy the second time he did it. Be sure to end this now, in the long run it in benefit the entire team and even your colleague can finally realize how important teamwork is. | |
| Mar 8, 2019 at 11:37 | comment | added | okolnost | I would just add that you may also decide to present more than one proposal and let the client choose, but that should be agreed before the meeting. | |
| Mar 8, 2019 at 10:59 | answer | added | UKMonkey | timeline score: 0 | |
| Mar 8, 2019 at 10:09 | comment | added | gidds | Could the subordinate's alternative proposal have been motivated by anything that happened during the meeting (e.g. a client's expressed concerns)? Or was it clearly something they had always planned to present? | |
| Mar 8, 2019 at 9:43 | answer | added | Robert Andrzejuk | timeline score: -2 | |
| Mar 8, 2019 at 6:49 | comment | added | Mast | It's all about expectations. Make sure you communicate your expectations to your subordinate or it will be everybody's and nobody's fault when things go south. | |
| Mar 8, 2019 at 1:26 | answer | added | Wayne Werner | timeline score: 4 | |
| Mar 7, 2019 at 21:45 | review | Close votes | |||
| Mar 10, 2019 at 2:55 | |||||
| Mar 7, 2019 at 21:28 | history | became hot network question | |||
| Mar 7, 2019 at 21:00 | history | tweeted | twitter.com/StackWorkplace/status/1103762382067822611 | ||
| Mar 7, 2019 at 19:39 | answer | added | Tim | timeline score: 11 | |
| Mar 7, 2019 at 18:39 | comment | added | joeqwerty | 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. | |
| Mar 7, 2019 at 18:11 | answer | added | OnoSendai | timeline score: 27 | |
| Mar 7, 2019 at 18:07 | history | edited | DarkCygnus♦ | CC BY-SA 4.0 |
deleted 30 characters in body; edited tags; edited title
|
| Mar 7, 2019 at 18:05 | answer | added | DarkCygnus♦ | timeline score: 95 | |
| Mar 7, 2019 at 17:49 | history | edited | user4214 | CC BY-SA 4.0 |
added 47 characters in body
|
| Mar 7, 2019 at 17:47 | comment | added | sf02 | 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 | |
| Mar 7, 2019 at 17:45 | comment | added | user4214 | @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. | |
| Mar 7, 2019 at 17:40 | review | First posts | |||
| Mar 7, 2019 at 18:29 | |||||
| Mar 7, 2019 at 17:38 | comment | added | sf02 | 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? | |
| Mar 7, 2019 at 17:35 | history | asked | user4214 | CC BY-SA 4.0 |