Navigating Difficult Conversations: A Guide for Academic Leaders
The Conversation You've Been Postponing
You know the one. Maybe it's with a senior faculty member whose behavior in team meetings has been demoralizing the group for two years. Maybe it's a trainee who isn't performing and doesn't seem to know it. Maybe it's a peer who took credit for work that wasn't theirs, and you said nothing at the time.
You've thought about it. You've rehearsed versions of it in your head while driving home. You've even had conversations with trusted colleagues about whether you should have the conversation at all.
And you haven't had it yet.
This is one of the most consistent patterns I see in academic leaders at every level — chairs, division chiefs, program directors, senior faculty. The technical parts of leadership are manageable. The interpersonal parts are where people get stuck.
Why Academic Leaders Avoid Difficult Conversations
The reasons are real, not just a failure of courage. In academic medicine, the stakes of interpersonal conflict are high in ways they aren't in most industries.
You may have a thirty-year career ahead of you in the same institution as the person you need to confront. The faculty member you need to address may have more seniority than you, or more political capital, or a national reputation that makes them feel untouchable. The trainee you need to counsel may be one of three residents who matched into a competitive program, and you need to maintain relationships with the residency director who sent them.
The academic hierarchy also creates confusion about authority. If you're a division chief who doesn't have formal HR authority, is it really your place to address a senior faculty member's behavior? If you're a program director, how hard can you push a struggling resident before it crosses into territory that requires formal documentation?
These aren't rationalizations. They're genuine complications. But they're also not reasons to avoid the conversation indefinitely. They're reasons to have it more carefully.
What Avoidance Actually Costs
Every difficult conversation you postpone has a cost, even when it feels like you're keeping the peace.
Other people are watching. Your team — residents, junior faculty, staff — see who gets confronted and who doesn't. When a senior physician routinely interrupts colleagues in meetings and nothing is said, the implicit message is that this behavior is acceptable, or that protecting the relationship with that person matters more than protecting everyone else in the room. That observation doesn't stay private. It shapes how people understand the norms of your department.
The person who needs the conversation is also harmed by your avoidance. If a junior faculty member's writing isn't ready for the journals they're targeting and no one tells them clearly, they spend years in a cycle of submission and rejection that a direct conversation could have interrupted. Protecting someone from uncomfortable feedback is rarely kind to them in the long run.
And the longer you wait, the harder the conversation becomes. A behavior that's been happening for six months is a pattern. A pattern that's been happening for three years is an identity. The earlier you address something, the more likely the other person is to hear it as information rather than indictment.
A Framework for Having the Conversation
There's no script that works for every situation, but there is a structure that holds up across most of the difficult conversations that academic leaders face.
Get clear on what you actually want to achieve. Before you walk into the room, know your goal. Are you trying to change specific behavior? Address a relationship rupture? Deliver news the other person isn't going to like? The goal shapes everything else — your tone, what you lead with, how you handle the response. If you don't know what you're trying to accomplish, you'll chase your tail once the conversation gets uncomfortable.
Separate observation from interpretation. This is the most common place things go wrong. There's a difference between "you've been dismissive of junior faculty in team meetings" (interpretation) and "in the last two M&M conferences, you've spoken over residents mid-sentence three times" (observation). The first invites a debate about your characterization. The second is harder to argue with.
Stick to what you've directly observed. If you're relying on secondhand accounts, say so: "Multiple people have come to me with the same concern" — and be prepared for the possibility that the account is incomplete or one-sided.
Say the hard thing directly. Academic culture rewards verbal agility. It also produces a lot of indirect communication where the actual message gets buried under qualification and hedging. If you need someone to change a specific behavior, say that. If you're telling someone they're not going to be promoted, don't leave them parsing your language afterward to figure out what you meant.
Directness is not the same as harshness. You can be clear and kind at the same time. But clarity has to come first.
Make space for their response. After you've said what you came to say, stop talking. Give the other person room to respond. They may need a moment. They may be surprised. They may have information you don't have.
The hardest part of a difficult conversation often isn't delivering the message — it's sitting with the discomfort of someone's reaction without rushing to fill the silence or walk back what you said. If you've been direct and fair, you don't need to apologize for the conversation.
Agree on what happens next. Every difficult conversation should end with clarity about next steps. If you're asking for a behavior change, be specific about what you'll need to see and when. If the conversation was about performance, agree on how you'll assess progress. If it was relational, name what you're hoping the relationship looks like going forward.
Conversations that end without a clear next step tend to get renegotiated in the other person's head until they mean something different than what you said.
When the Other Person Reacts Badly
Some difficult conversations go smoothly. The other person takes in the feedback, thanks you for raising it, and engages constructively. These happen.
Many don't. The person gets defensive. They shift to counterattack. They bring up unrelated grievances. They cry. They shut down.
None of these reactions mean you did something wrong. They often mean you said something true that the other person wasn't ready to hear.
When someone reacts with defensiveness or anger, don't escalate and don't capitulate. Name what you're observing: "I can see this is landing hard." Stay with the core message. And if the conversation breaks down completely, it's okay to pause: "I want to come back to this when we've both had a chance to think. Can we schedule time in the next week?"
You don't have to resolve everything in one conversation. You do have to make sure the conversation happens.
The Practice Is the Point
Difficult conversations don't get easier because you think about them more. They get easier because you have them.
Leaders who are effective at navigating conflict aren't people who find conflict comfortable. They're people who've learned that a well-handled difficult conversation almost always improves the situation, even when it's painful in the moment. That experience accumulates over time.
If you're preparing for a specific conversation and want to think through the approach, or if you're dealing with a pattern of avoidance that's affecting your effectiveness as a leader, individual coaching is a place to work through that in depth. Many of the conversations I have with leaders start exactly here.
The conversation you've been postponing probably needs to happen. The question is whether it's going to happen on your terms or in a crisis.
