What to Say When the Feedback Did Not Land
DIFFICULT CONVERSATIONS
What to say when the feedback did not land.
You gave the feedback. The behavior continued. Now the next conversation needs more structure, not more frustration.
Most managers know when the first conversation did not work.
The issue shows up again. The same deadline slips. The same tone lands in the meeting. The same handoff gets missed. The manager feels the frustration building because they already said something.
That is usually where the mistake happens.
The manager either repeats the same feedback louder, softens the message because they feel awkward, or skips the follow-up because they do not want to seem like they are micromanaging.
None of those fix the pattern.
The second conversation has a different job.
The first conversation names the issue.
The second conversation names the pattern.
That shift matters. If the manager keeps treating a repeated issue like a first-time miss, the standard gets weaker every time.
The conversation needs to move from:
“Here is what happened.”
to
“This has now become a pattern we need to address differently.”
That does not require drama. It requires clarity.
MANAGER SCRIPT
Use this opening.
“We talked about this previously, and I am seeing the same issue show up again. I want to reset the expectation and be clear about what needs to change from here.”
That opening does three things. It references the previous conversation, names the repeat issue, and signals that the next step is not another casual reminder.
Do not start with frustration.
Frustration may be understandable. It is not the structure.
When managers start with frustration, the conversation often turns into tone, defense, or debate. The employee reacts to the emotion instead of the expectation.
Start with the pattern. Then move to the standard.
LANGUAGE SWAP
Instead of: “We have already talked about this. Why is it still happening?”
Try: “This is the second time we are addressing this, so I want to be clear about the expectation and the follow-up from here.”
The first version invites defensiveness. The second version creates a path.
The conversation needs four parts.
01
Name the repeat issue.
Be specific. Do not hide behind general words like attitude, ownership, or communication.
02
Reset the expectation.
Say what good looks like. The employee should not have to guess what changes after the meeting.
03
Ask for the barrier.
Give the employee a chance to name what is getting in the way without letting the conversation drift away from the standard.
04
Set the follow-up.
The meeting is not finished until the next check point is named.
A cleaner second-conversation script.
“We talked about this previously, and I am seeing the same issue show up again. I want to reset the expectation clearly.
The expectation is [name the standard]. What I am seeing is [name the behavior or result].
Before we talk about next steps, I want to understand what is getting in the way.
From here, I need [specific change] by [timeframe]. We will follow up on [date] to review whether the change is holding.”
Simple. Direct. Harder to dodge.
FREE SCRIPT PACK
Need the first sentence for the conversations managers avoid?
Get the free script pack and start with the five conversations that most often get delayed.
Get the Free Script PackWhen the pattern keeps repeating.
If the same issue keeps coming back after the reset conversation, the manager needs more than a script. They need a system.
That is where the next step matters: evidence, agreement, follow-up, and a clear decision point.
NEXT TOOL
The Accountability Conversation System
Built for the conversation that needs more than another reminder.
See the System