Give Developmental Feedback

---
name: give-developmental-feedback
description: Use when a manager needs to deliver specific, in-the-moment developmental feedback to a direct report — separate from a formal performance review — to improve a behavior or reinforce a strength using observable evidence.
source: SBI feedback model (Center for Creative Leadership, CCL); Kim Scott "Radical Candor" (2017); Gallup "State of the American Workplace" (2017); Netflix Culture Deck
tags: [feedback, developmental-feedback, sbi, manager, coaching, performance, direct-report, behavioral-feedback]
---

# Give Developmental Feedback

Deliver specific, behavior-grounded feedback using the Situation-Behavior-Impact (SBI) model so the recipient can act on it immediately without becoming defensive.

## Why This Is Best Practice

**Adopted by:** The CCL's SBI model is licensed to 750+ organizations globally including Google, Meta, Microsoft, and Cisco; Kim Scott's Radical Candor framework — built on the same behavioral-specificity principles — is used at Apple, Twitter, and Dropbox; Netflix's culture deck mandates candid, real-time peer and manager feedback as a non-negotiable operating principle across the entire organization
**Impact:** Gallup's 2017 research (State of the American Workplace, 195k respondents) found employees who receive regular meaningful feedback are 3.6× more likely to be engaged than those who don't; CCL research documents that behavior-focused feedback using SBI reduces defensive reactions by 40–60% compared to judgment-framed feedback, because recipients can accept a description of behavior without feeling their identity is under attack; managers who give feedback in the moment — not batched into quarterly reviews — improve behavior correction speed by 8–12 weeks
**Why best:** Vague feedback ("be more proactive", "good work") produces no behavior change because recipients cannot identify what to repeat or stop; annual performance review feedback arrives months after the event, making behavioral course-correction practically impossible; SBI grounds every piece of feedback in an observable event that both parties can agree happened, removing the subjectivity that makes feedback feel unfair

Sources: Center for Creative Leadership "Feedback That Works: How to Build and Deliver Your Message" (CCL Press, 2nd ed. 2014); Kim Scott "Radical Candor" (St. Martin's Press, 2017); Gallup "State of the American Workplace" (2017); Netflix "Culture" (culture.netflix.com)

## Steps

### 1. Choose the right moment

Deliver feedback within 24–48 hours of the observed behavior. Beyond 48 hours, behavioral specificity degrades and the feedback feels retrospective rather than developmental.

**Timing rules:**
- Corrective feedback: always in private — never in group settings, channels, or in front of peers
- Positive reinforcement: public delivery is acceptable and often amplifies impact
- Never deliver corrective feedback immediately after a high-stress event — wait for both parties to be calm

If the situation doesn't allow for immediate private conversation, schedule it explicitly: "I'd like 10 minutes with you before end of day — is 4pm OK?"

### 2. State the Situation

Describe the specific context — meeting, project, interaction — so the recipient immediately knows what you're referring to. Be concrete, not general.

```
✅ "In this morning's client call with Acme at 10am..."
✅ "On the code review you submitted for the auth module yesterday..."
❌ "Lately when you're in meetings..."
❌ "Sometimes you tend to..."
```

The Situation sets shared context. Without it, the recipient has to guess which event you're referring to — which creates immediate uncertainty and defensiveness.

### 3. Describe the Behavior

State only what you observed — a specific, visible action or utterance. This is the most important step and the most commonly failed.

**Behavior is:**
- Observable: another person in the room would have seen or heard the same thing
- Factual: can be stated without inference about intent or character
- Specific: references the exact action, not a generalization

```
✅ "You interrupted the client three times before they finished their sentence."
✅ "You presented the data without the confidence intervals we discussed."
✅ "You said 'that's a great idea' and immediately moved on without recording it."

❌ "You were dismissive." (interpretation, not behavior)
❌ "You don't respect other people's time." (character judgment)
❌ "You always do this." (generalization — never use "always" or "never")
```

### 4. Describe the Impact

State the effect the behavior had — on you, the team, the customer, or the work. Use first-person language. The impact is what makes feedback matter to the recipient.

```
✅ "I noticed the client stopped contributing for the rest of the call."
✅ "The team wasn't able to assess the risk of the recommendation without those numbers."
✅ "I was left uncertain whether their idea was captured for follow-up."
```

Do not claim certainty about how others felt — report what you observed or experienced:

```
❌ "The client felt disrespected." (you don't know what they felt)
✅ "The client went quiet for the rest of the call." (you observed this)
```

### 5. For corrective feedback: ask before prescribing

After stating the SBI, resist the urge to tell the recipient what to do differently. Ask first:

```
"What are your thoughts on that?"
"What would you do differently if that situation came up again?"
"What was going on for you in that moment?"
```

This surfaces the recipient's perspective (they may have context you don't), increases ownership of any behavior change, and transforms the conversation from a one-way critique into a dialogue.

If their answer reflects the desired change, affirm it. If not, add your suggestion: "Here's what I'd suggest: [specific behavior]."

### 6. Agree on a specific next behavior

Close the feedback loop with a concrete, observable commitment — not a vague goal.

```
❌ "Let's work on your listening skills." (too vague — no observable behavior)
✅ "In the next client call, will you let them finish their thought before responding?"
```

The agreed behavior should be observable by both of you in the next occurrence of a similar situation. If no natural next occurrence is coming up, create one: "You'll have another chance in the Thursday call — let's debrief briefly after."

### 7. Follow up

Within two weeks of the feedback conversation, observe whether the behavior changed and close the loop:

- **If it changed:** acknowledge it specifically — "In Thursday's call I noticed you waited for the client to finish — that made a real difference."
- **If it didn't change:** return to the conversation — "We talked about X last week. I didn't see it yet in Thursday's meeting. Let's talk about what's getting in the way."

Not following up signals that the feedback wasn't real — which trains the recipient to discount future feedback.

## Rules

- One behavior per feedback conversation — addressing multiple behaviors in one session dilutes all of them and overwhelms the recipient
- Never use "always" or "never" — universals are almost always factually wrong and always trigger defensiveness
- Corrective feedback in private; positive reinforcement can be public
- Behavior, not personality — "you interrupted" not "you're inconsiderate"; "you didn't include the data" not "you're careless"
- Do not batch feedback for quarterly delivery — the behavioral window is 48 hours; beyond that, correct it immediately or don't raise it

## Common Mistakes

- **"You always..." or "You never..."** — factually inaccurate and impossible for the recipient to accept; they will spend the conversation finding the exception, not hearing the feedback.
- **Bundling multiple behaviors** — "In that meeting you interrupted the client, the presentation was unclear, and you were late sending the deck" — recipient cannot process or prioritize; pick the most important one.
- **Leading with intent** — "I know you didn't mean to..." softens the impact so much that the recipient doesn't register a behavior change is needed.
- **Skipping the follow-up** — feedback without follow-up teaches the recipient that nothing really changes after a feedback conversation, eroding trust in future feedback.
- **Private praise only** — positive feedback that only happens in private misses the motivational impact of public recognition; meaningful work recognized in front of peers has outsized engagement effects.
- **Using feedback as a performance review proxy** — if the feedback conversation begins with "I need to tell you this before your review..." the recipient hears evaluation, not development; keep developmental feedback entirely separate from formal evaluation cycles.

## When NOT to Use

- During or immediately after a high-emotion event (argument, near-miss, difficult client escalation) — the recipient is not in a state to process behavioral feedback; wait for both parties to be calm.
- When the behavior stems from a systemic issue, not a personal one — if the same behavior is appearing across multiple people, the root cause is a broken process or unclear expectation, not an individual behavior to correct.
- As a substitute for a Performance Improvement Plan when a pattern of underperformance has already been documented — once behavior is chronic and documented, the appropriate mechanism is a structured PIP, not in-the-moment feedback.