How to Give Feedback That Actually Changes Behaviour

Why timing matters more than most founders assume

Feedback loses most of its value the longer it's held back. Something raised the same day, or within a day or two, is fresh enough that the person can remember exactly what they did and immediately apply the correction to the next similar situation. The same point raised three months later at a formal review has lost its usefulness almost entirely — the details are fuzzy, the moment has passed, and it often feels, fairly or not, like an ambush.

Small teams have a real advantage here: there's rarely a bureaucratic reason to delay feedback to a scheduled review cycle. Use that advantage. A short, timely conversation is almost always better than a longer, delayed one.

A structure that works for almost any feedback

A simple three-part structure covers most everyday feedback situations, whether positive or corrective: what I noticed, why it mattered, and what I'd like to see (again, or instead) next time. This keeps the conversation factual and forward-looking, rather than turning into a judgement of the person's character or ability.

For example: 'I noticed you flagged the delayed order to the customer before they asked — that mattered because it protected their trust in us even though the news wasn't good. I'd like you to keep doing that every time, even on small delays.' The corrective version follows the same shape: 'I noticed the report went out without the updated figures — that mattered because the client made a decision based on wrong numbers. Next time, flag if you're not sure the figures are final before sending, rather than sending anyway.'

1. What I noticed: describe the specific behaviour or outcome, not a generalisation
2. Why it mattered: the actual impact, on the customer, the team, or the business
3. What I'd like next time: a concrete, actionable request, not a vague aspiration

Positive feedback deserves the same specificity

It's tempting to treat positive feedback as easy — a quick 'great work' and moving on. But a generic compliment doesn't tell the person what exactly to keep doing, so it has less power to reinforce the behaviour than specific praise does. Naming the actual behaviour turns a nice moment into a genuinely useful piece of information.

Public praise, given in front of the team where appropriate, can also do real work in a small business by making expectations visible to everyone, not just the person being praised — but check first whether the individual is comfortable with public recognition, since not everyone is.

Giving corrective feedback without damaging trust

Corrective feedback should almost always be given privately, calmly, and as close to the event as reasonably possible. Focus entirely on the specific behaviour and its impact — never on generalised character traits like 'you're careless' or 'you never think things through', which invite defensiveness rather than change and tend to be remembered as an attack rather than useful information.

Leave space for the other person's account of what happened before you conclude anything. There may be a blocker, a miscommunication, or a genuine external cause you weren't aware of. Asking 'what happened from your side?' before delivering the full correction often changes the conversation entirely, and it signals fairness even when the correction still needs to be given.

Corrective feedback about a specific incident is not the same thing as a formal performance process. Most everyday corrections should stay informal — escalate to something formal only when a pattern persists despite fair, clear feedback.

When feedback isn't landing

If you've given clear, specific, well-timed feedback more than once about the same issue and nothing changes, it's worth checking a few things before assuming it's a motivation problem: was the feedback actually understood, does the person have the skills or resources to act on it, and is there a genuine blocker you haven't identified yet.

If those checks come back clear and the pattern continues, this has moved from ordinary feedback into a performance conversation, which should be documented and handled with reference to Acas guidance on managing performance, rather than continuing to repeat informal feedback indefinitely.

Feedback in remote and hybrid settings

Giving corrective feedback over a written channel like chat or email strips out tone and often lands more harshly than intended, so use a call or video conversation for anything beyond a very minor, low-stakes point. Reserve written feedback for confirming what was agreed after a verbal conversation, not for delivering the correction itself.

Positive feedback travels reasonably well in writing — a specific, genuine message of thanks in a team channel can do real work for a remote team where in-person recognition moments happen less naturally.

Common mistakes that blunt feedback's effect

A short list of habits worth checking yourself against.

• Saving up small issues for a formal review instead of raising them close to the event
• Wrapping corrective feedback in so much softening language that the actual point gets lost
• Giving vague praise that doesn't specify what to repeat
• Delivering correction in front of others, which damages trust even when the point itself is fair
• Treating a single incident as a pattern before checking whether it's actually recurring