Feedback that changes behaviour describes one specific action, names the concrete effect it had, and asks for one specific thing instead — delivered close to the moment, not saved up. Feedback often fails on all three counts: it arrives weeks late, it describes a person rather than an action, and it stops at the complaint without ever stating what should happen next time.
Why does feedback so often change nothing?
Much of what gets called feedback is one of three other things: a complaint, a character judgement, or a hint.
A complaint describes how the owner feels — "I'm not happy with how that went" — without describing what happened. A character judgement attaches the problem to the person rather than the action — "you're just not detail-oriented" — which nobody can act on because it names no behaviour. A hint is designed to be deniable: a pointed comment in a team meeting, a sigh, a slightly cooler tone, all aimed at someone who is meant to work out what it means and fix it unprompted.
All three leave out what a person needs to change what they do next: what happened, what it cost, and what to do differently.
Owners also avoid direct feedback because it feels like it risks the relationship. In Performance on Purpose terms, that instinct protects the sense of being liked at the expense of performance, and unaddressed problems damage the relationship anyway.
What does feedback that changes behaviour look like?
Say three parts in order, in under two minutes: the behaviour, the impact and the request.
- The behaviour. One specific, observable thing — something you could have filmed. Not "you've been sloppy lately," but "the last two client invoices went out with the wrong VAT code on them."
- The impact. What that specific behaviour cost, in time, money, trust or risk. Not "it's not great," but "I had to reissue both, and one client queried why we'd got it wrong twice."
- The request. One concrete thing to do differently next time, stated as an instruction. Not "try to be more careful," but "check the VAT code against the client's setup sheet before you send anything out."
Say all three plainly and then stop talking. Cushioning the request with reassurance, such as "but you're doing great generally", tells the listener the request was optional.
Worked example: missing expense receipts
Imagine a team member who keeps submitting expense claims without receipts attached, and you have mentioned it twice already, in passing, without effect.
The vague version: "Can you try to be more on top of your paperwork? It's a bit of a mess at the moment." It names no behaviour, no cost and no fix, so the person does the same thing next month.
The three-part version: "The last three expense claims came in without receipts — the taxi on the 3rd, the client lunch on the 9th and the parking on the 14th. Without the receipts I can't reclaim the VAT on any of them, and at roughly 20% that's about £14 of VAT we've lost on those three alone, plus the twenty minutes each time I've had to chase you for them. From now on, claims without a receipt attached don't get processed until the receipt is there — can you get into the habit of photographing it at the till before it goes in your pocket?"
The behaviour is dated and specific, so there is no room to dispute what happened. The impact is a number and a time cost. The request is a habit the person can start tomorrow. The figures in the example are illustrative.
How do you make feedback a habit?
Give feedback within a day or two of the behaviour, while both people remember what happened. Feedback saved for a monthly one-to-one or a quarterly appraisal has to reconstruct the memory first, and by then it has often grown bigger than the original moment.
Treat feedback as a two-minute interruption to the working day rather than a scheduled event. See the behaviour, say the three parts before the end of that day if you can, and move on. The first few instances can feel uncomfortable, and once a team is used to small, quick, specific feedback, no single instance feels like a crisis.
Feedback needs something concrete to measure against. If nobody owns a clear outcome or a number to check, start with building real accountability into your business. If you have just promoted someone into their first management role, teach them this three-part structure; promoting your first manager covers the first six weeks.
What if the behaviour does not change?
If you named the behaviour, the impact and the request clearly, and gave it a fair run — a couple of weeks for a habit, longer for something that needs practice — and nothing moved, the cause is one of three things: the person cannot do what you asked (a skill or resourcing gap), the person does not understand what you asked (the feedback was less clear than you thought), or the person will not do what you asked (a performance issue).
Clear three-part feedback lets you tell those apart. Once you know the person understood what was asked and has not delivered it, our guide on managing poor performance covers the next steps. Give clear feedback at least once before starting a formal process.
What to do this week
- Think of one piece of feedback you have been avoiding or diluting, and write down the behaviour, the impact and the request in three separate sentences before you say anything out loud.
- Notice the next time you catch yourself saying "try to be more careful" or "try to be more on top of things," and rewrite it as an instruction someone could follow tomorrow morning.
- Give one piece of small feedback within 24 hours of seeing the behaviour, rather than saving it for your next scheduled one-to-one.
- After you deliver it, stop talking and do not soften the request with reassurance.
- If a piece of feedback has already gone nowhere twice, treat that as data: the structure was probably missing the impact or the request.
Get the next one in your inbox
One practical guide for business owners each week. Unsubscribe at any time.
Frequently asked questions
Is this the same as being more direct?
No. Bluntness changes the tone of the delivery, not the content of it, and most feedback that goes nowhere was already delivered bluntly — "that report was a mess" is direct and completely useless, because it gives the other person nothing to act on. What changes behaviour is specificity: naming one observable action, one concrete effect it had, and one request for what should happen instead. You can say all three gently or firmly and it will still work. Practise the three parts on one small issue this week before you use them on a bigger one.
What if the person gets upset or defensive when I raise it?
Expect it sometimes, and do not treat it as a sign you did something wrong. A person who has not been given clear feedback before will often experience the first real instance of it as an attack, purely because it is unfamiliar, and that reaction often fades within a day. Your job in the moment is to hold the structure rather than soften the content: repeat the observed behaviour and its impact calmly, resist the urge to withdraw the point to make the discomfort stop, and end on the request rather than on reassurance.
How often should I give feedback?
As close to the moment as you reasonably can, which means within a day or two rather than saved for a quarterly review. Feedback loses most of its power to the gap between the behaviour and the conversation about it: raise a missed deadline eight weeks later at appraisal and the person barely remembers the specifics, so there is nothing left to correct except a vague sense of having been marked down. Small, quick, specific feedback delivered close to the event is both easier to give and far more likely to change anything, because the behaviour and its consequence are still connected in both your minds. Appraisals should summarise a pattern you have already discussed, never introduce one for the first time.
What do I do about something I have been avoiding raising for months?
Raise it once, properly, without waiting for a comfortable moment. Prepare the same three parts — the specific behaviour, its concrete impact, and what you want instead — and say plainly that you should have raised it sooner. Expect the conversation to be harder than it would have been in week one, because the person has had months of silence that read as tacit approval, and be ready for a fair question back: why did it take this long. Answer it and then move into the three parts.