Most managers give feedback that is too vague to act on, too delayed to be relevant or too focused on character rather than behaviour. Most managers also do not actively seek feedback on their own performance — which means they are missing one of the most valuable sources of information available to them. This guide covers both sides of the feedback loop: how to give it well and how to receive it in a way that actually makes you better.
Why feedback fails — and what to do differently
Feedback fails most often for one of three reasons: it is too general to be actionable (“you need to be more proactive”), it arrives too late to be connected to what actually happened (“in your review last year I mentioned…”), or it is framed as a judgement about the person rather than an observation about a specific behaviour (“you’re not a team player”).
The common thread across all three failures is that the feedback is not useful enough to act on. The person receiving it does not know what specifically they did, why it mattered or what to do differently. Effective feedback is none of those things: it is specific, timely and behavioural. It describes what happened, what its impact was and what you would like to see instead — in enough detail that the person can actually change something.
Giving feedback Prepare before the conversation
Feedback conversations that are not prepared tend to be vague, emotional or both. Preparation does not mean scripting every word — it means being clear on three things before you start: what specifically happened, what its impact was and what you want the outcome of this conversation to be.
Gathering concrete examples is the most important part of this. “The deliverable for the Q2 campaign was three days late, which meant the design team had to compress their timeline and work over the weekend” is a basis for a productive conversation. “You’re always missing deadlines” is not — it is an accusation that triggers defensiveness rather than reflection.
Before any feedback conversation, write down: the specific situation (when and where), the specific behaviour you observed, and the concrete impact it had. If you cannot be specific on all three, you do not yet have enough to have a useful conversation. Gather more examples first, or wait until you do.
Giving feedback Focus on behaviour, not character
The distinction between behaviour and character is the single most important thing to get right in feedback delivery. Behaviour describes what someone did in a specific situation. Character describes what kind of person they are. Feedback about behaviour can be heard and acted on. Feedback about character triggers defensiveness and shuts down the conversation.
Compare: “You’re irresponsible” versus “I noticed the report went out with several inaccuracies that required correction before it could be shared with the client.” The second version describes what happened without making a judgement about intent or identity. It is both more accurate and more useful.
The SBI model — Situation, Behaviour, Impact — is the most reliable structure for keeping feedback behavioural. Describe the situation (when, where), the specific observable behaviour (what they did or did not do), and the concrete impact (what happened as a result). This structure keeps you out of interpretation and assumption and in the territory of observable fact.
Without SBI: “You’re not a team player — you never give people space to contribute.”
With SBI: “In this morning’s team meeting [situation], I noticed you spoke over two colleagues before they finished their point [behaviour]. It meant those ideas didn’t get heard, and I could see others pull back from contributing [impact].”
Giving feedback Deliver it promptly and specifically
The longer you wait to give feedback, the less connected the person can be to what you are describing and the harder it becomes to change. Feedback about something that happened six months ago cannot change six months ago — it can only create a vague unease about what else might be being quietly accumulated. Feedback about something that happened this week can change what happens next week.
The same principle applies to positive feedback. Praising someone in their annual review for something they did in March is significantly less powerful than acknowledging it on the day. “That was a really well-structured presentation — the way you used the data on slide five made the market trends immediately clear for people who were new to the topic” is specific enough to be memorable and timely enough to reinforce the behaviour you want to see more of.
Aim to deliver feedback within 24 to 48 hours of the event where possible. If a conversation needs to happen in private and the right moment does not exist immediately, schedule it for the next day rather than letting it sit. The habit of addressing things promptly prevents the accumulation of small issues into a much harder performance conversation down the line.
Giving and receiving feedback is Week 9 of the LeadWise Emerging Leaders Program — with practical exercises you apply directly with your real team, including feedback conversations you plan, have and reflect on.
Explore the program — €299Receiving feedback Actively seek it — do not wait for it
Most managers wait for feedback to come to them. In practice, most team members will not voluntarily give their manager critical feedback unless they are explicitly invited to and genuinely believe it is safe to do so. Which means that if you are not actively creating those conditions, you are likely receiving a systematically incomplete picture of how you are actually doing.
Actively soliciting feedback — asking specific questions after meetings, projects or significant interactions — signals that you genuinely want to know, not just that you are performing openness. It also gives people permission to say things they would otherwise hold back.
After leading a significant meeting or project, ask two questions: “What’s one thing I did that was useful or that you’d like to see more of?” and “What’s one thing I could have done differently?” The specificity of the ask makes it easier for people to respond honestly than a general “any feedback for me?” which is easy to deflect with “no, it was great.”
Receiving feedback Listen without defending
Receiving feedback — especially critical feedback — triggers a natural defensive response. The instinct is to explain, to provide context, to correct the record. Acting on that instinct in the moment is almost always counterproductive. It signals to the person giving feedback that they were wrong to raise it, which teaches them not to raise things in future.
The more productive response is to listen to the end, reflect back what you heard to confirm you understood it correctly, and then thank the person for raising it — genuinely, not performatively. You can ask clarifying questions to better understand. You can take time to think about it before responding with your perspective. What you should not do is respond defensively in the moment, even if you disagree with what you are hearing.
A team member says: “I feel like I don’t get enough direct guidance from you on my tasks, and I end up spending a lot of time trying to figure things out on my own.”
Defensive response: “I have so many other things to manage — I can’t be available for everything.”
Constructive response: “Thank you for telling me that. So what you’re saying is that you’d find it helpful to have more explicit guidance or clearer check-in points on tasks — is that right? Can you give me an example of a recent task where you felt this most strongly? I want to understand this better.”
When you receive feedback that you disagree with or that provokes a strong reaction, give yourself permission to say: “I appreciate you raising this — I want to think about it properly before I respond.” Then follow up within a day or two with your considered response. This shows that you took it seriously, which is far more trust-building than an immediate but defensive reply.
Closing the loop: act visibly on what you hear
The feedback culture in a team is shaped almost entirely by what happens after feedback is given. If people observe that nothing changes after they raise something — or worse, that raising it made things awkward — they stop doing it. If they see that their input is taken seriously and produces visible change, they contribute more honestly and more frequently.
This applies both to feedback you give your team and to feedback you receive. When you act on feedback someone gave you — and name it explicitly: “After our conversation last week, I’ve been trying to be more specific in how I brief tasks” — you demonstrate that the feedback loop is real, not performative. That demonstration changes the culture of the team more than any amount of talking about psychological safety or open communication ever will.
The bottom line
Feedback done well is one of the highest-leverage activities in management. It accelerates development, builds trust and catches problems early when they are still manageable. Feedback done badly — vague, late, personal or one-directional — erodes exactly the same things.
The good news is that the skills are straightforward and improve rapidly with practice. Be specific. Be timely. Focus on behaviour. Seek feedback on yourself. Listen without defending. And close the loop by acting visibly on what you hear. None of these are complex in concept. They all require consistency in practice — which is exactly what separates the managers whose teams grow fastest from those whose teams plateau.