Feedback That Changes Behaviour: A Practical Guide for Leaders

Feedback is one of the most discussed and least effectively practised leadership capabilities. Most leaders have received training on how to give feedback, can describe the frameworks they were taught, and still find that the feedback they give does not reliably produce the behaviour change they intended. The gap between knowing how feedback should work and being able to give feedback that actually works is wide and real. Understanding why it is wide is the starting point for closing it.

Why most feedback does not land

Feedback that does not produce behaviour change usually has one of three problems. It is too general to act on: observations like your work has been good lately or you need to be more proactive tell the recipient how they have been assessed but not what they should do differently. Without specificity about the behaviour, there is no behaviour to change. General feedback changes nothing because it provides no direction. The second problem is timing: feedback delivered long after the behaviour it addresses is feedback without context. The recipient cannot clearly remember the situation being referenced, which makes the feedback feel abstract and the connection between behaviour and consequence tenuous. Immediate or near-immediate feedback — delivered when the event is fresh for both parties — produces much clearer connection between the observation and the behaviour. The third problem is framing: feedback delivered as evaluation — you did this well, you did this poorly — positions the recipient as the subject of judgement rather than as a participant in improvement. Evaluative framing activates defensiveness rather than receptivity, which is the opposite of what feedback is designed to produce. Feedback framed as observation and invitation — I noticed this, I want to understand it, here is what I think it could look like differently — is substantially more likely to be received in a way that leads to change.

The specificity requirement

Effective feedback is always specific: it references a particular situation, a particular behaviour, and a particular consequence or impact. Not your presentations have been unclear lately but in the client presentation on Tuesday, the financial projections section was presented before the problem context, which meant the committee was evaluating numbers without the frame needed to assess them. That specificity gives the recipient something concrete to think about and something specific to do differently. Specificity also protects the feedback from the perception of bias or subjectivity. A general observation — you need to communicate more clearly — can be experienced as a personality judgement with which the recipient can reasonably disagree. A specific observation — in this meeting, the information was presented in this order, which produced this response — is an account of an event that is harder to dismiss and easier to learn from.

The invitation that completes feedback

Feedback that is purely transmitted — from leader to team member, without dialogue — misses half of its purpose. The most important part of a feedback conversation is what happens after the observation: the invitation to the recipient to share their understanding of the situation. Did they see the same event the same way? What was the context they were operating in? What was driving the behaviour the leader observed? These questions are not concessions to relativism — the feedback stands. They are the mechanism through which the leader learns whether their observation is complete and the recipient moves from receiving feedback to owning improvement. A recipient who has been invited to contribute to the understanding of a situation, rather than simply being told what was wrong with their behaviour, is far more likely to leave the conversation with a genuine commitment to doing something differently. Ownership of improvement is not produced by well-delivered feedback alone. It is produced by conversation that involves the recipient in diagnosing and solving the problem rather than simply informing them of it.

Positive feedback is not the easy half

Positive feedback — recognising what someone did well and why it mattered — is commonly treated as the easy complement to developmental feedback. It is not easy, and it is not less important. Positive feedback that is specific and explains the impact of the behaviour — the decision you made in the client meeting to push back on the timeline worked because it protected the quality of the delivery and the client respected the honesty — is substantially more powerful than general affirmation. It tells the recipient exactly what to keep doing and why it matters, which makes it likely to be repeated deliberately rather than by accident. Feedback cultures in organisations are built or undermined by the quality of positive feedback as much as developmental feedback. An organisation where good work is specifically and regularly recognised produces people who know what they do well and who feel seen in their contribution. An organisation where recognition is generic and rare produces people who cannot tell whether they are performing well and who are therefore constantly uncertain about whether to keep doing what they are doing. The leader who gives specific, timely, genuine positive feedback as consistently as they give developmental feedback is the leader whose team performs with the most confidence and the most clarity.

For further reading on this topic, check out our guide on How to build a marketing team as your company grows.