What if I told you that you don't have to tailor your feedback to the person?

One of the most common things I hear from leaders is that you have to tailor your feedback to the individual. Some people want direct. Some want gentle. Some need context first. Some need data. People think that this is good leadership, reading the person and adjusting accordingly.

I get why that's appealing, because it sounds thoughtful and most of us want to be thoughtful. But in practice it trips a lot of leaders up. They end up spending so much energy trying to figure out how it will land best that they lose sight of what matters.

Here's what I've come to believe: there is a way of giving feedback that works for everyone. Not because it's a magic script, but because it's built on two things that are universally human: clarity and genuine curiosity.

The personality that matters most in a feedback conversation isn't theirs, it's yours.

Here's what I mean by that.

Three ways feedback conversations go wrong

Say you've got a Director on your team who has pushed back hard on Operations in the last two cross-functional planning sessions. You were in both meetings and witnessed that it got tense. Also a couple of your peers mentioned it to you after.

Here are three ways that feedback conversations usually go:

1. Too soft and unclear. You sand the edges off so much that they don't recognize this is a pattern, that it's a problem, or that it's theirs to own. "It would be worth building the relationship with Operations a bit. I try to grab coffee with Dana every quarter and it makes a difference when we disagree on something."

   
   

   They hear a suggestion and a tip about how you work. What they don't hear is that this has happened twice now, that it's theirs to solve, or that it's starting to shape how they're seen. Nothing changes, and a few months later you're frustrated that you had the conversation and it made no difference.

2. Too much telling. You're clear and direct, which feels like exactly the right thing to be. You name what you saw and you tell them what to do differently. "I want to talk about how you're working with the other functions. When Operations proposed running the pilot in their region, you pushed back on it right there in the meeting, in front of everyone. You need to take concerns like that to Dana before the session rather than raising them cold in the room."

   
   

   Nothing about that is unkind, and it's certainly not vague. But you did all the talking. You told them what to do without ever asking what was going on, and there is always something going on. The feedback happens to the person rather than with them, and now they're either quietly complying with a fix that doesn't address the real problem, or getting defensive.

3. Too late. You say nothing at all, and it comes out at the annual review. "I've been meaning to raise this for a while. There's a perception across the leadership team that you're difficult to work with. It came up after the planning session in the spring, and again after the pilot discussion in the summer. I should have said something at the time. When we talked about the VP role last month, that was the concern, and it's why we're holding off for now."

   
   

   By then it isn't one conversation, it's six months of accumulated evidence landing at once, and they're finding out in November about a decision that was made without them ever knowing it was in play. If someone is genuinely surprised by your feedback, that tells you something about how long you waited.

   
   

What these three have in common isn't tone. It's that the other person never really got to take part. In the first, they never understood there was a problem. In the second, you'd already decided what should happen. In the third, they found out once it had already cost them something.

So you don't need a different approach for every personality on your team. You need one approach that has both clarity and curiosity, because none of these has both. You also need to use it while there's still time for the person to do something with it.

The goal of a feedback conversation is to change something. Not to inform someone that they have a problem, and not to get it off your chest. And the thing that actually produces change is agreeing on the problem together and then working out what to do about it together. That sounds like a small distinction, but it makes a difference to the outcome.

So what does that actually look like?

What works

1. "Here's what I've observed."

Start with facts rather than interpretations. "In the last two planning sessions, Operations put forward a proposal and you pushed back on it right away in front of the group. In the pilot discussion, you cut in before Dana had finished" is an observation. "You're being territorial" is an interpretation. "You're difficult to work with" is a judgment.

Facts give the other person something concrete to respond to, and they signal that you're working from evidence rather than from a feeling.

2. "Here's where you stand."

This is where a lot of people soften, usually by naming the impact on the work instead of the impact on the person.

"Those sessions have been getting tense" is a fact about the meeting. It's true, and it lets everyone off the hook. What the person needs to hear is that this is a pattern and what it means for them.

Something closer to: "This is the second time this has happened. At this level, how you work across the business is a big part of the job, and right now this is getting in the way. It's starting to affect how people outside our team see you, and that will matter for where you go next."

That's a harder thing to say, and I'd encourage you to say it anyway. Caring about someone doesn't mean hedging, and the kindest thing you can do is make sure they understand this is serious while it's still fixable.

Then: "and this is workable."

The second half of this step matters just as much. Once you've named it, make clear it can be solved and that you haven't already decided how. "This is absolutely something we can sort out. Before I say anything else, I want to understand what's going on from your side." Clarity on its own lands as a verdict. Reassurance on its own is the soft version all over again, and you need both.

3. "What's your perspective on this?"

This is the step that tends to get skipped, because you don't know what the other person will say and a one-way conversation feels safer.

So you ask, and then you actually stop talking. "Help me understand what's happening for you in those sessions."

Here you might get: "Back in the spring, Operations changed the spec on the integration halfway through the build and didn't tell us. My team ate three weeks of rework. I've raised it with Dana privately three times since then and nothing changed. So now I say it in the room, because that's the only place anything sticks."

That's a completely different problem from the one you walked in with, and it's information you would never have gotten if you'd spent this part of the conversation talking. Notice too that the obvious fix, take it to Dana first, is the one thing they've already tried.

What you don't do next is drop the original point. Both things are true, and you say so: "I didn't know any of that, and I'm glad you told me. It also doesn't change the fact that the way it's coming out in the room isn't working for you."

4. "What do you think needs to change, and what do you need from me?"

Now you hand it to them. "So what are you going to do differently now, and what do you need from me to make that work?"

You might get: "I'll take it to Dana directly before the meeting instead of raising it cold in the room, and work on building my relationship with her. I don't really know much about her team or their pressures. I do need the spec change process fixed though, and I don't think I can get that done on my own. Will you raise it with her too?"

If the answer is thin, push once. "That's a start. What happens if it comes up again in the room?" You're not looking for a plan you could have written yourself. You're looking for evidence they've thought it through. And if they need time to think, that's fine. Ask them to sit with it and pick it up again tomorrow.

Telling someone exactly what to do sets them up to either fail quietly or disengage. Asking them genuinely builds their capacity to solve their own problems, which at this level is most of the point. This step is also where you signal that you expect more of them - not more effort, more ownership. You're handing them the thinking rather than the instructions, and in my experience most people rise to that.

Why this works regardless of personality

The steps keep you from lecturing, and they keep you from skipping the part that matters, which is the conversation itself.

You can ask "what's your perspective on this?" as a formality and move straight past the answer, or you can ask because you genuinely want to know. The person sitting across from you will feel the difference.

And that difference matters a lot, because a feedback conversation that feels like a verdict tends to create more disengagement than the original problem ever did. Change rarely happens when someone leaves the room feeling managed rather than heard.

Adapting it sideways and up

The same four steps hold when you're talking to a peer, or to your own boss. The thing that shifts is step two, and there's a simple rule that makes it work: impact has to land on a person, not on a process.

With someone on your team, the person it lands on is them, which is why the language is "here's where you stand." With a peer, it usually lands on you and on the work you share. With your manager, it lands on you, and that's the only version that's appropriate, because their performance isn't yours to assess. "From where I sit, here's what this is doing to my work" is something nobody can argue with.

Step four shifts in the same way. Downward, they own what happens next. Sideways, you both do. Upward, you own the follow-up, and you ask what you need from each other.

The formula isn't complicated. Be clear about where they stand, be curious about their experience, and figure out what comes next together.

Have feedback on feedback? I'd love to hear how you approach these conversations, what works, what doesn't and whether any of this lands differently than you’ve been doing.