How to give and receive feedback at work

A lot of workplaces still treat feedback like a ritual rather than a skill. It shows up in annual reviews, after a problem has festered, or in a vague comment that lands badly and then gets repeated for months. Meanwhile, Gallup’s State of the Global Workplace 2024 reports that only 23% of employees worldwide were engaged in 2023. That’s not a feedback problem alone, but it is a warning sign: many teams are not getting the kind of honest, useful conversation that helps people improve.

The awkward part is that most people want feedback. They just don’t want surprise attacks, fuzzy praise, or performative honesty dressed up as “candour”. They want something they can use on Monday morning. They also want a way to hear difficult messages without turning defensive, disappearing, or turning the whole thing into a debate about wording. That’s the real work here.

Why it matters now

Work has become more distributed, more written, and more visible. People are often collaborating across chat, video, documents, and project tools rather than in one room, which means misunderstandings can grow fast if nobody checks them early. Feedback is no longer a once-a-quarter manager task. It’s part of how teams stay aligned when signals are thinner and context gets lost in translation.

There’s also a broader shift in management expectations. Right? Employees increasingly judge managers by how clearly they communicate, how often they coach, and whether they make it safe to raise problems before they become incidents. In that environment, feedback is not a soft skill on the margins. It is operating system stuff.

The core idea

Btw, Good feedback has one job: change what happens next. That sounds obvious, but it’s where most feedback falls apart. People either talk too generally to be useful, or they bury the useful part under judgement, emotion, or too much history. The best feedback is specific enough to act on and small enough to absorb.

That means separating three things that often get mixed together:

• Observation: what actually happened, without interpretation.
• Impact: what that behaviour changed, caused, or risked.
• Request or next step: what should happen differently next time.

Btw, If you blur these together, the conversation becomes slippery. “You’re careless” is not feedback. “The report had three broken links and the client flagged them before the meeting” is closer. Add the impact - “that made us look unprepared” - and then a next step - “please run a final link check before sending” - and now the person has something they can do.

The same logic applies when you receive feedback. Your first job is not to agree with everything on the spot. It is to understand what is being said well enough to decide whether to act on it. That takes a little discipline. You listen, ask one or two clarifying questions, and resist the urge to turn every comment into a courtroom defence.

Aim for feedback that a tired person can use on a busy Tuesday.

There is also a difference between feedback on performance and feedback on style. Performance feedback is about results, decisions, and behaviour that affects work. Style feedback is about preferences, tone, and interaction habits. Both matter, but they should not be confused. Someone may dislike your meeting style; that does not automatically mean your work quality is weak.

A practical feedback exchange often follows this shape:

1. State the context briefly.
2. Describe the observable behaviour.
3. Explain the effect.
4. Invite a response or agree a fix.
5. Check that the next action is clear.

This is simple, but not easy. Simplicity is the point. The more emotion is involved, the more structure helps.

What this looks like in practice

A mid-size SaaS team ships features fast, but customer complaints keep pointing to confusing onboarding. The product lead gives feedback to a designer in a weekly review: not “the flow is bad”, but “users are dropping at step 3 because the labels don’t match the next screen”. The designer doesn’t need a speech. They need a clear bug to fix.

A solo freelancer gets a client note that a draft “doesn’t feel right”. That’s useless as written, so they ask for one example of what feels off, one example of what feels right, and the intended audience. The feedback becomes usable only after it is made specific. That is often the difference between endless revision and a quick turnaround.

A 50-person agency runs into a common pattern: juniors avoid upward feedback because senior people seem busy, and seniors assume silence means things are fine. When a project slips, both sides are surprised. A regular habit of low-stakes feedback - short reviews after deliverables, not only during crises - creates earlier warnings and fewer awkward escalations.

Common mistakes to avoid

• Using labels instead of evidence. Saying someone is “disorganised”, “not strategic”, or “hard to work with” gives them a verdict, not a path forward. Labels make people defend themselves. Evidence gives them something to inspect.

• Waiting too long to speak. Feedback loses power when it arrives weeks later and is bundled with five other grievances. The person hears a history lesson, not a correction. If it matters, say it while the details are still fresh.

• Making feedback about your mood. “I felt annoyed” may be true, but it is not enough on its own. Translate the feeling into a work-related effect. What did the behaviour change? What risk did it create? That’s the useful part.

• Softening the message until it disappears. Overly polite language can become unclear language. If there is a problem, name it cleanly. People can handle directness better than they can handle vague disappointment.

• Receiving feedback as if it were a verdict on your character. Many people hear one comment and immediately jump to identity: “I’m bad at this”, “they don’t respect me”, “I’m being singled out”. Slow down. A piece of feedback may be about one situation, not your entire ability.

• Arguing before you understand. Defensiveness is natural, but it can shut down the very information you need. If the feedback is poor, you can challenge it later. First, get the facts, the examples, and the expectation.

A practical checklist

1. Prepare one real example before you speak. If you are giving feedback, anchor it in a recent, observable situation. If you are receiving it, ask for one example if the comment is vague.

2. Use a short structure. Try: situation, behaviour, impact, next step. Keeping the shape consistent makes hard conversations easier to repeat.

3. Keep the conversation close to the work. Focus on output, decision-making, communication, timing, or process. Avoid psychoanalysing the person unless there is a real conduct issue.

4. Ask one clarifying question before responding. Good options are: “Can you give me an example?” or “What would better look like next time?” This slows the moment down without being evasive.

5. Separate feedback from evaluation when you can. A review meeting is not the best place to process every frustration from the past quarter. If possible, give performance feedback in a planned setting and small corrections in the flow of work.

6. Agree on the next action immediately. End with a specific change, a follow-up date, or a simple check-in. Feedback without a next step often becomes emotional theatre.

7. Write down the gist after the conversation. A sentence or two is enough. It helps both sides remember what was actually agreed, not what they later assumed was said.

When NOT to do this

There are moments when direct feedback is the wrong first move. If someone is in clear distress, overwhelmed by workload, or dealing with a sensitive personal issue, a blunt critique can make things worse. Timing matters. So does sequence.

There is also a trap on the other side: not every annoyance deserves a feedback meeting. If a preference is merely your preference, treat it as one. A lot of work relationships deteriorate because people formalise every minor difference. Sometimes the better move is to adapt, let go, or simply note the difference and move on.

Where to learn more

• https://www.gallup.com/workplace/ - research on employee engagement and management.
• https://en.wikipedia.org/wiki/Feedback - a broad overview of feedback as a communication process.
• https://hbr.org/topic/feedback - practical management and communication articles from Harvard Business Review.

The best feedback does not sound clever. It sounds clear, fair, and usable. If you can give it without theatre and receive it without panic, you will fix more problems early, waste less time later, and probably become much easier to work with - which, honestly, is one of the rare advantages that compounds.