Giving and receiving feedback at work

Good feedback is specific, timely and focused on the work rather than the person, and it runs in both directions. Giving it means describing what you observed, what effect it had and what you would like to see next. Receiving it means listening for the substance before responding, asking clarifying questions and showing what you do with the input.

Most feedback conversations go wrong not because of the content but because one person hears judgment where the other intended help. Clear requests, a calm setting and a habit of following up prevent much of that friction.

Ask for specific input

General questions such as "Any thoughts?" tend to produce vague answers. Narrower questions get more useful information, such as "What is one thing that would have made the presentation clearer?" or "Where did the status summary fall short for you?" Naming the situation helps the other person recall the details and gives them a clear task. Ask soon after the event, while the details are fresh, and say how you plan to use what you hear.

Build feedback into your routine instead of waiting for an annual review. A short check-in after a project milestone, or a regular question at the end of a one-on-one, gives you small signals early enough to adjust. Frequent, small requests are easier for others to answer than one large request for a full assessment.

Choose your sources carefully as well. A peer may notice different things than a manager, and a client may see a side of your work that colleagues never do. Collect input from several places over time and look for patterns that appear more than once. A single comment can reflect one person's preference, while a repeated theme deserves attention.

When someone takes the time to answer, follow up with a short thank-you that names the point you found most useful. People who see their input used are more willing to help again.

Receive comments without getting defensive

Your first reaction is often to explain or defend yourself. Slow that response down. Thank the person, restate what you heard in your own words and ask one clarifying question, such as what a better result would look like. The aim is to understand the comment fully before deciding whether you agree with it. Defensiveness closes the conversation and makes people less likely to give candid input next time.

Separate the observation from the conclusion. "The report arrived after the deadline" is an observation you can check. "You are unreliable" is a conclusion that calls for examples and more context. You can accept the observation, ask for the examples behind the conclusion and decide afterward what to do. If the feedback feels unfair, say so calmly and with facts, and still thank the person for raising it.

If you need time to think, say so. Ask for a follow-up conversation rather than responding in the moment, especially when the comment is unexpected. A pause gives you room to hear the substance and prevents a reply you later regret.

Give feedback others can use

A useful structure for giving feedback is to describe the situation, the specific behavior you saw and its impact. Many managers and trainers use a version of this approach, often summarized as situation, behavior and impact. In practice it might sound like this: "In Monday's client call, you interrupted the client twice. The client stopped sharing their concerns, and we ran out of time to address them." Then invite a response, for example by asking how the person saw the call and what they would like to do differently next time.

Check that the message landed as intended. Ask the other person to say in their own words what they heard, which quickly shows whether the point was clear. If they dispute a fact, listen for the specific detail and correct only that part, rather than defending the whole observation.

Keep feedback timely and proportionate. Raise minor points soon after they happen, and save larger concerns for a scheduled one-on-one rather than a group setting. Avoid stacking several unrelated issues into one conversation. When you point out what someone did well, use specifics rather than general praise, since vague compliments are easy to dismiss.

Act visibly on what you hear

Feedback has value only when it leads to change, and people notice whether you act. After a conversation, write down the two or three points you plan to address and share a short update within a week or two. For instance, you might tell your manager that you now send agendas before weekly meetings and would welcome a check on whether they help. Visible follow-through builds trust and signals that future feedback will be heard.

After you make a change, ask whether it helped. A question such as whether the new agenda made the meeting easier to run keeps the loop open and gives you evidence that your effort landed. It also reminds the other person that feedback leads to visible results.

Some comments will not fit your priorities, and you do not have to act on every suggestion. Explain your reasoning briefly and say what you are doing instead. Closing the loop matters even when the answer is no, because it shows you considered the input seriously. A feedback habit built this way makes later conversations easier, since both people know how the other will respond.