Most feedback doesn’t work.
You tell someone what went wrong, they nod, maybe apologize, and then two weeks later you’re having the same conversation.
The problem isn’t that you’re being too soft or too harsh. It’s that you’re giving feedback on the problem instead of the pattern.
Problem vs. Pattern
When you give feedback on a problem, you’re addressing a single incident.
For example, “You missed the deadline on the report” or “That client presentation didn’t go well.”
The person hears it as an isolated one-time thing.
They’ll try harder next time or be more careful but their behavior doesn’t actually shift because they don’t see what they keep doing wrong.
When you give feedback on a pattern, you’re naming what keeps happening:
“You consistently underestimate how long things take” or “You’re pitching features instead of solving the client’s actual problem.”
Now they can’t dismiss it as a one-off. They have to look at their behavior differently and that’s when change happens.
The Framework
Here’s how to give feedback that lands:
“Here’s the pattern I’m seeing, here’s the impact it’s having, here’s what needs to change.”
What This Looks Like in Practice
Before:
“You were late to the client meeting this morning. You need to be on time.”
After:
“You’re consistently 5-10 minutes late to client meetings. The impact is that it signals to clients we don’t value their time, and it puts the team in an awkward position. What needs to change is building in buffer time so you’re there early, not just on time.”
See the difference?
The first version addresses one meeting. The second addresses the behavior that causes the problem repeatedly.
Before:
“The proposal you sent had several errors in it. You need to proofread more carefully.”
After:
“You’re sending work that has avoidable errors because you’re not building in review time before deadlines. This creates rework for the team and makes us look less credible to clients. What needs to change is finishing drafts a day early so you have time to review with fresh eyes.”
Before: “You talked over Sarah in that meeting. That wasn’t respectful.”
After: “When you disagree with someone, you jump in before they finish their point. People stop sharing ideas because they don’t feel heard. What needs to change is letting people complete their thought before you respond, even when you disagree.”
What Happens When You Use This
When you name the pattern, people see the larger issue.
They can’t argue with a pattern the way they argue with a single incident.
It’s harder to say “that was just a bad day” when you’re pointing out something that’s happened five times in three weeks.
And because you’re clear about the impact and what needs to change, they know exactly what success looks like.
The Bottom Line
Feedback works when it addresses patterns.
The next time you need to give feedback, ask yourself, is this a one-time mistake, or is this something I keep seeing?
If it’s a pattern, name it. Tell them the impact. Tell them what needs to change.
You’ll be surprised how much faster behavior shifts when people can actually see what they’re doing wrong.
