All skills
Feedback (Giving / Receiving)
Give constructive feedback, receive criticism gracefully, improve continuously
⬢ TIER 3Soft
+$10k-
Salary impact
6 months
Time to learn
Medium
Difficulty
4
Careers
TL;DR
Feedback skills = ability to deliver observations that accelerate growth. At L1, you give compliments and accept criticism without shutting down. At L2, you deliver Situation-Behavior-Impact feedback and actively seek input. At L3, you normalize feedback culture so criticism becomes team reflex, not threat. Built over 6-8 months through practicing radical candor (care personally + challenge directly), reading Stone & Heen's framework on receiving, and running blameless postmortems. Adds $10-30k across all career levels; at senior/manager tiers becomes a hiring requirement because teams without feedback die slowly.
What is Feedback (Giving / Receiving)
Feedback skills = ability to give/receive feedback effectively. Accelerates growth, essential for teams. Boost: +$10k-$30k (growth accelerator)
🔧 TOOLS & ECOSYSTEM
SBI model (Situation-Behavior-Impact) — Center for Creative LeadershipRadical Candor framework — Kim ScottThanks for the Feedback — Stone & Heen (receiving side)Crucial Conversations — Patterson et al.Lattice 1-on-1s + feedback cycles15Five weekly check-ins + peer feedback loopsBlameless postmortems (incident.io, incident.dev)Radical Candor Coach appReal-time feedback loops (Slack async, weekly sync)Growth mindset journaling (Carol Dweck)
📋 Before you start
💰 Salary by region
| Region | Junior | Mid | Senior |
|---|---|---|---|
| USA | $75k | $110k | $155k |
| UK | £45k | £65k | £95k |
| EU | €50k | €70k | €100k |
| CANADA | C$80k | C$115k | C$160k |
🎯 Careers using Feedback (Giving / Receiving)
⚖ Compare with
❓ FAQ
What's the difference between feedback and criticism?
Criticism is judgment ('you're bad at X'). Feedback is observation + impact ('when you skipped the PR review [situation], the bug made it to prod [impact]'). The SBI model trains you to stay observational — you describe what happened, the effect it had, then pause for their response. Criticism makes people defensive; feedback makes them curious. The shift is tiny linguistically (removing 'you always' / 'you never') but massive psychologically.
How do I give feedback to my boss?
Upward feedback is highest-risk because power imbalance makes people defensive. Three moves: (1) Ask permission first ('Can I share something I observed?'). (2) Frame as curiosity, not judgment ('I noticed X — was that intentional?'). (3) Connect to shared outcomes ('I think it'd unblock the team if...'). Best practice: psychological safety first — work on giving downward feedback until you see people actually change, THEN attempt upward. If your boss punishes feedback, you're in a broken system (consider leaving).
How do I receive feedback without getting defensive?
Three steps from Stone & Heen's research: (1) Listen without interrupting — your instinct is to defend. Suppress it. Say 'thanks, I'll think about that.' (2) Separate the feedback from the relationship — 'they said X' ≠ 'they hate me'. (3) Evaluate (not immediately) — later, decide what's useful and what's noise. Most people fail at step 1 (they start rebutting mid-feedback). The pause is the skill.
How do I run a blameless postmortem when someone clearly messed up?
The word 'blameless' doesn't mean 'nobody did anything wrong' — it means 'we're not here to punish, we're here to learn.' Start with: 'What happened?' (facts). 'Why did our systems allow this?' (always a why — training gap, unclear spec, monitoring blind spot). 'What changes prevent recurrence?' Three questions, not 'who messed up?'. The best postmortems find that the person was set up to fail (bad process) — they're usually grateful because it shifts from shame to improvement.
Feedback in async (Slack) vs synchronous (meetings) — which works?
Async works for low-stakes observations ('nice doc structure'). Sync is mandatory for critical feedback because tone is lost in text and they need chance to ask clarifying questions immediately. General rule: if there's risk of being misunderstood, do it live. Async feedback for praise (celebratory + visible), live for correction.
How does Radical Candor differ from just being honest?
Radical Candor = care personally + challenge directly. Being honest without caring feels like an attack. Caring without challenging feels like coddling. You need both. 'Your code is garbage' (honest, zero care) destroys people. 'You're doing great!' (caring, zero challenge) leaves them stuck. 'I care about your growth — here's where you're stuck and here's how we fix it' is Radical Candor. It's about intention + delivery.
What if someone doesn't want feedback? Can I force it?
No — forced feedback is just venting. If someone shuts down, stop. Return when trust is higher. Best practice: ask before giving. 'Can I share something I noticed?' opens the door. If they say no, respect it. Then work on rebuilding trust — ask them what kind of feedback helps them. Over time, people who feel genuinely cared for become feedback-hungry.
Not sure this skill is for you?
Take a 10-min Career Match — we'll suggest the right tracks.
Find my best-fit skills →Find your ideal career path
Skill-based matching across 2,536 careers. Free, ~10 minutes.
Take Career Match — free →