Feedback

Feedback is how teams improve. Yet most people hate giving it and hate getting it. This section covers frameworks for breaking through that discomfort and delivering feedback that actually helps people grow—whether in code review, performance conversations, or day-to-day collaboration.

Good feedback is specific, timely, and focused on behavior and impact, not character. It acknowledges what someone did well and what they could do better. These frameworks remove the guesswork from the feedback conversation and make it safer for both giver and receiver. When done right, feedback becomes a gift, not a threat.

Frameworks Covered

• SBI (Situation-Behavior-Impact) — Describe the situation, the specific behavior you observed, and its impact. Non-judgmental and grounded in observation, not assumption.
• CEDAR (Context-Emotion-Describe-Ask-Receive) — Establish context, acknowledge emotions, describe what happened, ask what they'll do differently, and listen to their response.
• COIN (Context-Observation-Impact-Next Steps) — Similar structure focused on clarity: context, what you observed, why it matters, and how to move forward.
• Radical Candor — Care personally about the person while being direct about their performance. Feedback paired with genuine interest in their growth.

When to Reach for This

• You need to give someone feedback on their work or behavior.
• You're in a code review and want to be constructive, not just critical.
• Someone's approach isn't working but you want to help them improve, not shame them.
• You're managing people and conducting performance conversations.
• You want to receive feedback better yourself.

Prerequisites

Foundations. Understand your intent and your audience before you give feedback; it's personal and high-stakes.