Giving difficult feedback at C1 — SBI, COIN, radical candor, and receiving feedback gracefully

Feedback at B2 was about the sandwich: positive open, constructive middle, forward-looking close. At C1, the stakes go up — you may be giving career-altering feedback to a direct report, telling a peer their work is damaging the team, calling out a senior leader’s behavior, or receiving feedback about your own performance from someone who outranks you. The B2 sandwich, useful as it is for routine feedback, starts to feel either too soft (the message gets lost) or formulaic (the recipient sees the structure and tunes out).

C1 feedback culture in the US is shaped by a constellation of frameworks — SBI (Situation-Behavior-Impact), COIN (Context-Observation-Impact-Next), Radical Candor (Kim Scott), Nonviolent Communication (Marshall Rosenberg), and the “feedback is a gift” ethos popularized at Netflix and Bridgewater. You don’t need to be a religious adherent of any one framework, but you need fluency with the vocabulary and patterns, because they saturate modern US professional language. Can I give you some feedback? / This is observational, not evaluative / I’m flagging a pattern / I want to share an impact that may not be visible to you — these are C1 feedback phrases that signal you operate at the modern American professional level.

This lesson covers giving difficult feedback (using SBI and COIN), the radical candor frame, opt-in phrasing for high-stakes feedback, sandwiching tradeoffs at the C1 level, and — equally important — receiving feedback gracefully.

Opt-in phrasing — earning permission first

C1 feedback opens with permission. Unsolicited feedback, even when accurate, often misses because the recipient is defensive before the first word. Opt-in phrasing changes the dynamic.

Standard opt-in openers

• I have some feedback. Is now a good time?
• Mind if I share an observation?
• Open to some feedback on the [meeting / pitch / draft]?
• Can I give you some honest feedback? I’ve been sitting on it for a couple of days.
• I have a piece of feedback I’d like to share — it’s not urgent, but I want to find a moment.

Opting in for harder feedback

• I have some feedback that I think is important. I’d like to find a time when we can both sit with it.
• There’s something I want to flag, and I want to do it well, so I’d like 20 minutes when you have it.
• I want to share some critical feedback. Tell me when works.

Asking for feedback yourself (modeling)

• I’d love some critical feedback on how I handled the meeting today.
• What’s one thing I could have done better?
• Push me — where am I weak on this?

SBI — Situation, Behavior, Impact

SBI (developed at the Center for Creative Leadership) is the most widely used feedback framework in US corporate environments. The structure: name the situation (when and where), describe the specific behavior (what they did, observationally), state the impact (what happened as a result).

Situation

Anchor in time and place. No vague you always or you never.

• In yesterday’s product review meeting…
• During the Q3 planning offsite, in the Wednesday session…
• On the all-hands Slack thread on Tuesday…

Behavior (observational, not evaluative)

What you saw or heard. Not what you inferred about motivation.

• …you interrupted Maria three times in the span of ten minutes.
• …you raised your voice when the data was challenged.
• …you committed to a delivery date without checking with engineering.

Impact

The effect, observed or experienced.

• …the impact was that Maria stopped contributing for the rest of the meeting and two other people I spoke to noticed.
• …the team read it as you not being open to pushback, and the conversation closed down.
• …engineering is now scrambling to meet a date they didn’t sign up for, and trust between us is taking a hit.

Full SBI example

In yesterday’s product review (situation), you interrupted Maria three times in the span of about ten minutes (behavior). What I observed was Maria stopped contributing for the rest of the meeting, and two other folks mentioned it to me afterward (impact).

COIN — Context, Observation, Impact, Next

COIN extends SBI with a forward-looking step. Common in US management training.

• Context: the situation
• Observation: the specific behavior
• Impact: the effect
• Next: what would change going forward

The Next step language

• Going forward, what I’d love to see is…
• Next time, what might help is…
• The change I’d want for the next round: …
• Here’s the experiment I’d love you to try: …

Full COIN example

In the product review yesterday (context), I noticed you interrupted Maria three times in about ten minutes (observation). Maria stopped contributing and two other folks flagged it to me afterward (impact). For the next session, what I’d love to see is you holding your responses until each person finishes — even when you disagree mid-sentence. Want to try that this week and check in afterward? (next)

Radical candor — care personally, challenge directly

Kim Scott’s framework (Radical Candor, 2017) is now woven into US management vocabulary. The two-axis frame: caring personally is the vertical axis, challenging directly is the horizontal axis. Radical candor is high on both.

The four quadrants and the phrases that distinguish them:

Radical candor opening phrases

• I care about you and your trajectory here, and that’s why I’m going to be direct.
• I’d rather give you the hard version now than have you find out the soft version in a perf review.
• This is going to land hard. I’m telling you because I think you can handle it and use it.
• I’d rather risk this conversation than let you keep going on this path.

Resisting ruinous empathy

• I owe you the honest version of this, even though the easy version would be to say it’s fine.
• Telling you it’s good would be doing you a disservice.
• I’d be a bad [manager / colleague / friend] if I let this slide.

Sandwiching tradeoffs at C1

The classic B2 feedback sandwich (positive-constructive-positive) is fine for routine moments. At C1, sandwiching gets more sophisticated — you’re sandwiching tradeoffs, not pure positives and negatives. The structure: name what’s working, name the tradeoff that’s costing you something, propose a different tradeoff.

Naming what’s working

• The strength here is X — that’s real and I don’t want to lose it.
• What I love about your approach is X.
• Where you’re shining is Y.

Naming the tradeoff

• Where this is starting to cost is…
• The price of that strength is that…
• The flip side of [strength] showing up is that [cost] is showing up too.

Proposing a rebalance

• What I’d love to see is the strength preserved, with the cost dialed down — here’s how I’d think about it…
• Can we keep [strength] and adjust [behavior that’s costing]?
• The goal isn’t to lose [strength] — it’s to soften [cost].

Example sandwich

The thing you’re doing brilliantly is challenging assumptions early in meetings — it has improved the quality of our decisions in a real way, and I want to be explicit that I value it. (Strength.) Where it’s starting to cost is that on three occasions in the last month, the challenge has come at a moment when a more junior person was just starting to share, and they stopped sharing. (Tradeoff.) What I’d love is the same intellectual challenge, with a beat of patience for the more junior voices to land their point first. Same skill, slightly later in the sequence. (Rebalance.)

High-stakes feedback patterns

Beyond the frameworks, C1 American feedback has a few standard patterns for specific high-stakes situations.

Pattern flagging

• I want to flag a pattern I’m seeing.
• This is the third time something like this has happened — I think it’s worth naming.
• I’m noticing a thread across [situations], and I want to surface it.

Performance-improvement framing

• I want to be clear about where I see your performance and what would need to change.
• I’m having this conversation now because I’d rather have it now than in three months when the options narrow.
• Here’s what I need to see in the next 60 days.

Career-impact framing

• This isn’t a small thing — it’s affecting how senior people see your trajectory.
• I want to be candid: this is starting to shape your reputation in ways I don’t think you’d want.
• I’d rather you hear this from me than learn it indirectly later.

Boundary-setting feedback

• I want to share something that’s not negotiable for me: …
• This isn’t a preference — it’s a line I need us to hold.
• I need this to change. Let me explain why.

Receiving feedback gracefully — the C1 stance

How you receive feedback is itself feedback to the person giving it. Receiving badly trains people to stop giving. Receiving well makes you someone people invest in.

Opening posture

• Thank you for the feedback — I want to make sure I’m hearing it well.
• I appreciate you bringing this to me directly.
• Let me sit with that for a second before I respond.

Asking for specifics

• Can you give me a specific example?
• Help me see exactly what you saw — I want to understand the behavior.
• What did it look like from your side?

Acknowledging the impact

• I can see how that landed, and I’m sorry it did.
• I hadn’t seen it from that angle. Thank you for surfacing it.
• The impact you’re describing is real, and I want to own it.

Avoiding defensiveness

• I want to resist the urge to explain that away, and just take it in.
• Let me not react to that right now. Can I come back to you tomorrow with a better response?
• I might disagree with parts of this, but I want to start by taking it seriously.

Closing well

• Here’s what I’m going to do with it: …
• Can we check in on this in two weeks?
• Thank you. This is the kind of feedback that’s hard to give and hard to hear — I appreciate you doing it.

Mini-dialogues

Dialogue 1: SBI feedback to a peer

You: Hey, do you have ten minutes? I have some feedback I want to share. Peer: Sure, now’s fine. You: Thanks. In yesterday’s planning meeting, when Maria proposed the Q4 framing, you cut in before she finished and pivoted the discussion to your Q3 critique. (situation + behavior, observational) What I saw afterward was Maria didn’t speak again for the rest of the meeting, and I had two side-conversations from people on the team who picked up on it. (impact) I wanted to flag it because I don’t think it represents how you usually show up, and I think the cost — if it becomes a pattern — would be Maria pulling back from the bigger conversations. (care + concern about pattern) Peer: I didn’t realize. I was excited about the Q3 angle. I owe her an apology. You: I think that’d land well.

Dialogue 2: difficult feedback to a direct report (radical candor)

You: I want to give you some honest feedback. I care about you and your trajectory at this company, and that’s why I’m going to be direct. Report: OK. You: The presentation to the leadership team last week didn’t land. (direct claim) I want to be specific about what I observed: the deck opened with a long methodology section before the recommendation, the executives had drifted by slide 8, and the Q&A surfaced three questions you weren’t prepared for on the customer data. (specifics — behavior level) The impact is that the leadership team is now hesitant on the project, and I’m being asked to reset the executive narrative myself. (impact) Here’s what I’d want to see next time: recommendation up front, three slides of supporting evidence, a Q&A prep doc covering the top five expected questions. I’m happy to work through that with you. (next + offer of support) This is going to feel hard, and I want to be honest with you that this is the kind of feedback that, if I sandwiched it, you’d hear as small. It’s not small. We have one more shot to reset the narrative on this project, and I need your prep on the next one to be different. Report: That’s a lot to take in. Can I come back to you tomorrow? You: Absolutely. Sit with it. We’ll talk tomorrow.

Dialogue 3: receiving feedback well

Manager: I have some feedback. Is now a good time? You: Yes, please. Manager: In the Sales QBR last Thursday, when the VP of Sales challenged your numbers, you got defensive and the room felt the energy shift. Two people commented on it afterward. You: Thank you for telling me. (open) Can you tell me what defensive looked like from your side? I want to make sure I’m seeing what you saw. (ask for specifics) Manager: Your tone got clipped, you started cutting him off mid-sentence, and you used the phrase “with respect” twice in a way that read as sarcastic. You: I can see how that landed. (acknowledge impact) I want to resist the urge to explain it away in the moment. Let me sit with it tonight and come back tomorrow with how I want to handle it differently next QBR. (don’t justify) I appreciate you bringing it to me directly. (close)

Phrase bank — feedback at C1

AmE-specific functional language

• Radical candor — Kim Scott’s framework, near-mandatory vocabulary in US management.
• Drop the ball — informal admission of a missed responsibility.
• That landed hard / didn’t land — describes how feedback or a message was received; AmE business.
• Sit with it — pause to process before responding; AmE.
• Take it in — receive feedback non-defensively.
• Check in — follow up after an agreed period; AmE corporate.
• Skip-level — feedback that travels two management levels up or down.
• Real-time feedback / in the moment — feedback given immediately rather than saved for review.
• Net-promoter feedback / 360 feedback — both AmE corporate vocabulary.

BrE often prefers raise / point out / mention where AmE uses flag. Push back, lean in, sit with it are AmE-dominant in feedback contexts.

Cultural notes

US feedback culture has shifted dramatically in the last decade — driven by Netflix’s “candor” ethos, Bridgewater’s radical transparency, Kim Scott’s book, and the broader management self-help canon. Modern US workplaces increasingly expect:

• Direct feedback delivered with care — both directness and care, not one without the other.
• Real-time feedback over saved-up feedback — feedback within 24-48 hours of the behavior is the standard; feedback saved for the annual review is increasingly seen as failure of management.
• Receiving feedback gracefully as a professional skill — defensiveness, even when justified, is read as a maturity issue.
• Permission and consent in feedback — opt-in phrasing, agreed channels, agreed cadences.

Russian-speaker traps include: avoiding feedback to preserve relationship (reads as ruinous empathy), giving feedback as judgment rather than observation (reads as obnoxious aggression), receiving feedback by justifying (reads as not coachable), and not modeling feedback-seeking behavior (which signals you’re not a peer in modern American management culture).

Common Russian-speaker mistakes

1. Skipping the opt-in — launching into feedback unannounced. The American C1 norm is to ask for permission first. I have some feedback. Is now a good time? This is not optional formality — it’s signal that the feedback is important enough to deserve framing.
2. Inferring motivation instead of describing behavior — You were being dismissive invites argument; You interrupted three times doesn’t. Stay on the observable.
3. Sandwiching too aggressively — burying the message between two positives so heavily that the recipient misses it. American sandwiching at C1 is about preserving honesty within softening, not hiding the message.
4. Importing Russian directness without American care framing — Your draft is bad, fix it is technically clear feedback; in US contexts it reads as obnoxious aggression and burns the relationship. Add the care: I want you to do well, and that’s why I’m being direct.
5. Receiving feedback by explaining or justifying — even when the explanation is correct, justifying in the moment reads as defensive. Let me sit with it, can I come back to you tomorrow? is the C1 stance.
6. Treating feedback as judgment, not observation — You’re not a good communicator (judgment) vs In yesterday’s meeting, the team read your message as harsh (observation). C1 feedback stays close to the observable.
7. Not modeling feedback-seeking — In American C1 cultures, what’s one thing I could do better? is a peer-level move. Senior people who never ask for feedback are read as defensive. Asking models the behavior.

Summary

• Opt in first: I have some feedback. Is now a good time? Permission protects the message.
• SBI: Situation, Behavior (observational), Impact. Anchor in time, stay observational, name the impact.
• COIN: SBI + Next. Add the forward-looking ask.
• Radical candor: high care + high challenge. Both, not one.
• Sandwich tradeoffs, not pure positives — at C1 you’re rebalancing strengths and costs, not coating bad news in sugar.
• Pattern flagging, career impact, performance framing — known C1 patterns for high-stakes feedback.
• Receive gracefully: thank, ask for specifics, sit with it, don’t defend in the moment.
• Avoid: skipping opt-in, inferring motivation, sandwiching to invisibility, defensiveness in receipt, judgment instead of observation.

Next lesson: Handling conflict and de-escalation — naming, validating, and proposing a path forward.