What Great Feedback Looks Like
Most of us have given feedback that did not work. We either softened it so much it said nothing, or delivered it so bluntly it put the other person on the defensive. There is a better way.
By The Weekly Reset Team
Feedback is one of those things that sounds simple in theory and proves surprisingly difficult in practice. The intention is straightforward: help someone understand how they are doing and what they could do differently. What actually happens is often quite different.
The feedback is too vague to act on. Or it arrives at exactly the wrong moment. Or it is framed in a way that makes the person feel attacked rather than helped, and the conversation closes down before anything useful can come out of it. Good intentions, poor outcome.
The mechanics of useful feedback are not complicated, but they do require a deliberate approach that most people never bother to learn.
Describe what you saw, not what you concluded
The most common feedback mistake is leading with an interpretation rather than an observation. Telling someone they lack initiative, come across as disorganised, or do not show enough ownership gives them a conclusion without the evidence. They have no way to evaluate whether you are right, no way to see what you saw, and no path to changing anything specific.
Starting with a concrete description of what actually happened is a different kind of conversation. You were not the one who raised the issue in the client call, and I think that changed the direction of the meeting, gives the person something real to reflect on. They can consider whether they agree, what was behind their behaviour, and what they might do differently next time. That is the beginning of a productive exchange. The conclusion on its own is just a verdict.
The timing changes everything
Feedback given long after the event loses most of its usefulness. The details have faded, the context is gone, and the person being given the feedback cannot connect what you are saying to anything specific they remember. What should be useful information starts to feel like a grievance being aired at an unhelpful moment.
The closer to the event the better, with one exception: the heat of the moment is not ideal either. A short gap of a few hours, enough to ensure the delivery is measured, is worth it. But a few hours is very different from a few weeks.
Make it a conversation, not a delivery
A lot of feedback sessions are structured as a one-way transmission. The person giving the feedback speaks; the person receiving it listens, hopefully nods, and the session ends. This feels tidy but it rarely produces change, because the person receiving the feedback has had no chance to engage with it.
Asking what the other person makes of what you have said, whether they see the situation the same way, or what was going on from their perspective turns the exchange into something more honest. You might learn something that changes your view. They are far more likely to genuinely reflect on feedback they helped examine than feedback they simply received.
The version people forget
Positive feedback done well is as useful as critical feedback, and it uses exactly the same mechanics. Specific, timely, behaviourally described. The way you redirected that conversation when it started to go sideways is the kind of detail that tells someone what to do more of. Well done does not.
Good feedback, in either direction, is not a performance. It is a contribution to someone else's thinking. Treated that way, it becomes something people are glad to receive rather than something they brace for.