They Heard You. They Just Didn't Change.

It was a Wednesday one-to-one.

 

You'd rescheduled it twice already. You had something to say, something real, something that needed to be said and you'd been thinking about how to say it for two weeks.

So you said it. Sort of.

You opened with what was going well. You framed the issue carefully. You softened the edges, added a qualifier, sandwiched the point between two pieces of genuine praise.

They nodded. Said they appreciated the feedback. Left the room.

 

Three weeks later — nothing had changed.

The feedback wasn't wrong. The architecture was.

Here is what most of us were never taught about giving feedback:

 

"Delivery is not receipt. Being heard is not the same as being understood. And being understood is not the same as being moved to change."

 

Most feedback fails not because the manager lacks courage, care, or clarity.

It fails because the structure of the feedback, the order, the framing, the language makes it almost impossible for the other person to receive it as useful rather than as a verdict.

 

Verdict feedback triggers defence. Invitation feedback triggers growth.

The difference between the two is not how much you care. It's how you build the sentence.

The Belief Worth Examining

Most experienced Leaders believe that once they've said something, the person knows. The conversation happened. The message was delivered. The rest is on them.

That belief is understandable. And it is costing your team more than you realize.

Because feedback is not a transmission. It is a construction, built in real time between two people, shaped by relationship, timing, language, and the emotional state of the person receiving it.

 

You can deliver a perfectly accurate piece of feedback in a way that makes it completely unreceivable. And you can deliver an uncomfortable truth in a way that makes the other person lean forward and say: tell me more. The difference is architecture.

 

5 Feedback Frameworks That Actually Land

Each of these is a structure — not a principle. You can use them before your next one-to-one ends.

1.   The Future Frame

Language: "I want to talk about something because I think it's going to matter a lot for where you're heading. Not to revisit what happened — to make sure it doesn't get in the way of what's next."

 

This frames feedback as a growth investment, not a performance review. It signals that you're looking forward, not adjudicating the past. The moment someone hears 'where you're heading' their defensive posture softens, because you've just told them this conversation is on their side.

This is #SeekGrowth in action: positioning the feedback as part of someone's trajectory, not a judgement of their current position.

 

2.     The Specific Moment

Language: "In the Tuesday stakeholder call, when [specific thing happened], I noticed [specific observable behavior]. I want to understand what was going on for you in that moment."

 

Vague feedback — 'you sometimes come across as dismissive in meetings' — is impossible to act on because it describes a character trait, not a behavior. Specific Moment feedback describes an observable event. The person can see it. They can work with it. They can change it.

The question at the end — 'what was going on for you' — does something critical: it opens a conversation rather than closing one. You learn something. They feel heard. The feedback lands in dialogue, not decree.

 

3.     The Impact Gap

Language: "The intention I think you had was [X]. The impact it had on the team was [Y]. I don't think those two things match — and I want to help you close that gap."

 

Most behavioral issues aren't caused by bad intent, they're caused by a gap between what someone thinks they're communicating and what the room is actually receiving. The Impact Gap framework names that gap without assigning blame. It separates the person from the problem.

When someone hears that their intention was seen and respected even as the impact is being addressed, they stop defending and start problem-solving. That shift is everything.

 

4.    The Growth Question

Language: "If you could go back to that moment knowing what you know now — what would you do differently?" Then stop. Wait. Let them answer first.

 

The most powerful feedback conversations are not the ones where the manager does the most talking. They're the ones where the other person arrives at the insight themselves. The Growth Question creates that moment.

When someone names their own area for growth, in their own words, they own it. They are far more likely to act on a conclusion they reached than one that was handed to them. Your job in this framework is to ask the question and then be quiet.

 

5.     The Commitment Close

Language: "Before we finish — what's one thing you're going to do differently based on our conversation today? And when should I check in with you on it?"

 

Feedback without a next step is a conversation. Feedback with a next step is a commitment. The Commitment Close transforms the discussion into a shared accountability moment without pressure, without surveillance, with genuine partnership.

It also tells you something important: if the person can't name one thing they'll do differently, the feedback hasn't landed yet. That's not failure, it's information. And you can use it to go one level deeper before the conversation ends.

 

The Thing You Cannot Un-Know

Here's the insight that changes this permanently: Feedback is not about the past. It never was.

When you give feedback well, with the right architecture, the right framing, the right question, you are not reviewing what happened. You are co-authoring what happens next.

 

You are not a judge. You are a growth partner.

 

And once you understand that, you cannot give vague, sandwiched, verdict-shaped feedback again without knowing exactly what you're withholding from the person in front of you.

 

The kindest thing you can do for someone's growth is give them feedback they can actually use. Vague feedback is not kindness. It's avoidance dressed up as consideration.

 

Your Turn ⚡

Think about the person on your team whose performance has been quietly bothering you for longer than you'd like to admit.

You've probably told yourself you've addressed it. But have you given them feedback or have you given them a version of feedback that was safe enough for you to deliver?

Drop your answer in the comments. Or just sit with the question.

 

Both are a form of growth. ⚡

 

Seeking growth is a choice you make every week.

The Leap Lab is where that choice lives.

⚡ Subscribe — and invest in your own growth this week.

 

🌍 Share — because someone on your team is waiting for you to have this conversation better.

 

Leap First. Learn Always. ⚡