Use when the user needs to prepare for a difficult conversation, give constructive feedback, navigate workplace conflict, or design a feedback system. Covers framework selection, timing decisions, power dynamics, and cultural adaptation. Do NOT use for: email composition or tone (use email-composer), internal team announcements (use internal-comms), professional writing style (use professional-communication), or meeting facilitation (use daily-meeting-update).
| File | Load When | Do NOT Load |
|---|---|---|
framework-selection.md | User asks which feedback framework to use, or is giving feedback and needs a structure beyond basic SBI | User already knows their framework and needs execution help |
conversation-dynamics.md | User is preparing for a difficult conversation, anticipating resistance, or dealing with emotional reactions | User needs quick feedback phrasing, not conversation strategy |
organizational-feedback-systems.md | User is designing a team feedback culture, 360 review process, or feedback cadence for an organization | User needs to give one specific piece of feedback to one person |
| Topic | This Skill | Other Skill |
|---|---|---|
| Preparing difficult 1:1 conversations |
| YES |
| - |
| Choosing feedback frameworks (SBI, COIN, DESC) | YES | - |
| Navigating defensive reactions | YES | - |
| Power dynamics in feedback (upward, downward, peer) | YES | - |
| Cultural adaptation of feedback style | YES | - |
| Designing organizational feedback systems | YES | - |
| Writing feedback emails | Mention only | email-composer |
| Professional tone and communication style | NO | professional-communication |
| Internal announcements and comms | NO | internal-comms |
| Meeting facilitation and standups | NO | daily-meeting-update |
| Performance review documentation | NO | - (HR domain) |
| Conflict resolution in negotiations | NO | - (negotiation domain) |
| Customer complaint handling | NO | customer-support |
Not all feedback should be given immediately. Timing determines whether feedback lands or backfires.
| Signal | Action | Why |
|---|---|---|
| Safety issue or ethical violation | Give feedback NOW, even if imperfect | Delayed feedback = complicity. Document immediately |
| Behavior happened <48 hours ago, you're calm | Give feedback within 24 hours | Memory is fresh for both parties. Specificity is highest |
| Behavior happened <48 hours ago, you're emotional | Wait until calm (max 72 hours) | Amygdala hijack lasts 18-20 minutes (Goleman 1995), but residual cortisol elevation persists 2-4 hours. Feedback given while cortisol-elevated is 3x more likely to escalate (Baumeister 2007) |
| Pattern behavior (3+ occurrences) | Schedule a dedicated conversation | Pattern feedback requires examples and data. Ambushing someone with accumulated complaints backfires |
| The person is in crisis (personal, project, health) | Defer non-urgent feedback 1-2 weeks | Cognitive load theory: people in crisis have reduced processing capacity. Feedback won't land |
| You're uncertain if it's a pattern or one-off | Wait for second occurrence | Single-instance feedback risks being perceived as nitpicking. Exception: if impact was severe |
| Public setting | NEVER give corrective feedback publicly | Public correction triggers shame response (Tangney 1995). Praise publicly, correct privately. Zero exceptions |
The 48-hour rule: Feedback given >48 hours after the event loses 40-60% of its impact (Hillman 2019). The recipient's memory of the situation diverges from yours. If you can't give feedback within 48 hours, write down the specific SBI details immediately and use those notes when you do give it.
| Your Situation | Use This Framework | Why |
|---|---|---|
| Simple behavioral feedback (one specific incident) | SBI (Situation-Behavior-Impact) | Minimizes defensiveness. Observable facts only |
| Need to connect feedback to organizational context | COIN (Context-Observation-Impact-Next steps) | Adds organizational "why" that SBI lacks |
| Addressing a pattern, need to describe feelings | DESC (Describe-Express-Specify-Consequences) | Allows emotional expression that SBI deliberately excludes |
| Giving upward feedback to your manager | SBI + permission opening | "I have an observation. Would you be open to hearing it?" reduces power asymmetry threat |
| Cross-cultural feedback (high power distance) | Indirect SBI -- soften with questions | "I noticed X. What was your thinking?" instead of stating impact directly |
| Performance improvement conversation | GROW (Goal-Reality-Options-Will) as wrapper, SBI for specifics | GROW provides coaching structure. SBI provides evidence |
When SBI fails: SBI assumes the recipient values observable facts and logical impact chains. It fails with (1) highly emotional people who need feelings acknowledged before facts, (2) cultures where direct behavioral descriptions feel accusatory, and (3) situations where the "impact" is your feelings, not a business outcome. In these cases, DESC or relationship-first approaches work better.
Feedback flows differently depending on power relationships. Ignoring this is the #1 source of feedback failure.
| Direction | Key Challenge | Adaptation |
|---|---|---|
| Manager -> Direct report | Power amplifies every word. A "minor suggestion" lands as a "serious criticism." Managers consistently underestimate their impact by 2-3x (Kluger & DeNisi 1996) | Soften opening, ask questions first, emphasize support. One critical feedback point per conversation max |
| Peer -> Peer | No formal authority. Feedback can feel like overstepping. Risk of damaging collaborative relationship | Frame as shared problem. "I noticed something that's affecting our work. Can I share?" Not "you did X wrong" |
| Direct report -> Manager | Highest-risk feedback direction. 60% of upward feedback is either not given or softened to meaninglessness (Tourish & Robson 2006) | Request permission explicitly. Focus on impact on YOU, not their behavior. "When X happens, I find it hard to Y" |
| Skip-level (to their boss) | Perceived as going over someone's head. Damages trust with immediate manager | Exhaust direct feedback first. Document attempts. Only escalate for safety, ethics, or persistent pattern after 3+ direct attempts |
| Cross-functional | Different team norms, no shared context, no relationship bank | Build relationship first. Feedback without relationship = criticism from a stranger. Minimum 3 positive interactions before first corrective feedback |
The 5:1 ratio (Gottman 1994, validated in workplace by Losada & Heaphy 2004): Relationships that sustain honest feedback maintain a minimum 5:1 ratio of positive to negative interactions. Below 3:1, corrective feedback damages the relationship more than it improves behavior. Track your ratio before giving difficult feedback.
Before giving feedback, assess the environment. Feedback in a psychologically unsafe environment does more harm than silence.
| Level (Edmondson 2018) | Signals You'll See | Feedback Approach |
|---|---|---|
| Stage 1: Inclusion safety | People participate in meetings, share personal stories, new members feel welcomed | Basic feedback possible. Keep it positive-heavy (8:1 ratio) |
| Stage 2: Learner safety | People ask questions without ridicule, admit mistakes, seek help openly | Constructive feedback possible in private. Growth-framed: "here's how to improve" |
| Stage 3: Contributor safety | People volunteer ideas, challenge status quo, take initiative | Regular feedback in both directions. SBI works well here |
| Stage 4: Challenger safety | People disagree openly with leaders, point out problems, propose changes without fear | Full honest feedback culture. Direct, specific, frequent. "Radical Candor" is possible HERE and only here |
The Radical Candor trap: Kim Scott's framework requires Stage 4 psychological safety to work. Applied at Stage 1-2, "Challenge Directly" is perceived as aggression, not candor. Most teams are at Stage 2. Assess before prescribing.
| Situation | Why Skip It | Do This Instead |
|---|---|---|
| The behavior is preference, not performance | Your way isn't the only way. Code style, meeting style, communication style differences are not feedback-worthy unless they cause measurable impact | Ask yourself: "Is this a problem, or is it just different from how I'd do it?" |
| You have <3 interactions with this person | No relationship bank. Feedback without relationship = unwelcome criticism | Build 3-5 positive interactions first. Then you've earned the right to be honest |
| The person already knows | They missed the deadline. They know. Telling them adds shame without information | Ask: "What happened? How can I help?" Information > judgment |
| You're the wrong person | Feedback about someone's relationship with their manager should come from their manager, not you | Redirect to the right person or encourage them to seek feedback from the right source |
| It won't change | Deeply ingrained personality traits, physical characteristics, things outside their control | Accept, adapt, or escalate to HR if it's a performance issue. Don't give feedback on who someone IS |
| Name | What Happens | Why It Fails |
|---|---|---|
| Feedback Sandwich | Positive-Negative-Positive ("You're great, BUT..., and also great") | Recipients learn to ignore positives and brace for the "but." Dilutes both the praise and the criticism. 78% of recipients report the sandwich feels insincere (Schwartz 2019) |
| Drive-By Feedback | Quick critical comment in passing, no context, no follow-up | Recipient has no opportunity to respond, clarify, or act. Creates anxiety and resentment. The feedback-giver feels relieved; the recipient feels ambushed |
| Delayed Dump | Saving up 6 months of feedback for the annual review | Recipient can't improve what they don't know about. Each item loses specificity over time. The conversation becomes overwhelming and unactionable |
| Proxy Feedback | "Several people have told me that you..." without naming sources | Feels like a conspiracy. Unverifiable claims can't be addressed. The recipient trusts no one. Either own the feedback yourself or bring specific people into the conversation |
| Therapy Feedback | Psychoanalyzing motives: "I think you do this because of your need for control..." | You're not their therapist. Stick to observable behaviors and their impact. Motive-guessing triggers maximum defensiveness |
| Scorekeeping | Keeping a mental tally: "Last month you did X, and before that Y, and also Z..." | Feels like prosecution, not feedback. Address issues as they arise. Accumulated lists signal you've been withholding, which breaks trust |