Giving & Receiving Feedback

Key Dimensions

Dimension	Effective Feedback	Ineffective Feedback
Specificity	“In the retro on Tuesday, you talked over Alex twice”	“You need to listen more”
Timeliness	Within 48 hours of the behavior	Months later in a performance review
Intent	Help them grow	Prove you’re right, vent frustration
Balance	Both reinforcing and redirecting, weighted toward reinforcing	Only negative, or only positive (false kindness)
Ownership	“I noticed…” / “The impact was…”	“Everyone thinks…” / “People are saying…”
Follow-up	Check in later: “How did that conversation go?”	Deliver and forget

The SBI Model (Situation-Behavior-Impact)

Developed by the Center for Creative Leadership. The most reliable framework for delivering feedback that lands without triggering defensiveness.

The components:

Situation: Ground the feedback in a specific time and place. This prevents the recipient from feeling like you’re making a global judgment about their character.

• “In yesterday’s sprint planning…” (not “You always…”)
• “During the incident on Friday night…” (not “Whenever there’s an incident…”)

Behavior: Describe the observable behavior — what you saw or heard, not what you inferred about their intent.

• “You closed your laptop and started scrolling your phone during the presentation” (observable)
• NOT “You were disrespectful” (interpretation)
• “You shipped the feature without running the integration tests” (fact)
• NOT “You were careless” (judgment)

Impact: Explain the effect of the behavior — on you, the team, the project, or the person themselves.

• “The presenter noticed and lost confidence for the rest of the session, which meant we didn’t get good input on the design”
• “The broken integration caused 3 hours of downtime and the on-call engineer spent their evening debugging”

SBI-I: Adding Inquiry

The best version of SBI adds a fourth element: Inquiry — asking for their perspective.

• “I’m curious — what was going on for you in that moment?”
• “Is there context I’m missing?”
• “How do you see it?”

This does three things: (1) you might learn something that changes your interpretation, (2) it signals respect for their perspective, (3) it shifts from one-way delivery to a conversation.

When SBI fails:

SBI is mechanical. For deep interpersonal issues, the formula can feel clinical. If someone is dealing with a trust violation, a values conflict, or a pattern that’s been discussed multiple times, SBI alone won’t cut it. You need to move to a more direct conversation: “We’ve talked about this before. The pattern is continuing. I need to understand what’s making it hard to change.”

Radical Candor (Kim Scott)

The 2x2 framework that captures the two axes of effective feedback:

            Care Personally
                 HIGH
                  |
  Ruinous         |      Radical
  Empathy         |      Candor
  (kind but       |      (caring AND
   not honest)    |       honest)
------------------+-------------------
  Manipulative    |      Obnoxious
  Insincerity     |      Aggression
  (neither kind   |      (honest but
   nor honest)    |       doesn't care)
                  |
                 LOW
           Challenge Directly →
        LOW                    HIGH

The four quadrants:

Radical Candor (top right): You care about the person AND you tell them the truth. This is the goal. “I care about your career, and that’s why I need to tell you that your communication in cross-team meetings is holding you back from the Staff promotion.”

Ruinous Empathy (top left): You care about them but avoid telling them hard truths. This is the most common failure mode for managers. You think you’re being kind, but you’re actually depriving them of information they need to grow. “Everything’s great!” while privately thinking they’re underperforming.

Obnoxious Aggression (bottom right): You tell the truth but without caring about how it lands. “That presentation was terrible.” Occasionally effective in crisis, but sustainable only in very specific cultures (and even then, it’s often just bullying rationalized as “honesty”).

Manipulative Insincerity (bottom left): You don’t care and you’re not honest. Political behavior, passive aggression, talking behind people’s backs. Toxic and unfortunately common in large organizations.

The key insight:

Most managers who think they’re being Radically Candid are actually in Ruinous Empathy. The bar for “challenging directly” is higher than you think. If giving the feedback doesn’t make you at least slightly uncomfortable, you’re probably softening it too much.

How to move toward Radical Candor:

1. Start with small things — give direct feedback on a low-stakes issue first. “That email could have been half as long and twice as clear.” Build the muscle.
2. Give more positive feedback with specificity — “Your API design doc was excellent — specifically, the way you mapped failure modes to recovery strategies showed real system thinking.” This builds the caring-personally foundation.
3. Ask for feedback first — “What’s one thing I could do differently?” When you receive direct feedback gracefully, it normalizes the behavior.
4. Name the awkwardness — “This is uncomfortable to say, but I care about your growth and I think you need to hear this.”

Feedforward (Marshall Goldsmith)

Feedforward is an alternative to traditional feedback that focuses on future behavior rather than past mistakes. Goldsmith’s argument: people can’t change the past, and dwelling on past failures triggers defensiveness. Instead, ask: “What could you do differently next time?”

When feedforward is better than feedback:

• The person already knows they messed up (no need to rub it in)
• The relationship is new and trust isn’t established yet
• The person tends to be defensive (feedforward is less threatening)
• You want to coach rather than evaluate

When feedback is necessary (feedforward isn’t enough):

• The person doesn’t see the pattern — they need specific examples
• There’s a compliance or ethical issue — you can’t be indirect
• The behavior has been discussed before and hasn’t changed — you need to escalate directness
• You’re documenting for performance management purposes

In practice, blend both:

“In yesterday’s meeting, you presented the architecture without mentioning the security implications [SBI — past behavior]. For the board presentation next week, I’d suggest leading with the risk analysis before the proposed solution [feedforward — future suggestion]. What do you think?”

Frequency — The Most Underrated Dimension

The research:

Gallup found that employees who receive feedback at least weekly are 3.6x more likely to be engaged than those who receive feedback annually. Not 36% more — 360% more. The implication: your feedback cadence matters more than your feedback quality.

Why frequent, small feedback beats infrequent, formal feedback:

1. Lower stakes per interaction — “Hey, quick thought on your PR comment” is easy. An annual review is loaded with emotional weight.
2. Faster course correction — a small behavioral adjustment in week 2 prevents a pattern that requires a PIP in month 6.
3. Recency — feedback on something that happened yesterday is specific and credible. Feedback on something from 4 months ago feels like an ambush.
4. Normalization — when feedback is constant, it becomes part of the culture. No one dreads “the feedback conversation” because every conversation includes feedback.

The 5:1 ratio (Gottman/Losada):

Research on high-performing teams (and stable marriages) suggests a ratio of approximately 5 positive interactions for every 1 negative interaction. Below 3:1, relationships deteriorate. Above 13:1, feedback loses credibility (everything’s praise, nothing’s actionable).

The practical implication: If you’re giving someone redirecting feedback once a week, you should be giving specific positive feedback 5 times a week. Not “good job” — specific: “The way you handled the customer escalation this morning was exactly right — you de-escalated first, then addressed the technical issue.”

Creating a Feedback Culture

The manager’s role:

You can’t mandate a feedback culture. You model it. The three behaviors that create feedback culture:

1. Publicly ask for feedback on yourself — in a team meeting: “What’s one thing I should do differently?” Then act on what you hear. If you get defensive, you just killed the culture.

2. Give feedback in real-time — when you see a good code review comment, say “Great catch on the race condition — that level of review rigor is what we need.” When you see a problem, address it within 24 hours.

3. Celebrate feedback-giving — when someone gives good feedback to a peer, acknowledge it: “I noticed you gave [person] really specific feedback on their system design. That’s the kind of directness that makes us better.”

Peer feedback mechanisms:

Mechanism	When to Use	Risk
Real-time in Slack/PR comments	Small, specific technical feedback	Can feel like public criticism
1:1 peer feedback	Interpersonal or behavioral feedback	People avoid it — needs manager encouragement
360 reviews	Comprehensive development feedback	Becomes political, people game the system
Retro feedback	Process and team dynamics	Stays surface-level without facilitation
Feedback Friday (structured)	Weekly habit-building	Feels forced, peters out without reinforcement

The 360 review trap:

360 reviews can be powerful or destructive. Common failure modes:

• Too many people — 15 reviewers means generic feedback. Limit to 5-7 who actually work with the person.
• No anonymity calibration — fully anonymous invites score-settling. Attributed feedback invites retaliation. The middle ground: feedback is attributed to the manager but the specific source is not shared.
• No coaching on how to write 360 feedback — untrained reviewers write “they’re great” or weaponize the process.

Handling Defensiveness

When someone gets defensive, your natural instinct is to push harder with more evidence. This almost always backfires.

Why people get defensive:

• Identity threat — the feedback challenges their self-image (“I’m a strong engineer” vs. “your code quality needs improvement”)
• Surprise — they didn’t see it coming (your fault — see “no surprises” principle)
• Lack of trust — they don’t believe you have their best interest at heart
• Poor delivery — the feedback was vague, judgmental, or public
• They disagree — sometimes the defensiveness is legitimate because you’re wrong

What to do when someone gets defensive:

1. Pause, don’t escalate — “I can see this is landing hard. Let’s take a step back.”
2. Acknowledge their experience — “It sounds like you see this differently. I want to understand your perspective.”
3. Separate intent from impact — “I don’t doubt your intent. I’m talking about the impact.”
4. Offer time — “I don’t need your response right now. Take a day to sit with this and let’s talk again.”
5. If they shut down completely — end the conversation gracefully and revisit later. Forcing it when someone is in fight-or-flight is pointless.

When YOU get defensive:

If a direct report gives you tough feedback and you feel your defensiveness rising:

1. Thank them immediately — “Thank you for telling me this. I know it wasn’t easy.”
2. Don’t explain or justify — just listen
3. Ask for specifics if needed — “Can you give me a recent example?”
4. Follow up later — “I’ve been thinking about what you said about [X]. Here’s what I’m going to do differently.”

The moment you defend yourself, you’ve taught your team that giving you feedback is painful. They won’t do it again.

Feedback in Specific Situations

Feedback to senior/experienced people:

Senior people are harder to give feedback to because (1) they may know more than you in their domain, (2) they’re used to being the authority, (3) the power dynamic is complicated when you’re managing someone with more technical depth.

What works: Frame feedback in terms of impact at their level. “Your technical approach is sound — the gap I’m seeing is in how you bring others along. At the Staff level, influence matters as much as correctness. In Tuesday’s review, you had the right answer but delivered it in a way that shut down discussion.”

Feedback across cultures:

Different cultures have different feedback norms. In German culture, direct feedback is the norm and indirectness is seen as dishonest. In many East Asian cultures, direct negative feedback (especially in public) causes face-loss and should be delivered privately through indirect signals. In the US, the “praise sandwich” is common but often transparent.

For a manager in Germany leading a multicultural team: Default to direct, private feedback (respects German norms while being culturally safe). In 1:1s, explicitly ask: “How do you prefer to receive feedback? Some people want it very direct, others prefer more context first.” Calibrate per person.

Feedback to your manager (managing up):

See Managing Up & Stakeholder Relationships for detail. The key principle: frame feedback in terms of outcomes, not feelings. “When priorities shift weekly, I spend 30% of my time re-planning instead of building. Could we establish a quarterly priority lock?” is more effective than “It’s frustrating when you keep changing priorities.”

Common Feedback Anti-Patterns

Anti-Pattern	What It Sounds Like	Why It Fails	Better Alternative
The praise sandwich	“Great job on X. But you need to improve Y. But overall, great!”	People learn to tune out the praise, waiting for the “but”	Give positive and critical feedback separately
The proxy	“Some people have mentioned that…”	Strips accountability, creates paranoia	Own the feedback: “I’ve observed…”
The drive-by	Dropping critical feedback in passing	Signals it’s not important enough for a real conversation	Schedule dedicated time
The annual dump	12 months of feedback in one review	Overwhelming, unfair, too late to act on	Weekly micro-feedback
The comparison	“Why can’t you be more like [person]?”	Humiliating, breeds resentment	Compare to the rubric, not to a peer
The label	“You’re not a leader”	Unfalsifiable, attacks identity	“In these 3 situations, here’s what I observed…”
The interrogation	“Why did you do that? What were you thinking?”	Triggers defensiveness immediately	“Walk me through your thinking on this”
Positive-only	Never giving critical feedback	Person has no idea where to grow, blindsided at review time	Pair reinforcing feedback with one growth edge

The Feedback Flywheel

When feedback culture is working, it creates a reinforcing loop:

Manager models feedback
         ↓
Team sees it's safe to give feedback
         ↓
Team members give each other feedback
         ↓
Quality improves, trust deepens
         ↓
More feedback is given (and received) naturally
         ↓
Manager has to intervene less
         ↓
Team becomes self-correcting

The time investment is front-loaded. The first 3-6 months of building a feedback culture require constant modeling and reinforcement. After that, the team maintains it with less managerial effort.

References

Books

• Radical Candor — Kim Scott (the definitive framework for caring + challenging)
• Thanks for the Feedback — Stone & Heen (the receiving side — essential complement to Radical Candor)
• Crucial Conversations — Patterson, Grenny, McMillan, Switzler (high-stakes feedback conversations)
• The Culture Map — Erin Meyer (cultural dimensions of feedback — essential for multicultural teams)
• What Got You Here Won’t Get You There — Marshall Goldsmith (feedforward model)
• Nonviolent Communication — Marshall Rosenberg (the observation-feeling-need-request model)
• The Coaching Habit — Michael Bungay Stanier (asking instead of telling)

Research & Articles

• Center for Creative Leadership — SBI model (original research)
• Gallup — weekly feedback and engagement correlation
• Losada & Heaphy (2004) — “The Role of Positivity and Connectivity in the Performance of Business Teams” (the positivity ratio)
• Google re:Work — “Give Feedback” guide (practical, open-source)
• Lara Hogan — “Feedback Equation” (blog post, concise framework)

Talks

• Kim Scott — “Radical Candor” (multiple talks, the book launch talk is the most concise)
• Sheila Heen — “How to Use Others’ Feedback to Learn and Grow” (TEDx, the receiving perspective)
• Brene Brown — “The Power of Vulnerability” (TED, foundational for why feedback requires trust)