In our 2026 Real-Time Business Conversation Index, one respondent shared this insight:
“Colleagues have difficulty with tough conversations. I often see my colleagues take things too personally rather than focus on the facts and possible outcomes. As professionals and senior leaders, we need to lead by example and ensure we take an objective approach to problem solving and addressing issues.”
Difficult conversations arise for everyone. In this series, I’m sharing insights about these conversations and offering ideas for improving them. Your input and experience are always appreciated. We welcome your comments and feedback.
Most of us have been here at least once during our careers:
We’re sitting around a table at a team meeting. The meeting is focused on the delay of an important project because of someone’s mistake. The voice in our head starts to speak up loudly, “It wasn’t me”, “I didn’t make that mistake”, “Who is it that made that dumb mistake?” or “Gosh, I hope it wasn’t me!”
While none of us want to be the cause of a major error, our immediate focus on fault and blame continues to put the project at risk. Why? Because the ensuing conversation becomes personal. Everyone’s focus is on protecting themselves instead of on finding solutions and moving forward.
When a meeting starts to revolve around “Who missed this?” or “Why didn’t you catch this?”, the conversation is hijacked by defensiveness. People focus on explaining, justifying or deflecting rather than brainstorming solutions.
On the other hand, when accountability is completely ignored, perhaps with a “We’ll just fix it and move on”, the immediate tension vanishes, but can result in the issue arising again.
The question, and the challenge, becomes how to make these conversations truly productive, while ensuring that the events and reasons for the problem are fully understood and avoidable in the future.
Here’s how to create a mindset shift:
- Don’t avoid accountability. Delay it long enough to understand what actually happened. When you assign blame prior to understanding what actually happened, you’re guessing. And when you guess, you rarely come up with the best fix for a problem.
- Start the conversation with facts. Perhaps say: “Let’s focus on what happened here and how we can fix it quickly.” Everyone hears that the goal of the meeting is to reach a resolution, not to assign blame.
- Reconstruct the timeline with specifics. For example: “What was our initial plan?”, “What happened next?”, “Where did things shift?” This builds clarity for everyone and keeps the discussion logical and progressive.
- Look for gaps in the process. As everyone agrees on the timeline, the specific issue often becomes obvious. This could be something like, “Looks like the handoff between X and Y wasn’t clearly defined.” Or “We didn’t have a checkpoint before this stage.” Everyone is now involved in solving the right problem.
- Establish accountability going forward, not backward. Ask the questions “Who now owns this step?” and “What needs to be in place so this doesn’t happen again?” This does not assign blame. It gives you and your team ownership and control over eliminating the problem in the future.
- Finally, be explicit about the agreed-upon action. “Let’s add a checkpoint here.” and “We’ll clarify ownership before kickoff each time.” The issue now has a resolution that extends beyond the moment.
Projects no longer get stalled because of personal reactions. They get stronger and immediately back on track because you’ve established both clarity and accountability.
Try this this week:
When a project is put at risk, don’t focus on the “who”. Start by gathering everyone together to review the agreed-upon process and timeline. This keeps the team engaged without igniting defensiveness. The review will uncover an obvious gap, resulting in a solution.
