CEDAR & COIN

CEDAR (Context-Emotion-Describe-Ask-Receive) and COIN (Context-Observation-Impact-Next Steps) are two feedback frameworks that extend SBI in different directions. CEDAR explicitly handles the emotional dynamics of feedback conversations — it treats emotion as a first-class part of the framework, not a side effect to be avoided. COIN keeps the SBI rigor and adds an explicit Next Steps phase so the conversation closes with commitment, not just insight.

Origin

CEDAR — Emerged from executive coaching practice in the 2000s, notably in the work of Anna Wildman and the International Coach Federation (ICF) community. It was a reaction to the observation that managers trained in SBI often delivered the content cleanly but fumbled the emotional reaction — either ignoring it or getting thrown by it. CEDAR makes emotional awareness part of the procedure.
COIN — Popularized in corporate coaching and used heavily in tech-company management training (e.g., Atlassian, Microsoft, various L&D curricula). It is designed to keep feedback conversations from becoming unresolved — the Next Steps phase makes commitment explicit.

Both are variations on the same underlying insight: SBI is excellent but insufficient on its own. Real conversations have emotional dynamics and need closure.

The Frameworks

CEDAR

C - Context:   Set the scene; why now, why this conversation
E - Emotion:   Acknowledge your emotion and invite theirs
D - Describe:  Describe the behavior and its impact (this is SBI)
A - Ask:       Ask them what they'll do differently
R - Receive:   Actively listen to their response; do not rebut

CEDAR is especially useful when the conversation has a high emotional charge — when something has gone wrong, trust is shaky, or the relationship matters more than the immediate issue.

COIN

C - Context:      The specific situation or moment
O - Observation:  The specific behavior observed (not inferred)
I - Impact:       The effect on you, team, or outcome
N - Next Steps:   What changes from here; concrete, owned

COIN is closer to SBI in structure but adds the explicit closure. Where SBI tells you to deliver the observation and then have a dialogue, COIN tells you not to end the conversation until there is a concrete next step.

How They Relate to SBI

SBI:    S - Situation  B - Behavior      I - Impact
COIN:   C - Context    O - Observation   I - Impact   N - Next Steps
CEDAR:  C - Context    E - Emotion       D - Describe (~SBI)
                                          A - Ask     R - Receive

SBI is the core. COIN adds closure. CEDAR adds emotional holding space. Most practitioners use SBI as their default and switch to CEDAR or COIN when the situation warrants it.

How to Use It

Using CEDAR

1. Context: "I want to talk about yesterday's review. I've been
   thinking about it overnight and I think it's worth a real
   conversation, not a Slack reply."

2. Emotion: "I'll be honest — I was frustrated, and I want to be
   careful not to let that drive this. How are you feeling about it?"

3. Describe (SBI): "Specifically, when you [behavior], what I
   experienced was [impact]."

4. Ask: "What's your read on it? What would you do differently if
   you had that moment again?"

5. Receive: [Listen. Do not immediately counter. Ask follow-ups.
   Let them fully respond before moving on.]

CEDAR works because it explicitly makes room for the emotional temperature of the conversation. Most feedback failures are not content failures — they are emotional-dynamics failures.

Using COIN

1. Context: "In yesterday's 2pm architecture review..."
2. Observation: "...when Priya was presenting the tradeoffs and
   you interrupted her three times..."
3. Impact: "...she stopped contributing, and I noticed I
   self-censored my next question too."
4. Next Steps: "Going forward, can we agree that in reviews we
   only interrupt with direct questions, not counter-arguments,
   until the presenter hits a stopping point? And maybe we take
   a moment next review to let Priya know you value her input?"

The Next Steps make the conversation action-oriented. Without N, the conversation can end with a vague "I hear you" that changes nothing.

Tech & Company Example

A tech lead is giving feedback after a heated design review. Compare the three approaches:

SBI version (tight, observation-focused):

  "Sam, quick feedback on yesterday's review.

   S: In the 2pm review when we were discussing the retry policy,
   B: you said 'that's a dumb idea' after Jamie's proposal,
   I: I noticed Jamie didn't speak for the rest of the meeting
      and asked me afterward if they should be in these reviews."

COIN version (adds explicit next step):

  "[Same as SBI]...

   N: Going forward, can we agree to critique the idea, not the
      person? Something like 'I see tradeoffs there — can we walk
      through cost?' keeps the review productive. Also, I'd ask
      you to ping Jamie and clarify your intent — I don't think
      you meant what it sounded like, but the effect is real."

CEDAR version (when trust is shaky or emotions are high):

  C: "Sam, I want to talk about yesterday's review. I've been sitting
     with it and I think a real conversation is better than Slack."

  E: "I'm going to be honest — I was frustrated, both in the moment
     and after. I don't want that to run this conversation. How
     are you feeling about how it went?"

  D: "Specifically, when you said 'that's a dumb idea' after
     Jamie's proposal, Jamie didn't speak for the rest of the
     meeting. They asked me afterward if they should keep
     attending."

  A: "What's your read on it? Knowing what you know now, what
     would you do differently?"

  R: [Sam responds. Tech lead listens, asks follow-up, does not
     jump to rebuttal.]

The same core observation, three delivery modes. The mode depends on the stakes and the relationship.

When to Use Which

Low emotional charge, single incident:      SBI
Need commitment to change:                  COIN
High emotional charge or trust shaky:       CEDAR
Repeating pattern, needs action plan:       COIN
One-off, just needs to be named:            SBI
Direct report / power dynamic heavy:        CEDAR

When It Works

Manager-report feedback conversations (especially CEDAR)
Peer feedback with ongoing collaboration (COIN's Next Steps matter)
Performance review conversations (CEDAR's Emotion step prevents the conversation from blowing up)
Post-incident human factors discussions (CEDAR respects that incidents are emotional)
360 review debriefs

When It Does Not Work

Emergency feedback — If someone is doing something harmful right now, skip the framework and stop the behavior. CEDAR in a crisis is malpractice.
Public settings — CEDAR especially needs privacy; the Emotion step cannot be done in a group.
Trivial issues — Using CEDAR for a minor code-style note is overkill and signals you view it as bigger than it is.
When the relationship is fundamentally broken — Frameworks help when there is some trust to build on. When there is none, HR or a neutral facilitator is needed first.

Common Failure Modes

CEDAR-specific

Skipping the Emotion step — Delivering CEDAR as SBI with extra words; the Emotion step is the point.
Performing empathy — "I feel your frustration" when you do not actually understand. The Emotion step requires real listening, not scripted sympathy.
Rebutting in Receive — Using the Receive phase to mount a counter-argument. It is called Receive, not Rebut.
Weaponizing emotion — "I want to share how angry I am" is not the Emotion step. Emotion is named, not deployed.

COIN-specific

Next Steps that are demands — "Stop doing that" is not a Next Step. Next Steps should be co-created, specific, and owned.
Next Steps without ownership — "We should communicate better" is not a Next Step. "I will start meetings with a check-in for 4 weeks" is.
Skipping I (Impact) — Without Impact, the Next Step feels arbitrary; people comply grudgingly rather than commit.

Cross-framework

Framework worship — Reading out the letters ("Now for the Ask step...") makes the conversation robotic. The framework is scaffolding; the delivery is human.
Scripted conversations — Pre-writing all 5 letters and delivering without adapting loses the person in front of you.

SBI — The shared ancestor; start here.
SBI-I — SBI with an added Intent-check step.
DESC (Describe-Express-Specify-Consequences) — Assertiveness-training cousin; covered in Difficult Conversations.
Radical Candor — The philosophical framing; CEDAR/COIN/SBI are tactics for delivering Radical Candor.
GROW — Coaching framework that pairs well with feedback conversations that uncover development needs.
AID (Action-Impact-Desired outcome) — Even more compact cousin for in-the-moment peer feedback.