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. Most feedback owners give 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.
That gap is why so many owners conclude that "feedback doesn't work here" or that a particular person "just doesn't respond to it." Usually the person would respond fine. What they were given was not feedback in any form a behaviour could act on — it was a mood, delivered verbally, with no instruction attached.
Why does feedback so often change nothing?
Because most of what gets called feedback is actually one of three other things: a complaint, a character judgement, or a hint dropped and hoped for.
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 is not a behaviour, it is a verdict. A hint is worse than either, because it 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. Most people cannot, and the ones who can usually fix the wrong thing.
None of these fail because the owner was too harsh or not harsh enough. They fail because none of them contain the three things a person actually needs to change what they do next: what specifically happened, what it cost, and what to do differently. Strip those out and you can deliver the warmest, most diplomatic version of a complaint and it will still produce nothing but a slightly awkward afternoon.
There is also a quieter reason owners avoid the direct version, and it is worth naming honestly: it feels like it risks the relationship. In Performance on Purpose terms, that instinct is protecting purpose — the sense of being liked, of keeping things pleasant — at the direct expense of performance, and over time it usually costs both, because unaddressed problems erode the relationship anyway, just more slowly and with more resentment attached.
What does feedback that actually changes behaviour look like?
Three parts, said in order, in under two minutes: the behaviour, the impact, 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 actually 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 a wish. Not "try to be more careful," but "check the VAT code against the client's setup sheet before you send anything out."
If you can only remember one thing: never end on the impact. A complaint that stops after "here's what it cost" is still just a complaint. The request is the part that gives someone something to do.
Say all three plainly and then stop talking. The instinct many owners have is to cushion the request with reassurance — "but you're doing great generally, don't worry about it too much" — which feels kind and reliably undoes the whole conversation, because it tells the listener the request was optional. Kindness here is being clear enough that the person genuinely knows what to do differently, not softening the message until it disappears.
A worked example: turning a vague complaint into something someone can act on
Take a common one. Imagine a team member who keeps submitting expense claims without receipts attached, and you have mentioned it twice already, in passing, without effect.
The version most owners actually say: "Can you try to be more on top of your paperwork? It's a bit of a mess at the moment." This is a complaint wearing feedback's clothes. It names no behaviour, no cost, and no fix. The person nods, means it, and does exactly the same thing next month, because nothing about what to do differently was ever stated.
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?"
Notice what changed. The behaviour is dated and specific, so there is no room to dispute what happened. The impact is a real number and a real time cost, not a feeling. And the request is a habit the person can start doing tomorrow, not an attitude they are meant to acquire by osmosis. The arithmetic in that example is illustrative rather than a real client's figures, but the structure and the size of the numbers are exactly the range most small businesses see with this specific problem — small individually, and irritating enough in aggregate that it is worth a two-minute conversation rather than a third silent mention.
How do you make this a habit rather than a once-a-quarter ordeal?
The single biggest lever is timing. Feedback given within a day or two of the behaviour costs almost nothing — both people remember exactly what happened, so there is nothing to relitigate. Feedback saved up for a monthly one-to-one or a quarterly appraisal has to reconstruct the memory before it can even start, and by then it has usually curdled into something bigger than the original moment deserved, because you have been carrying it.
Practically, that means treating 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 possibly can, and move on. This is uncomfortable at first precisely because it is unfamiliar — most teams have never experienced a manager who raises small things small, so the first few instances land harder than they should. That discomfort is temporary. A team that gets used to small, quick, specific feedback stops treating any single instance of it as a crisis, which is the opposite of what happens on teams where feedback only ever shows up wrapped in a formal conversation.
It also compounds with structure elsewhere. If nobody owns a clear outcome or a number to check, there is nothing concrete to give feedback against in the first place — that is the problem our piece on building real accountability into your business sets out to fix. And if you have just promoted someone into their first management role, teaching them this exact three-part structure is worth more than any course; see promoting your first manager for the six weeks that decide whether that promotion sticks.
What if the behaviour doesn't change after you've done all of this properly?
Then you have learned something useful, which a vague conversation would never have told you. 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, you are no longer looking at a feedback problem. You are looking at one of three things: the person cannot do what you asked (a skill or resourcing gap), the person does not understand what you asked (feedback wasn't actually as clear as you thought), or the person will not do what you asked (a genuine performance issue).
Good three-part feedback is what lets you tell those apart, because it rules out the excuse that the request was never clear. Our guide on managing poor performance picks up exactly at this point, once you have already established that the person understood what was being asked and simply has not delivered it. Do not skip to that guide before you have given clean feedback at least once; jumping straight to a formal process on the back of a hint or a complaint is how owners end up with a grievance instead of a fixed problem.
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 actually 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. Resist the urge to soften the request with reassurance once you have said it clearly.
- If a piece of feedback has already gone nowhere twice, treat that as data: the structure was probably missing the impact or the request, not that the person is unreachable.
Get the next one in your inbox
One practical, plain-English guide for business owners each week. No spam, unsubscribe any time.
Frequently asked questions
Is this not just a fancy way of saying be more direct?
No, and treating it that way is why so much direct feedback still fails. 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 actually 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, because the structure is doing the job, not the volume. Owners who mistake volume for clarity tend to get compliance in the room and no change afterwards.
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 usually fades within a day once the surprise wears off. 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. If you cave and dilute the message because someone looked upset, you have taught them that visible discomfort makes feedback go away, which is a lesson they will use again.
How often should I actually be doing this, rather than saving it for appraisals?
As close to the moment as you reasonably can, which for most owners 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, rather than continuing to wait for a moment that feels comfortable, because that moment does not arrive on its own. 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, which is honest and also disarms the obvious question of why now. 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 that honestly and then move straight into the structure rather than staying in the apology.