How to Give Constructive Feedback at Work

Knowing how to give constructive feedback at work is one of those rare leadership skills that compounds across your career. Done well, it builds trust and high performance. Done badly, it kills relationships and motivation. Here is the practical framework, the scripts and the etiquette for receiving feedback yourself.

Why feedback usually fails

• It's vague: "you need to communicate better".
• It's late: 6 weeks after the moment.
• It's emotional: delivered in frustration.
• It's public: shaming dressed as coaching.
• It's one-way: no chance for the receiver to respond.

Fix those five and your feedback becomes 10x more useful overnight.

The SBI framework — your default

Situation, Behaviour, Impact. Three short sentences that strip emotion and add clarity:

• Situation: "In yesterday's design review with the marketing team..."
• Behaviour: "...you cut Sarah off twice while she was explaining the new spec."
• Impact: "Sarah didn't share her last point, and the team missed the input we needed."

End with a request: "Next time, can you let her finish even if you disagree?"

When to give feedback

• Immediate, casual feedback: within 24 hours of the event.
• Major behavioural feedback: in a private 1:1, prepared, scripted.
• Formal performance review: quarterly or annually, summarising recurring patterns.

Never give critical feedback in a group setting. Praise can be public; criticism is always private.

Praise: cheap, specific, public

"Good job" is forgotten. "Sarah's three follow-up questions in the client meeting today turned a polite nod into a signed contract" is remembered for years. Make praise specific, name the behaviour and link it to the impact.

Hard conversations: the 6-step structure

1. Schedule it. "Can we talk for 15 minutes tomorrow about the project?"
2. Frame the intention. "I want to share some feedback because I value your work and want to help you grow."
3. Use SBI. Situation, behaviour, impact.
4. Pause and ask. "I'd like your perspective on this."
5. Agree on next steps. One specific change, with a follow-up date.
6. Document. A 3-line written summary in Slack or email.

Scripts for common situations

Missed deadline

"In the last two sprints, three of your stories slipped past their committed dates without prior warning. The team had to rebalance work mid-sprint twice. Going forward, I'd like you to flag risks 48 hours before the deadline so we can adjust together."

Email or Slack tone

"Your reply on the #engineering channel this morning came across as dismissive. Two engineers messaged me about it. I know that wasn't your intent — could we agree to add a sentence of context whenever you push back, especially in writing?"

Quality concern

"In your last two PRs, the test coverage dropped below our 80% threshold and reviewers had to flag missing edge cases. I'd like us to slow down a bit on the next one and pair-review before merge. Does that work for you?"

Behaviour in meetings

"In the standup yesterday, you spoke for about 6 of the 10 minutes. The team didn't get to share blockers. Going forward, can you keep your update under a minute and we'll save deeper discussion for after?"

Avoid these phrases

• "You always..." or "You never..." — almost never true and triggers defence.
• "I'm not sure how to say this..." — get to the point.
• "Other people on the team think..." — name the source or don't say it.
• "Don't take this personally..." — they will. Frame it kindly instead.

The radically candid sweet spot

Kim Scott's framework: care personally, challenge directly. Most managers default to either "ruinous empathy" (kind but vague) or "obnoxious aggression" (clear but cold). The growth zone is honest + warm. Practice both.

How to receive feedback yourself

1. Default to gratitude. Even if it stings, "thank you for telling me" is the right opener.
2. Ask one question to clarify instead of explaining or defending.
3. Sit with it for 24 hours before reacting.
4. Look for the 10% truth in even the harshest feedback.
5. Loop back. "I thought about what you said. Here is what I'm going to try differently."

The quarterly feedback ritual

Every quarter, run this 30-minute conversation with each direct report:

• 10 min: 3 things they're doing well.
• 10 min: 2 things to work on, with specific examples.
• 5 min: career and growth check-in.
• 5 min: their feedback to you.

Common manager mistakes

• Saving feedback for the annual review (too late, too vague).
• Sandwiching criticism between two compliments (people learn to dread the compliment).
• Outsourcing the conversation to HR.
• Asking "how do you think it went?" hoping they will self-criticise — it usually doesn't work.
• Avoiding the conversation when the issue is about race, gender or another sensitive topic — get coaching, but still address it.

The culture compounds

A team where feedback flows in both directions outperforms a team where it only flows from the top. Model the asking ("what could I be doing differently?") and the receiving (without defending) and within 6 to 12 months the team is significantly stronger.

The 7-day starter

1. Day 1: write down two pieces of feedback you've been avoiding.
2. Day 2: schedule the 1:1 conversations.
3. Day 3: give the first piece of feedback using SBI.
4. Day 4: send a 3-line follow-up summary.
5. Day 5: ask one direct report for feedback on you.
6. Day 6: thank them, ask one clarifying question, take notes.
7. Day 7: implement one small change based on the feedback.

The bottom line

Constructive feedback at work is a craft, not a personality trait. Give it timely, private, specific and respectful. Receive it with curiosity instead of defence. Build the muscle and you will become the manager people credit for the most growth in their career — and the colleague everyone wants to keep working with.