Giving Feedback That Actually Changes Behaviour

Almost everyone has been told to give more feedback. Far fewer have been told what good feedback sounds like, which is why most of it is some combination of too vague, too late, and so carefully softened that the person leaves unsure anything was wrong.

Feedback that changes behaviour has a recognisable shape. It is not complicated, but it does require giving up two habits most managers have.

Habit one to drop: the praise sandwich

Praise, criticism, praise. It is taught everywhere and it fails for a specific reason: people remember the opening and closing and discard the middle. You deliver a concern, they hear that things are broadly fine, and you are then baffled when nothing changes.

Worse, used repeatedly it poisons praise itself. Once a team learns that compliments precede criticism, every compliment becomes a warning and genuine recognition stops landing.

Praise and correct separately, and mean both.

Habit two to drop: feedback about the person

"You're disorganised" is a verdict on character. It cannot be acted on, and it invites defence rather than change. "The last three reports came in after the deadline" is an observation that can be discussed.

The test: could the person argue with it? If the answer is a matter of opinion about who they are, you have given a judgement. If it is a matter of what happened, you have given feedback.

A structure that works

Situation. When and where. "In yesterday's client call."

Behaviour. What you observed, specifically, without interpretation. "You answered the pricing question before Sarah had finished explaining the scope."

Impact. What followed. This is the part that makes it matter. "The client anchored on that number and we spent the rest of the call defending it."

Then stop and listen. The most-skipped step. There is often context you do not have — they may have been heading off a worse question. Deliver, then genuinely ask.

Agree what changes. Not "be more careful". Something observable. "In client calls, let the scope conversation finish before pricing comes up."

Timing beats polish

Feedback delivered badly on the day beats feedback delivered beautifully six weeks later. Delay creates three problems: memory diverges, the behaviour repeats and becomes habit, and the person reasonably asks why you said nothing at the time.

If you are saving items for an appraisal, you are not managing — you are collecting evidence. Nothing in a formal review should be a surprise.

Positive feedback is the one being underused

Most managers worry about the hard conversations and under-invest in the easy one. Specific positive feedback is the cheapest management tool available and the most wasted.

"Great job" tells someone nothing repeatable. "The way you restructured that paper so the recommendation came first — the board got to the decision in ten minutes instead of forty" tells them exactly what to do again.

Aim to be specific about what worked at least as often as about what did not.

When it is serious

There is a point where feedback stops being feedback and becomes a performance conversation with procedural consequences. Crossing that line without saying so is unfair to the person and creates problems for you.

Be explicit when it changes. "This is a conversation about whether this role is working" is a different sentence from a note about a late report, and the person is entitled to know which one they are in. At that point formal procedures and fair process apply — see our guide to managing poor performance and fair procedures. For the conversation itself, our guide to difficult conversations at work covers the structure.

Receiving it, briefly

How you take feedback determines how much you get. If your first move is explanation, people learn that feedback to you costs them effort, and they stop. Say thank you, ask one clarifying question, and sit with it before responding. You can disagree later; disagreeing immediately ends the supply.

Frequently asked questions

How often should I give feedback?

Close to the event, whenever there is something worth saying. Scheduling it monthly guarantees it arrives late.

What if they get upset?

Let them. Do not retract something true to relieve the discomfort — that teaches the team that emotion ends the conversation. Pause, acknowledge, continue.

Should feedback be written?

Spoken first, always. Written afterwards if it is serious enough to need a record.

What about feedback upward?

Same structure, more context, and pick the moment. Situation, behaviour, impact works in both directions.

Our CPD courses include management development mapped to professional body requirements, and our guide to your first management role covers the wider transition.