Feedback That Lands: Beyond the Sandwich Method

Many leaders have learned to wrap criticism between two positive statements. The intention is understandable: protect the relationship and reduce defensiveness. The problem is that experienced employees quickly learn the pattern and wait for the negative sentence in the middle.

Feedback becomes more trustworthy when recognition and corrective feedback are both allowed to stand on their own.

Describe behavior, not identity

“You are not collaborative” is difficult to work with. “In the last two planning meetings, you rejected the proposal before the other team had finished explaining the constraints” gives the recipient something concrete to examine.

A simple structure is situation – behavior – impact: when did it happen, what was observable, and what effect did it have on the work or relationship?

Do not save everything for the annual review

Feedback loses value when it arrives months after the relevant behavior. Timely feedback keeps context available and allows smaller adjustments before a pattern becomes entrenched. That does not mean reacting to every irritation immediately; it means addressing relevant patterns while examples are still concrete.

State the purpose

Corrective feedback lands differently when the recipient understands why you are raising it. Is the goal better collaboration, clearer leadership, higher quality or a different customer outcome? Linking behavior to a relevant outcome prevents the conversation from sounding like a personal preference.

Invite the other perspective

Feedback is your observation of impact, not an objective account of another person’s intention. After describing what you saw, ask how the person understood the situation. New information may change your interpretation without invalidating the impact you observed.

Make the next behavior concrete

“Be more strategic” or “communicate better” is not a useful behavioral request. Define what you would want to see next time: involve the other function before the decision, raise the risk earlier, summarize the decision at the end of the meeting, or ask before assuming intent.

Leaders need feedback too

The higher the hierarchy, the more filtered feedback often becomes. Senior leaders can counter this by asking for examples rather than general ratings: “Which behavior of mine makes collaboration easier? Which makes it harder? What should I notice earlier?”

The most important part is what happens afterwards. If people take the risk of giving upward feedback and nothing visibly changes, the channel closes again.