When feedback waits, it changes shape.
Leaders delay feedback for sensible reasons.
Sometimes the issue looks like a one-off. A deadline slips. The work isn’t up to the usual standard. You wait to see if it happens again.
Other times, it’s not the work. It’s the way someone behaves while doing it. The tone. The disrespect. The way other people stop contributing after they speak.
Both situations create the same leadership moment. You notice something, you hesitate, and you decide whether to address it now or later.
Later is tempting.
Performance feedback can be direct
Early in my consulting career, I was a new program manager on a major program. I travelled to London most Monday mornings and it had worked for months. One Monday, fog closed the airports and I couldn’t get into the city in time for a critical meeting.
My program director said one sentence: you should have travelled on Sunday.
No lecture. No debate. Just the standard I hadn’t considered. If the meeting mattered, my travel plan needed a buffer and a backup. After that, I never travelled on the day of an important event again.
That’s one reason performance feedback can move faster. It’s anchored to something visible. It points to a better decision next time.
Even then, leaders hesitate. They don’t want to pile on. They don’t want to be unfair based on one moment. They don’t want to overreact. So they let it slide and hope it self-corrects.
Behaviour feedback is where many leaders freeze
Behaviour is different.
It isn’t only about outcomes. It’s about what it’s like to work with someone. When behaviour is disrespectful or undermining, it affects the whole team. People pull back. Meetings get cautious. Someone has to carry the emotional cost of the tension, and it usually isn’t the person causing it.
And because behaviour feedback sits close to respect and power, leaders often hesitate even when the issue is obvious. They worry it’ll escalate. They worry about the reaction. They worry they’ll say it badly and make things worse.
So they wait. They manage around the person instead of addressing the behaviour.
The mistake I made as a new leader
When I became a program director, I had someone on my team who was openly disrespectful. He resented me being in the role and he didn’t hide it.
I didn’t address it quickly. Not because I didn’t see it, but because I didn’t know how to handle it.
Part of it was skill. I hadn’t built the muscle for a conversation like that. Part of it was the desire to be liked. I told myself it would settle on its own if I didn’t inflame it.
It didn’t settle. It spread.
Eventually I had to sit down with him and talk about specific incidents and their impact. Not labels. Not “attitude”. Specific moments. What happened, what it caused, and what needed to change.
I waited because I didn’t have the skill yet. Waiting didn’t make it easier.
The longer you wait, the more the conversation shifts
If you raise feedback early, it stays close to what happened. It’s about the event and what needs to be different next time.
If you wait, you’re no longer addressing an event. You’re addressing a pattern.
And while you’ve been waiting, you haven’t been neutral.
You’ve been noticing. You’ve been adjusting how you work with the person. You’ve been stepping in more, checking more, or avoiding certain situations because you don’t want a repeat of what happened. You may not call any of that feedback, but the person feels the change.
So when you finally speak, the conversation has more weight than it would have had weeks earlier. Now you’re not just saying, “Here’s what happened.” You’re also explaining why you’re frustrated, why you’ve lost confidence, or why you’ve changed how you work with them.
That’s when feedback starts to land as judgement, even when your intent is to protect the work and the team.
Leaders often say, “I didn’t want to overreact.”
Employees often say, “I wish you’d told me sooner.”
Both can be true. Waiting doesn’t keep things neutral. It increases the load when you finally speak.
If you’re avoiding a conversation, try this
You don’t need a script. You need a structure you can trust:
- Name the standard
- For performance: what does “good” look like here, in timing and quality?
- For behaviour: what does respectful disagreement look like on this team? What crosses the line? If you can’t name the standard, you’ll either avoid the conversation or drift into vague labels. Neither helps.
- Write three sentences before you speak
- What I observed. Facts you could point to.
- The impact. On the work or on other people.
- The expectation. What needs to happen next time.
If you can’t write those three sentences, don’t start the conversation yet. Do the thinking first.
- Keep it in the work
Try: “I want to talk about something that’s getting in the way of the work. Can I share what I’ve noticed?”
Then say your three sentences.
Then ask: “How do you see it?”
That gives the person room to respond without letting the standard drift.
A leadership choice
If you’re holding back feedback right now, you probably have a reason. You might be trying to be fair. You might be tired. You might be avoiding a reaction you don’t have capacity for.
Just don’t confuse delay with care.
Care is naming the issue while it’s still workable. Care is being specific enough that the other person can respond. Care is protecting the team from behaviour that makes work harder than it needs to be.
If something isn’t working, say it while it’s still about what happened.
Choose earlier.