A manager I worked with postponed a conversation with a senior analyst for five weeks. He described it as a big conversation, which is why it kept sliding. When it finally happened it took eleven minutes. She had known something was wrong, had been waiting for him to say it, and was relieved when he did.
Difficult conversations are postponed because they are rehearsed as confrontations. The manager imagines an argument, loses it several times in his head, and decides to wait for a better moment. The better moment does not arrive. Meanwhile the behaviour continues, his irritation accumulates, and by the time he speaks the conversation carries five weeks of unspoken frustration into a first sentence that was never going to survive it.
The structure below is deliberately plain. It is meant to be used on a Tuesday afternoon by someone who has not been trained as a coach, not to be admired.
Preparation: one page, three items
Write it down, even if you never look at it in the room. Writing forces the precision that speech lets you avoid.
- The behaviour, with dates. Not “your attitude has been poor” but “in the last three team meetings you responded to Priya’s update with a comment about how things used to be done”. Observable, specific, recent.
- The impact. What it costs the work, stated without exaggeration: the team has stopped raising issues in the meeting, and two people now bring problems to you afterwards.
- What you want. Not “an improvement in behaviour” but “I want the meeting to be a place where people can give an update without being second-guessed. If you disagree with an update, raise it with me after the meeting.”
Add one more line for yourself: what you might be getting wrong. Sometimes the behaviour has a cause you have not seen, and a manager who has considered that possibility listens differently.
The opening: two sentences
Open with the purpose and the subject, in that order. “I want to talk about how the team meetings have been going. I have a concern about the last three, and I would rather say it directly than let it sit.”
That opening does three things: it names the subject, it signals that this is not a casual chat, and it gives the person a moment to prepare. Do not open with “how are you” and work up to it. People can hear the approach coming and spend the preamble managing their anxiety instead of listening.
Then stop. Let them respond before you build the case. Their first response often contains information you did not have.
Staying on the behaviour
The conversation derails at the point where behaviour becomes character. “You interrupted Priya” is a behaviour. “You are dismissive of women in the team” is a character judgment, and it will produce a defence of character rather than a change of behaviour.
| What you mean | What comes out | What they hear |
|---|---|---|
| You interrupted twice | You are disrespectful | You are a bad person |
| The report was late three times | You are unreliable | My job is at risk |
| The tone in the meeting was sharp | You have an attitude problem | You do not like me |
When they defend, and they will, return to the instance. “I am not making a judgment about you. I am talking about what happened in Tuesday’s meeting, when Priya was three sentences into her update.” Repeat the instance as often as needed without adding new accusations. One conversation should address one pattern.
A difficult conversation fails at the moment the behaviour becomes a character judgment, and that moment usually belongs to the manager, not the employee.
Closing with a commitment
End with something specific that both of you can check later. Not “let us see how it goes” but “so from next week you will raise disagreements with me after the meeting, and I will make sure the agenda has ten minutes at the end for it. We will look at it again on the 24th.”
Get their words, not only yours. “Does that work for you, and is there anything you need from me for it to work?” A commitment the person has stated themselves is far more likely to hold than one they have merely accepted.
Write it down and send a short note afterwards: what was discussed, what was agreed, when you will review. Two paragraphs. That is not bureaucracy; it is the difference between a conversation and a decision.
Most difficult conversations fail after the meeting, not in it. The manager feels relief, the subject is never mentioned again, and the behaviour either continues or changes without anyone noticing. Either outcome teaches the team that conversations here are performances.
Put the review date in the calendar before you leave the room. Fifteen minutes, same structure: what has changed, what has not, what happens next. If the behaviour has improved, say so plainly and specifically. Managers systematically under-report improvement, then wonder why people do not repeat it.
If nothing has changed, the next conversation is shorter and firmer and should state what the consequence will be. That is not a threat. It is the information the person needs in order to make a decision.
Use it this week
Choose the conversation you have postponed longest. Do the one-page preparation tonight: behaviour with dates, impact, what you want, and what you might be getting wrong. Book thirty minutes. Use the two-sentence opening, stay on the instance, and close with a commitment in their words.
Then diarise the review. If you want support while you run the first one, coaching is more useful than a course at this stage, because the difficulty is specific to your situation. If the problem is wider, a management development programme gives a group of managers the same structure and a shared language for it, which matters more than individual skill. The reason it is worth the discomfort is simple: people leave managers far more often than they leave jobs, and most of that damage accumulates in conversations that were never held.