Goal
Give feedback that lands
Feedback lands when the person hears it as help with a piece of work rather than a verdict on who they are, and when something they do next week is different because of it. That takes five moves: small and soon rather than saved up, a weekly one-on-one that gives it a regular home, your own part named before theirs, a team where peers say it to each other instead of waiting for you, and a check afterwards on whether anything changed. Praise follows the same rules, and most people give far too little of it.
What is really going on
Most feedback fails before it is said, because it waits. The report with last quarter's figures, the client call that went badly, the habit of arriving ten minutes late to the morning meeting: each one is noticed and filed away, because the moment is awkward and the week is busy. By the time it comes out, in an annual review or in an irritated sentence on a bad day, it is no longer about a report. It is about a person, and the person hears it that way.
The fixes people reach for make it worse. The feedback sandwich hides the point between two compliments, so the listener either misses it or learns to brace whenever you praise them. Softening words, maybe, a little, just a thought, turn a clear request into a hint that can be politely ignored. The opposite reflex, bluntness that calls itself honesty, delivers the message and loses the person, who spends the rest of the conversation defending themselves instead of listening.
Picture Elif, who runs a small sales team at a furniture company in Kayseri. For a month she has watched one of her reps quote prices from memory, twice getting them wrong by a few thousand lira. She says nothing, because he is well liked and hits his targets. Two of his colleagues have noticed too, and they say nothing either, because they assume it is her job. When a client finally complains to the general manager, the conversation everyone avoided happens in its worst form: late, in front of others, and about his reliability. The five books below give the order in which that conversation should have gone.
Five ideas from five books
- 1
Keep it small, fast and about the work
Kim Scott's advice is to stop treating feedback as an event. Most of it should be a two- or three-minute conversation, in private, within a day of the thing happening, while both of you still remember the details and the stakes are still small. Talk about the work and what it caused, not about the person: 'the figures on page two were from last quarter, and the client noticed', not 'you are careless'. Praise gets the same treatment, specific and soon, and in front of others if the person enjoys that. For Scott, success is measured by what the listener understood, not by what the speaker said, so end by asking them to put it in their own words.
- 2
Give feedback a weekly home in the one-on-one
Andrew Grove's weekly one-on-one solves the problem that makes most feedback late: there is no natural moment for it. Book thirty to sixty minutes with each person, same slot every week, and treat it as their meeting, with their agenda and most of the talking theirs. Feedback then has somewhere private, regular and expected to go, and a small correction no longer needs a special summons that makes it sound serious. Grove has the manager ask one level deeper than the first answer: what happened, why, what would you do differently. Often the person reaches the point before you do. And because the agenda is theirs, it is also where they tell you what is in their way.
- 3
Name your own part before theirs
Stone, Patton and Heen observe that almost every problem at work was produced by more than one person, and that feedback framed as blame makes the listener defend rather than change. So map the contribution before you speak. Did you explain what good looked like? Did you review the draft in time, or hand over the client without notes? Say your part first, briefly and without drama, and theirs becomes easier to hear. Separate intent from impact as well: you know the effect their action had on you and the team, not why they did it. Describe the effect, and ask about the reason instead of announcing it.
- 4
Let feedback run sideways, not only down through you
Patrick Lencioni argues that on a strong team, accountability runs between peers, not only from the manager down. If you are the only person who ever says 'you said Thursday', every slip becomes a matter between one person and the boss, and the team learns to manage you rather than each other. Peers also see the work first, so their feedback can arrive soonest. That takes conditions: commitments said aloud with owners and dates, standards everyone has heard, and progress reviewed in the group. Then the moment that decides whether it sticks: the first time one member holds another to a date, say in front of the team that this is exactly right instead of smoothing it over.
- 5
Check the target first, then close the loop
Julie Zhuo's test is blunt: feedback that changed nothing was not feedback, however well it was delivered. Two habits help it pass. First, before criticising a result, check whether the person knew what a good one looked like. Many performance problems are an unclear purpose or a broken process rather than a people problem, and the fix is a clearer brief, not a harder talk; state the expectation at the start of the work, not after it. Second, close the loop: agree what will be different and how you will both know, look again at the next one-on-one, and say so out loud when the change happens. Noticed improvement is the praise that sticks.
Try this today — free
Today, pick one piece of feedback you have been holding back. Write down what happened and its effect, your own part in it and what you would like to be different, then say it in private, in under three minutes, before the day ends.
Questions people ask
- How do I give negative feedback without upsetting someone?
- You cannot promise they will not be upset, and that is not the goal; the goal is that they understand and something changes. Keep it private, soon and about the work: what happened and its effect first, then your own part and one specific request. Upset that comes from hearing a clear fact usually passes. Resentment that comes from a verdict on someone's character does not.
- Does the feedback sandwich work?
- Rarely. Wrapping criticism between two compliments hides the point, and people who hear it often enough learn to brace whenever you praise them, which spoils the praise too. Give praise and criticism separately, each on its own merits, and give praise more often, so that criticism arrives in a relationship that is not only corrections.
- How often should I give feedback to my team?
- Far more often than once a quarter. Small, specific comments within a day of the event, praise as well as criticism, do more than one big conversation saved for a review. If anything in an annual review surprises the person, the feedback came too late. A few minutes per person each week is a reasonable rhythm, and the weekly one-on-one is its natural place.
- What should I do if someone gets defensive when I give feedback?
- Stop pressing the point and get curious. Defensiveness usually means the person heard a verdict about who they are rather than a fact about the work. Restate the fact, say what you do not mean, 'I am not questioning your commitment', name your own part and ask how they see it. Return to your request only after that.
- How do I give feedback to my manager or a colleague?
- Ask permission first and be even more specific: one event, its effect on your work, and one request. With a manager, connect it to something they already care about, such as a deadline or a client. With a peer, ask in return what you could do differently. Feedback upwards and sideways lands best when it is rare, private and clearly useful.