You gave the team lead role to Hannah. Marcus expected it, his team knows it, and he asked for this meeting before you announce it tomorrow.
An engineering manager with eight direct reports.
You are promoting Hannah Marsh to team lead for the payments squad. Marcus Okonkwo has been the senior engineer on that squad for three years and was told eighteen months ago he was on track. The decision is made. Marcus asked for a one-to-one before you tell the team tomorrow morning.
Tell him clearly, hear him out without reopening the decision, and leave with a credible plan for what happens to him — not a promise you cannot keep.
Marcus
Senior Engineer, your organisation
She opens guarded, and she is holding 4 things back — 0 near the surface, 2 that take real questioning, and 2 you will only get to if the conversation genuinely goes well. What they are, and what makes her say them, is the part you have to find. She is not scripted to volunteer any of it.
The objectives for this scenario, and the four axes every leadership call is graded on.
Was the decision and its reasoning stated plainly and early, or buried under context and hedging?
Did they answer the actual objection, acknowledge legitimate cost, and hold the line where it should be held — without either caving or dismissing?
Did they say what they did not know, and what was genuinely bad about this, rather than sell it? Nothing costs a leader more credibility than good news that turns out to be spin.
Did the room leave understanding the decision, knowing what happens next, and believing they were told the truth?
Understood, believed, and clear on what happens next — agreement not required.
They will do it and they do not buy it.
The message did not survive the delivery.
Spin was detected, or a question was dodged in a way the room noticed.
Delivering bad news to someone who had a reasonable expectation, without caving or condescending. 15 minutes, live voice, and a scored debrief you can replay. The first call is free.