<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/healthy-feedback-2pl0t0oew" -->

---
title: Healthy Feedback | daily.dev
description: Thoughtworks colleagues Anuja Karnik and Sumeet lay out how to give and receive peer-to-peer feedback in software teams, framing all feedback as either...
canonical: https://daily.dev/posts/healthy-feedback-2pl0t0oew
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Healthy Feedback | daily.dev
og:description: Thoughtworks colleagues Anuja Karnik and Sumeet lay out how to give and receive peer-to-peer feedback in software teams, framing all feedback as either...
og:url: https://daily.dev/posts/healthy-feedback-2pl0t0oew
og:image: https://api.daily.dev/og/posts/2pL0t0OEW.png
og:image:alt: Healthy Feedback
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Healthy Feedback

**[Martin Fowler](https://daily.dev/sources/mafo)** · 24 min read · 0 upvotes · 0 comments

## Summary

Thoughtworks colleagues Anuja Karnik and Sumeet lay out how to give and receive peer-to-peer feedback in software teams, framing all feedback as either strengthening confidence or improving effectiveness. Practical patterns covered include the CSBI (context-situation-behaviour-impact) format, seeking permission before delivering feedback, escalating from content to pattern to relationship-level feedback, and receiving feedback with curiosity rather than defensiveness. The piece also catalogs antipatterns to avoid: tying feedback to performance reviews, the sandwich method, orchestrated events like public 360s and speedback, and feedback farming for appraisal credit. The core message is that a healthy feedback culture builds through consistent small moments rather than one-off frameworks or events.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://martinfowler.com/articles/healthy-peer-feedback.html>

## Questions this post answers

### What is the CSBI framework for giving feedback?

CSBI stands for context-situation-behaviour-impact, a format for sharing feedback that starts by asking about context before describing the situation, the observed behaviour, and its impact. Seeking context first, such as asking why someone skipped presentation slides, creates psychological safety and positions the feedback giver as curious rather than judgmental, reducing tension compared to jumping straight into judgment.

_daily.dev surfaces practical frameworks like this for engineers building stronger team habits._

### Why doesn't the feedback sandwich method work?

Sandwiching criticism between two layers of praise makes the praise feel insincere and the criticism feel diluted, leaving the receiver confused about the actual goal of the feedback. A better approach, used by practitioners like Pat Kua, is to headline the conversation by explicitly separating time spent strengthening confidence from time spent improving effectiveness, so both land clearly.

_engineers refining how they mentor teammates can find more culture-building patterns on daily.dev._

### Why shouldn't peer-to-peer feedback be collected during performance reviews?

Feedback tied to performance reviews tends to be neither useful for personal growth nor useful as review input, because it often addresses goals unrelated to the reviewee's actual objectives and can confound the process. Since reviews affect salary and promotions, people withhold honest criticism, and looking back over six months to a year produces vague platitudes instead of specific, actionable observations.

_daily.dev helps engineering leads track advice on building healthier, review-independent feedback loops._

## Similar posts on daily.dev

- [Giving Hard Feedback](https://daily.dev/posts/giving-hard-feedback-4olhol7mp) · Josh Hornby · 0 upvotes · 0 comments
- [Maximizing Return-on-Feedback — Aviv Ben-Yosef](https://daily.dev/posts/maximizing-return-on-feedback-aviv-ben-yosef-76az7cebh) · Tech Lead Digest · 0 upvotes · 0 comments
- [Feedback doesn't scale](https://daily.dev/posts/feedback-doesn-t-scale-fofy711w5) · Hacker News · 0 upvotes · 0 comments
- [Where feedback goes to die](https://daily.dev/posts/where-feedback-goes-to-die-7r08hf9cd) · bonnycode · 16 upvotes · 1 comments

---

Tags: [#leadership](https://daily.dev/tags/leadership), [#company-culture](https://daily.dev/tags/company-culture)

[View this post on daily.dev](https://daily.dev/posts/healthy-feedback-2pl0t0oew)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Healthy Feedback","url":"https://daily.dev/posts/healthy-feedback-2pl0t0oew","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/healthy-feedback-2pl0t0oew"},"datePublished":"2026-09-24T14:16:59.217Z","dateModified":"2026-09-24T14:23:17.277Z","description":"Thoughtworks colleagues Anuja Karnik and Sumeet lay out how to give and receive peer-to-peer feedback in software teams, framing all feedback as either...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1141c852d146ee01659f880d5658de00?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1141c852d146ee01659f880d5658de00?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Martin Fowler","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Martin Fowler","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/mafo","url":"https://daily.dev/sources/mafo"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/healthy-feedback-2pl0t0oew","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"leadership,company-culture","timeRequired":"PT24M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Martin Fowler","item":"https://daily.dev/sources/mafo"},{"@type":"ListItem","position":3,"name":"Healthy Feedback"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/healthy-feedback-2pl0t0oew#faq","mainEntity":[{"@type":"Question","name":"What is the CSBI framework for giving feedback?","acceptedAnswer":{"@type":"Answer","text":"CSBI stands for context-situation-behaviour-impact, a format for sharing feedback that starts by asking about context before describing the situation, the observed behaviour, and its impact. Seeking context first, such as asking why someone skipped presentation slides, creates psychological safety and positions the feedback giver as curious rather than judgmental, reducing tension compared to jumping straight into judgment. daily.dev surfaces practical frameworks like this for engineers building stronger team habits."}},{"@type":"Question","name":"Why doesn't the feedback sandwich method work?","acceptedAnswer":{"@type":"Answer","text":"Sandwiching criticism between two layers of praise makes the praise feel insincere and the criticism feel diluted, leaving the receiver confused about the actual goal of the feedback. A better approach, used by practitioners like Pat Kua, is to headline the conversation by explicitly separating time spent strengthening confidence from time spent improving effectiveness, so both land clearly. engineers refining how they mentor teammates can find more culture-building patterns on daily.dev."}},{"@type":"Question","name":"Why shouldn't peer-to-peer feedback be collected during performance reviews?","acceptedAnswer":{"@type":"Answer","text":"Feedback tied to performance reviews tends to be neither useful for personal growth nor useful as review input, because it often addresses goals unrelated to the reviewee's actual objectives and can confound the process. Since reviews affect salary and promotions, people withhold honest criticism, and looking back over six months to a year produces vague platitudes instead of specific, actionable observations. daily.dev helps engineering leads track advice on building healthier, review-independent feedback loops."}}]}
```

