The Cost of Waiting: Addressing Difficult Conversations Before They Escalate

Why waiting makes the conversation harder

Jay Bregman, founder and CEO of Andel, describes a familiar leadership challenge: the most difficult conversations are often those that should have happened weeks or months earlier.

For founders and CEOs, postponement can feel reasonable. There is a launch to finish, a customer to retain, or a colleague already under pressure. You may hope the issue will resolve itself—or worry that raising it will damage an important relationship.

But silence leaves room for conflicting interpretations. You may believe you are giving someone time to improve. They may believe their approach is acceptable. Meanwhile, frustration accumulates, teammates compensate, and a specific problem becomes a broader judgment about someone’s character.

The goal is not to confront people faster. It is to address meaningful concerns before resentment replaces curiosity.

Recognize when preparation has become avoidance

A short pause can help you gather facts, regulate your emotions, or choose a private setting. Repeated postponement without a concrete reason is different.

Ask yourself:

• Have I noticed the same concern more than once without discussing it?
• Am I venting to others instead of speaking with the person involved?
• Am I quietly taking work back or excluding someone from decisions?
• Have I decided they “should know” what I have never clearly explained?

If these patterns sound familiar, identify the conversation you are avoiding and schedule it. Give enough context for the other person to prepare rather than sending an ominous, unexplained invitation.

For example: “I’d like to discuss the recent handoff delays, understand what’s getting in the way, and agree on how we handle the next release.”

Separate the current issue from accumulated frustration

An overdue conversation should not become a surprise inventory of every disappointment.

Before meeting, write down four things:

1. The observable issue: What happened, and when?
2. The impact: What did it affect—delivery, customers, workload, or decision-making?
3. The expectation: What standard was communicated? What remained unclear?
4. The desired change: What would a workable improvement look like?

Choose a few relevant examples you can accurately describe. Avoid labels such as “uncommitted” or “not leadership material.” Those conclusions are harder to examine than specific behavior.

Also check your contribution. Did priorities change without notice? Did you assign responsibility without authority? Did you repeatedly rescue the work instead of explaining the gap? Accountability becomes more credible when it includes your own decisions.

Acknowledge the delay without weakening the message

If you waited too long, say so briefly. This is not an invitation to abandon the concern; it is a way to make the conversation fairer.

A possible opening is:

“I should have raised this sooner. In our last two planning cycles, the delivery risks surfaced after we had committed dates to customers. That left the team making last-minute changes. I want to understand what happened and agree on how risks get raised earlier.”

This opening acknowledges your delay, identifies the issue, and invites the other person’s perspective.

Then listen. Ask what they understood the expectation to be, what constraints they faced, and what you may be missing. Resist preparing your rebuttal while they speak. New information may change your assessment, even when the need for change remains.

Turn the discussion into an explicit agreement

A productive conversation needs more than mutual relief that the subject is finally open.

Agree on:

• The change: What will happen differently?
• The owner: Who is responsible for each action?
• The support: What resources, authority, or clarification are needed?
• The timing: When does the change begin, and when will you review it?
• The evidence: How will you both recognize progress?

For example, replace “communicate earlier” with an agreement to flag delivery risks in the shared project tracker when identified, including likely impact and a proposed response.

Summarize the agreement in writing and invite corrections. Where formal performance consequences are involved, follow applicable policies and get appropriate HR or legal guidance. A delayed informal conversation should not disguise a disciplinary decision already made.

Build a habit that prevents the next backlog

Set aside a few minutes each week to ask: “What am I tolerating, assuming, or avoiding that needs a direct conversation?” Use regular one-on-ones to discuss emerging concerns, not just project updates.

Not every irritation needs intervention. Look for meaningful impact, recurring patterns, or unclear expectations. Serious safety concerns, harassment, discrimination, or misconduct require prompt action through appropriate channels—not a wait-and-see approach.

You cannot undo weeks of silence in one meeting. You can stop extending the silence, establish a fair expectation, and follow through consistently.

Explore Jessica Hill Holm’s workbook library for structured reflection, and, if you want personal support preparing for an overdue conversation, consider a coaching call.