Most leaders don't have a communication problem. They have a courage problem. Here's how to close the gap and get better at it over time.

Sarah had been managing Scott for three years, and for most of that time, their working relationship had been fine. Scott was reliable, knew the business inside and out, and delivered quality work. But over the past year, something had shifted.

It started small. Scott would respond to new ideas with immediate skepticism. He'd point out potential problems before exploring possibilities. In team meetings, his first instinct was often to explain why something wouldn't work rather than how it might. It wasn't malicious, but it was becoming a pattern.

"I know I should probably say something," Sarah told me during one of our coaching sessions. "But honestly, Michelle, I'm not sure if I'm overreacting. He's not doing anything terrible. He's just... negative. And I'm worried that if I bring it up, I'll sound like I'm nitpicking or trying to control his personality."

This is the challenge most leaders face with difficult conversations. It's rarely about egregious behavior that demands immediate action. It's about the slow accumulation of small things that, left unaddressed, begin to impact team dynamics and performance.

Why We Avoid the Conversation

Let's be honest about what's actually happening when we avoid a difficult conversation. Our brains are wired to treat interpersonal tension as a threat. Even when we know logically that a conversation needs to happen, our nervous system kicks in with all the reasons to wait: the timing isn't right, it might make things worse, maybe the problem will resolve itself.

There's also what I call the "perfect moment myth" - the idea that there will come a time when you're fully prepared, the other person is in exactly the right headspace, and the stakes aren't so high. That moment almost never comes. And waiting for it is just avoidance with better branding.

The Real Cost of Waiting

When I asked Sarah to reflect on what this pattern was costing her and the team, she initially shrugged it off. "It's not that bad," she said. But as we dug deeper, the list grew:

"I'm spending mental energy wondering what Scott will say when someone brings up a new idea. The team has gotten quieter in meetings. I can see people hesitating before they speak up. And honestly? I'm starting to dread our team brainstorming sessions because I know Scott will find the problems before we've even explored the possibilities."

The tipping point came during a routine team meeting. A newer team member, Jessica, suggested a small process improvement. Before she could fully explain her thinking, Scott jumped in with, "We tried something similar a few years ago. It created more problems than it solved." Jessica nodded and moved on, but Sarah noticed she didn't contribute another idea for the rest of the meeting.

After the meeting, Sarah mentioned to Scott that his response had been pretty quick. "Someone needs to keep us realistic," he replied. "She'll learn that not every idea is worth pursuing."

That's when Sarah realized the conversation could no longer wait.

Preparing for What Matters

The framework we developed for Sarah's conversation with Scott draws from what I've learned works across hundreds of similar situations:

Step 1: Separate observable behavior from your interpretation

Sarah wrote down what she'd actually witnessed: "Scott responds to new ideas by immediately identifying potential problems. He references past failures when people suggest changes. Team members have become less likely to share ideas after he responds."

This was different from her interpretation: "Scott is negative and doesn't support innovation." Facts invite problem-solving. Interpretations trigger defensiveness.

Step 2: Get clear on your intent

Before any difficult conversation, ask yourself: what outcome are you hoping for? Sarah realized she wanted to understand Scott's perspective and help him see the impact of his communication style. She wasn't trying to change his personality or eliminate his critical thinking - she valued that. She wanted to help him deliver his insights in a way that didn't shut down exploration.

Step 3: Lead with curiosity, not conclusions

Instead of telling Scott what he was doing wrong, Sarah prepared questions that would help her understand his perspective:

• "I've noticed you often identify potential problems when new ideas come up. Help me understand what you're thinking in those moments."

• "What's your sense of how the team responds when concerns are raised early in the brainstorming process?"

• "What would need to be different for you to feel comfortable letting ideas develop before pointing out potential issues?"

The Conversation (Realistic Version)

When Sarah sat down with Scott, she started by acknowledging his contributions. "Scott, I want to talk about something I've been noticing in our team meetings. First, I want you to know that I value your experience and your ability to spot potential problems. That's saved us from some real mistakes."

She then moved into her observations. "I've noticed that when new ideas come up, you often point out the challenges right away. I'm curious about what's driving that."

Scott's initial response was defensive. "So what are you getting at? I'm just trying to be realistic. Someone has to think about what could go wrong."

This is where many leaders give up or get pulled into an argument. Instead, Sarah stayed curious. "I can see that you're trying to protect the team from problems. That makes sense. I'm wondering if you've noticed how people respond when concerns are raised early in the idea-sharing process."

It took several more exchanges before Scott began to soften. "I guess... I mean, I don't want people to waste time on things that won't work. But I hadn't really thought about whether my timing was shutting people down."

The breakthrough came when Sarah shared the impact she'd observed. "When Jessica suggested that process change last week, and you immediately referenced the past failure, she didn't share another idea for the rest of the meeting. I don't think that was your intention, but that was the impact."

Scott was quiet for a moment. "I didn't realize that. I was just trying to give her context."

The Ongoing Work

The conversation didn't transform Scott overnight. Change rarely happens that way. But it opened a door to ongoing dialogue about communication and team dynamics.

Over the following months, Sarah and Scott developed a system. In brainstorming meetings, they agreed that the first phase would be for generating ideas without evaluation. Scott could ask clarifying questions, but would hold his concerns until the evaluation phase. Sarah also made sure to explicitly ask for Scott's critical analysis when it was time to vet ideas.

Several months later, Scott still isn't the most naturally optimistic person on the team. But he's become more aware of his impact. He'll catch himself starting to point out problems and instead ask, "Should I share my concerns now, or wait until we're in evaluation mode?" The team has noticed, and Jessica recently told Sarah, "I really appreciate how Scott asks questions now instead of just shooting things down."

Your Framework for Difficult Conversations

Getting yourself to have it:

1. Name what you're actually afraid of (be specific)
2. Calculate the cost of not having the conversation
3. Shrink the ask - commit to just opening the door, not resolving everything
4. Put it on the calendar before you lose your nerve

Having it well:

• Know your intent before you open your mouth
• Lead with curiosity, not conclusions
• Separate observable behavior from your interpretations
• Close with clarity about next steps

Getting better over time:

• Reflect on what worked and what didn't after each conversation
• Lower your threshold - address things within 48 hours when possible
• Find someone to debrief the challenging conversations with
• Remember: you get better by having them sooner and more often, not by avoiding them

The Leadership Reality

Here's what I know from working with leaders across industries: the ability to have difficult conversations isn't about being naturally confrontational or having perfect emotional intelligence. It's about recognizing that avoiding conflict doesn't protect relationships - it slowly hollows them out.

The conversation you're avoiding right now? It's probably not as hard as you think. And it's almost certainly more important than you're letting yourself believe.

The most effective leaders aren't the ones who never face conflict. They're the ones who've learned to walk toward it with curiosity, care, and the quiet confidence that comes from knowing they can handle whatever comes next.

How is your leadership style impacting your team's performance? Take our Peak Performance Assessment to gain insights on the kind of culture you're fostering.

Categories: Building Trust, Conflict Management, Emotional Intelligence, Leadership Skills, Workplace Communication

Are you interested in learning how to lead your business through positive change? Click here to schedule an appointment.