The Conversation You Keep Avoiding

Maya knew exactly what she would say.

She’d had the conversation so many times she could have delivered it from memory. She’s had it in the car on the way home, in the shower on Tuesday mornings, lying awake at 2am with the particular clarity that arrives at 2am and dissolves by 7. She knew the specific moments she’d reference. She knew the impact she’d name. She knew how she’d open, how she’d stay calm, how she’d keep it about the work and not let it become about everything else it had slowly become about over two years.

She knew exactly what she would say.

She had never said it.

Her boss, the VP, was what her peers called a seagull. A term that required no explanation to anyone who had worked in an organization for more than eighteen months. He was not malicious. That would almost be easier. Just consistently, reliably present in the worst possible way: absent during the work, then descending without context at critical moments to drop opinions, redirect priorities, and undermine decisions already made. Then flying off again, apparently satisfied, leaving the team to clean up the mess and Maya to explain what had just happened.

He wasn’t a bad person. That was the part that made it harder for Maya to reconcile. He cared about the work. He was trying to be helpful in the way that people are trying to be helpful when they haven’t been told that what they’re doing isn’t, well, helpful. He had no idea what the landing looked like from below. Because nobody had told him. Because Maya hadn’t told him. Because every time she got close to the conversation, the calculus kicked in.

What if he gets defensive? What if it makes things worse? What if it follows her to her next review, her next project, her next opportunity? What if she’s wrong about how it’s landing? What if she’s right about how it’s landing and nothing changes anyway?

The what-ifs won. Every time. Reliably and completely.

And every time they won, something else happened. The team started hedging. Not dramatically, incrementally, in the way that slow damage works. It’s not committing fully to decisions they’d learned might get overridden without warning. It’s the team only half finishing because they knew they’d have to rework at the last minute anyway. It’s Maya stop bringing her best thinking forward, because the energy required to protect an idea from being redirected mid-execution wasn’t always worth the cost of losing it. She started spending more time managing around the dynamic than doing the work she’d been hired to do.

She complained about it. To peers, in the parking lot conversations that happen between work and life. To her partner at home, in the half-conversations that start over dinner and trail off because there’s nothing new to say. She had, on three separate occasions, updated her resume.

She had not said a word to the VP.

Two years in, she had started to forget what the job felt like before the managing around started. She couldn’t remember the last time she’d walked into his office with an idea she was genuinely excited about. She couldn’t remember the last time she’d felt fully present in a meeting rather than half-present and half-monitoring for the next descent.

She was still there. She just wasn’t all the way in anymore.

That’s what the avoidance cost looks like. Not in one moment, but in installments, slow burning. Small enough to absorb, large enough to compound, invisible enough that nobody including the VP knew it was happening.

Ask someone why they’re not having the conversation they need to have and the answers come quickly. They’ve been rehearsed too.

“It’s not the right time.”

It is never the right time. The project is always at a critical point. The relationship is always delicate. The quarterly review is always either just passed or just approaching. The right time is not a moment on the calendar. It’s a story the avoidance tells to stay comfortable, and it is extraordinarily convincing because it is always at least partially true. There is always a reason. The reasons are real. They are also, if you’re honest, never actually the reason.

“It probably isn’t as bad as I think.”

The gaslight we apply to ourselves. Said most often when the evidence is clearest and the conversation is scariest. When minimizing the problem is cheaper, in the short term, than addressing it. You don’t rehearse a conversation in the car for two years about something that probably isn’t that bad. The minimizing isn’t an honest assessment. It’s the avoidance finding new material.

“What if nothing changes?”

This one is different from the others. It isn’t a lie. It’s a fear. Specific, legitimate, and worth taking seriously rather than dismissing. The risk that you name the thing, make yourself vulnerable, absorb whatever defensiveness comes back, and the answer is that this is just how it is. That fear keeps more crucial conversations unspoken than any other single thing. And it deserves a real answer, not a reassurance.

We’ll come back to it.

Leadership development has produced an entire industry around the downward conversation. The performance discussion. The behavior feedback. The person who isn’t working out. There are models, scripts, frameworks, HR guidance, and whole chapters of books dedicated to saying hard things to the people who report to you.

Almost none of it addresses the conversation going the other direction.

This is not an accident. It’s a reflection of where the power sits, and power shapes what gets named and what gets managed around.

Feedback delivered downward carries some professional risk. Feedback delivered upward carries a different category of risk entirely. One that includes your performance evaluation, your visibility to senior leadership, your access to the opportunities that determine the trajectory of your career. The stakes of the upward conversation are not imagined. They are real. Any framework that doesn’t acknowledge that is a framework for a situation that doesn’t exist.

And yet. The cost of not having the conversation is also real. It compounds. It is paid in the currency of your energy, your engagement, your best thinking, and eventually your willingness to stay.

This is the part that makes the avoidance feel rational, and the part that makes it most costly.

The VP in Maya’s story was not performing malice. He was operating from a model of engaged leadership that felt, from his vantage point, like exactly what a good VP should do. He descended because he cared. He redirected because he thought he was adding value. He had no data, none, suggesting that the landings were doing damage, because the person closest to the damage had decided the risk of providing that data was too high.

So the behavior continued. Not because he chose to continue it. Because the information that would change it never arrived. The conversation Maya wasn’t having wasn’t just costing her. It was costing him the chance to understand something important about his own leadership. Both of them were losing something. Neither of them knew it.

Every week the thing goes unsaid, the gap between the current dynamic and the conversation required to change it widens. The resentment accumulates in the way interest accumulates. Compounding quietly and consistently until the balance is much larger than the original deposit. The relationship calcifies around the avoidance. The pattern solidifies. Having the conversation starts to feel not just risky but structurally impossible. Like trying to move something that has been load-bearing for too long to touch.

This is the cruel arithmetic of avoidance: the longer you wait, the more you need the conversation and the harder it is to have. The window doesn’t stay open indefinitely. It narrows. And one day you realize the window has closed. Not because of a dramatic moment, but because you updated your resume for the fourth time and this time actually sent it somewhere.

The Crucial Conversations framework, developed by Patterson, Grenny, McMillan, and Switzler, is built on one foundational insight: conversations fail not because of what gets said but because of what happens to safety before it gets said.

When people feel unsafe, they stop engaging with the content and start protecting themselves. They go silent like Maya, absorbing and managing around. Or they go aggressive, escalating in ways that confirm every fear about what happens when you name the thing. Either way, the actual issue disappears into the dynamic and nothing changes.

Everything in what follows is oriented toward keeping safety intact long enough for the real conversation to happen.

The model calls this Start with Heart, and it’s the step most people skip because they’re so focused on what they’re going to say that they never examine why they’re going to say it. The what is the easier question. The why is the one that determines whether the conversation produces something or just produces a reaction.

Two questions. Answer them honestly, before anything else.

What do I actually want from this?

Not what you want to say. Not what you want the other person to understand. What outcome are you genuinely hoping for? A specific behavior change? A shared understanding of how the dynamic is landing? A different working arrangement? Clarity on whether this relationship can function in a way that works for both of you?

The answer to this question shapes everything about how you walk into the room. Someone who wants to be heard walks in differently than someone who wants the behavior to stop. Someone who wants to understand what the VP is trying to accomplish walks in differently than someone who wants to deliver a verdict.

Clarity on what you want is not a small thing. It is the difference between a conversation and a confrontation.

What do I want for this relationship?

This question matters especially in the upward conversation, where the power dynamic can turn the conversation into something adversarial before anyone intends it to be.

Do you want this working relationship to function well? Do you want to find a way to operate together that works for both of you?

If the answer is yes, then the goal isn’t to win. It isn’t to be right. It isn’t to have your experience validated. It’s to build something that works. Holding that goal in your body before you walk in changes the conversation in ways that no technique can replicate.

If the answer is no, you’re in a different situation that requires a different kind of honesty.

The VP’s instinct when Maya names this will be defensiveness. Not because he’s a bad person, because being told that your leadership behavior is landing badly is uncomfortable for everyone. Discomfort without safety produces self-protection rather than curiosity. His first move, internal and probably invisible, will be to construct a threat. Your job, before you say the thing you came to say, is to dismantle the threat before it finishes forming.

Two tools for opening the room.

Contrasting: Name what you’re not saying before you say what you are.

“I’m not raising this because I don’t value your involvement in the team’s work. I do. I’m raising it because I think there’s a way for us to work together that gets better outcomes for both of us, and I want to find it.”

That sentence does something important: it removes the interpretation the other person’s defensiveness will otherwise provide. Left to construct their own frame, people hear the beginning of a difficult conversation as an attack. Contrasting gives them a different frame before the attack they were preparing for arrives, and a different frame produces a different response.

Shared purpose: Connect the conversation to something you both care about before you name the problem.

“I want to talk about something because I think it’s affecting the team’s ability to deliver, and I know that matters to both of us.”

Us. That word is doing work again, the same way it did in the feedback article. It places the conversation in a shared stake rather than an individual grievance. The VP isn’t being called into a complaint. He’s being invited into a conversation about something that costs both of them. That framing doesn’t guarantee a good conversation. It makes one possible.

This is where the Ladder of Inference and the SBI method do their work inside the crucial conversation. Stay on the bottom rung. Describe what you’ve observed. Do not lead with what you’ve concluded.

Not: “You don’t trust me to lead my team.”
But: “When decisions we’ve made get redirected at the last minute without context, the team loses confidence in their work and I lose the ability to hold them accountable to it.”

Not: “You micromanage.”
But: “When you come directly into the team’s work without looping me in first, it creates confusion about where decisions get made. And I think it costs us both in ways that are worth talking about.”

The behavior is observable. The verdict is a conclusion arrived at after several rungs of inference. Name the behavior. Connect it to the impact. Frame it around the shared goal. Ask a question. “I wanted to share what I’m experiencing, and I’d want to understand what you’ve been trying to accomplish in those moments. I think there might be a gap between the intent and the impact.” Then (and this is the part most people forget in the relief of having finally said the thing) stop talking.

Then listen. Actually listen. Not to confirm what you already think. To find out what’s actually there. The answer might matter in ways you haven’t anticipated, and the conversation only goes somewhere useful if both people are in it.

Before you have this conversation. Before you finalize the opening, before you rehearse the SBI, before you book the thirty minutes. Sit with this question privately and honestly.

If I have this conversation and the VP’s behavior doesn’t change, what then?

Not as a catastrophe. Not as a threat you’re planning to deliver. As a genuine reckoning with your own situation and your own options. Because the answer to this question. the real answer, changes what you bring into the room.

Someone who has honestly answered it walks in differently. They’re clearer. Less desperate for a particular outcome. More able to have the conversation as a genuine exchange rather than a plea, because they’re not dependent on a specific response to be okay. They can stay curious. They can listen to the VP’s perspective without needing it to immediately validate theirs. They can hold the conversation open longer, which is when conversations actually go somewhere.

Here is what most people discover when they sit with the question honestly away from the avoidance and the 2am calculus: they have more options than the avoidance has been telling them. Options they haven’t fully examined because examining them would make the current situation feel less like a trap and more like a choice. A choice implies responsibility for what happens next.

You might discover you’re willing to stay and keep working on the dynamic if the conversation opens something. You might discover there are structural changes, a different working agreement or a different cadence of involvement, that would change enough to be workable. You might discover that if nothing changes, you will eventually leave. Knowing that, honestly, makes you less afraid of the conversation because the worst case is something you’ve already decided you can navigate.

The fear of the answer keeps the question unasked. Answering it, even privately, even imperfectly, changes the conversation before it starts. It moves you from someone avoiding a conversation they feel powerless in to someone with a choice and responsibility in having a conversation. That shift is not small. It is, in many ways, the whole thing.

Here’s what it could look like when Maya decides to stop rehearsing.

She doesn’t ambush him. She asks for time, “I’d like thirty minutes to talk about how we’re working together. There’s something I want to raise and I’d rather do it properly than let it sit.” He says yes, slightly wary. Fine. Wariness is appropriate. She’d be wary too.

She starts with contrasting. She names the shared goal: the team’s ability to deliver, the outcomes they both care about. She describes three specific moments: situations, behaviors, impacts. No verdict. No character assessment. Just what happened, and what it cost.

He is defensive for about four minutes. She expected this. She doesn’t fill the silence with reassurance or walk the feedback back to make the room more comfortable. She lets him sit with it.

Then something shifts. He didn’t know the last-minute redirects were landing the way they were. He thought he was adding context. He wasn’t aware the team had started hedging. He’d noticed less initiative than he expected but had attributed it to something else. He asks a question. A real one. She answers it honestly.

They don’t solve everything in thirty minutes. They don’t arrive at a perfect new operating model or a transformed relationship. What they arrive at is a shared understanding that something has been happening that neither of them had fully accepted, and a tentative agreement to work on it differently.

Maya walks out of the room having done the thing she’d been telling herself for two years she couldn’t do. She discovers something the parking lot rehearsals never could have taught her: the conversation was survivable. It required much more courage than the rehearsals implied. But more useful than all of them combined. The VP didn’t become a different person. But something that had been calcifying started, slowly, to move.

The seagull didn’t disappear. But he called before he landed.

One question to ask: What has the avoidance actually cost you so far? Not what it might cost you to have the conversation, but what it has already cost you? Time, energy, your best thinking, your willingness to be fully present. Add it up honestly. The avoidance has never been free. It has just been billing you in small amounts on a schedule you stopped checking.

One behavior to stop: Stop mistaking the rehearsal for the conversation. Most people have had the crucial conversation many times. They’ve played it out in the car, in the shower, and at 2am with the particular clarity that evaporates by morning. The rehearsal feels like progress. It isn’t. It’s the avoidance wearing productive clothing. The conversation only exists when the other person is in the room.

One action this week: Answer the underneath question before anything else. If I have this conversation and nothing changes, what then? Write the answer down. Not as a plan, as a private reckoning. Then answer the first question: what do I actually want from this conversation? Write that down too. See if the conversation you’ve been avoiding feels as impossible as it did before you started. It probably doesn’t. The impossibility was never the conversation. It was the unanswered question underneath it.

There is a version of your career in which you have the conversations you need to have, with the people who need to hear them, before the silence becomes the relationship.

It doesn’t mean every conversation goes well. It doesn’t mean every VP becomes coachable, every dynamic becomes workable, every avoided thing becomes resolved. Some conversations don’t change the situation. They change you. They provide you clarity about what you will and won’t absorb, and they provide you knowledge that you said the thing rather than spending years wondering what would have happened if you had.

That knowledge is worth something. More than the resume updates. More than the parking lot rehearsals. More than the managed-around version of a job you were otherwise doing well in.

The conversation you keep avoiding is not going away. The situation it addresses is getting more expensive every week you don’t have it. The person who needs to hear it might, with that information, become a better leader than they currently are.

You know what you would say.

The only thing left is to say it to the right person.

If this landed, share it with someone who has been rehearsing a conversation it’s time to actually have.

Share