Feedback Conversations at Work: Rules, Methods, Example Phrases, and a Template (2026 Guide)

Few management tools are as effective, and as rarely used well, as the feedback conversation. Most people either get no feedback at all until everything lands at once in the annual review, or they get it in passing, in a hallway or a chat thread, where a well-meant remark can easily read as a jab. Both failure modes produce the same result: behavior doesn't change, and trust doesn't grow.

The good news is that giving feedback is a learnable skill. This guide covers what a feedback conversation is and how it differs from a performance review and a 1:1, which feedback rules have stood the test of practice, which methods exist and when each one fits, how to run the conversation in five steps, which phrases make criticism land instead of wound, how to receive feedback yourself, and where AI can take over the preparation and documentation work. There's also a template you can copy straight into your notes tool.

⚠️ This article was independently compiled based on publicly available information and user feedback as of September 2026.

Table of Contents

1. What Is a Feedback Conversation?
2. The 8 Essential Feedback Rules
3. Feedback Methods Compared: SBI, WWW, Sandwich, and More
4. Preparing a Feedback Conversation: Checklist
5. How to Run a Feedback Conversation: 5 Steps
6. Example Phrases: Constructive Feedback in Practice
7. Receiving Feedback: The Other Half of Feedback Culture
8. Template: Prepare and Document a Feedback Conversation
9. Common Mistakes in Feedback Conversations
10. How AI Supports Feedback Conversations
11. Frequently Asked Questions
12. Conclusion

What Is a Feedback Conversation?

A feedback conversation is a planned conversation in which one person gives another a specific observation about their behavior or their work, with the goal of reinforcing what works and changing what doesn't, together. It can go from manager to report, from report to manager, or between peers. What defines it isn't hierarchy but intent: feedback describes impact; it doesn't hand down verdicts.

Three formats get mixed up in everyday work even though they do different jobs:

The rule of thumb: the annual review should contain no surprises. Anything that comes up there should have been raised earlier, in feedback conversations, while it was still current and changeable. If you collect criticism for twelve months, you're no longer running a feedback conversation; you're running a reckoning.

Regular feedback conversations pay off twice. People change behavior most readily when the feedback arrives close to the event and is specific. And routine lowers the threshold: in teams where feedback happens every few weeks, it's a normal part of work. In teams where it only happens when something went wrong, the calendar invite itself becomes an alarm bell.

The 8 Essential Feedback Rules

A great deal has been written about feedback rules; in essence they come down to eight points. The first five concern the content, the last three the setting.

1. Specific, not general. "You're unreliable" is a verdict with nothing to work on. "The last two status reports arrived two days after the deadline" is an observation you can act on.
2. Behavior, not personality. Feedback addresses what someone does, not what someone is. Behavior can change; character judgments only trigger defensiveness.
3. Separate observation from interpretation. First describe what observably happened, then flag your reading as a reading. The difference between "you were disengaged" and "you had your laptop open during the presentation, which came across to me as disengaged" often decides how the conversation goes.
4. Use I-statements. "I noticed", "it came across to me as", "I'd like". I-statements put your perception on the table without claiming it as objective truth.
5. Make it actionable. Good feedback contains a direction: what would be better, and what's the first step toward it? Feedback about things nobody can change helps no one.
6. Give it promptly. The closer to the event, the sharper the memory on both sides and the bigger the effect. Weeks later, the observation has become an anecdote whose details can be disputed.
7. Choose the right setting. Praise can handle an audience; criticism can't. Critical feedback belongs in a private conversation with enough time, not in the team channel and not in the last two minutes of a meeting.
8. Make it a dialogue. Feedback is an offer, and the other person's perspective is part of it. If you only broadcast, you're not giving feedback; you're making an announcement.

These rules apply in both directions, including positive feedback. A generic "great job" is pleasant but inert; only the specific "the one-page summary made the decision easy for the board" tells someone which behavior to repeat.

Feedback Methods Compared: SBI, WWW, Sandwich, and More

Feedback methods are scaffolding that put the rules into a sequence. None of them is the best one; they fit different situations.

To get started, SBI plus the eight rules is enough: one concrete situation, the observable behavior, its impact on you, and then a request. The Pendleton model is the right choice when you want to hear the other person's self-assessment first, for example in coaching-style conversations. Many practitioners now advise against the sandwich method as a default: if you routinely wrap criticism in praise, people learn to hear every compliment as the opening act of a complaint. It's more honest to separate recognition and criticism and mean both.

When tensions have already escalated, every feedback method reaches its limit; at that point you're no longer giving feedback but working a conflict. That's where a look at the conflict management guide helps.

Preparing a Feedback Conversation: Checklist

Ten minutes of preparation often decide how the conversation goes. This checklist covers the critical points:

• Clarify the occasion. Which specific situation does the feedback refer to? If you can't name one, the feedback isn't ready for a conversation yet.
• Collect facts. What observably happened, and what is already your interpretation? Write both down separately; in the conversation, start with the facts.
• Define the goal. What should be different after the conversation? "Letting off steam" is not a goal. "Status reports arrive by Friday from now on" is.
• Check your own share. Was the expectation ever stated? Were priorities clear? An honest look at your own contribution often changes the tone of the conversation.
• Pick a method and an opener. SBI or WWW for the standard case, Pendleton when you want the self-assessment first. Prepare your first sentence; it's the hardest one.
• Set up the room. Private, undisturbed, enough time, close to the event. Announce the topic in one sentence with the invitation so nobody walks into an ambush: "I'd like to talk briefly about last week's project handover."

For managers, one extra question is worth asking: when was the last piece of recognizing feedback? If conversations only get scheduled when there's a problem, the team learns to read every invite as bad news.

How to Run a Feedback Conversation: 5 Steps

Step 1: Open and set the frame. Name the occasion and your intent in two sentences, without preamble and without accusation: "Thanks for making time. I'd like to talk about Tuesday's client meeting, because I noticed something I don't want to keep from you." The frame makes clear: this is about a situation, not about the person.

Step 2: Describe the observation. Describe the situation and the specific behavior the way a camera would have recorded it: "When the client asked about the timeline, you referred to engineering three times without giving an estimate." No generalizations ("always", "never"), no motives ("you obviously didn't care").

Step 3: Explain the impact and invite their perspective. First the impact, in the first person: "It came across to me as unprepared, and the client followed up twice afterwards." Then the most important question of the conversation: "How did you experience that situation?" From here on, the conversation is a dialogue. Hear the answer out before you respond; the techniques from active listening earn their keep here. Quite often it turns out there were reasons you didn't know about.

Step 4: State your request and agree on a solution. Say what you'd like going forward, and build the path there together: "I'd like us to be able to give an estimate in client meetings. What do you need from me or from engineering to make that possible?" An agreement the receiver helped build lasts far longer than one that was decreed.

Step 5: Summarize and schedule the follow-up. Wrap the agreement in one sentence, agree on how you'll both recognize progress, and set a moment to revisit it, for example in the next 1:1. Write the outcome down briefly. Not as a show of distrust, but because two memories of the same conversation reliably drift apart within a month.

For a pure recognition conversation, the sequence shrinks to steps 2 and 3: a concrete observation and its concrete impact. The request is simply: keep doing this.

Example Phrases: Constructive Feedback in Practice

The difference between wounding and constructive feedback rarely lies in the message; it almost always lies in the wording. Some typical cases:

Work delivered late

• Instead of: "You can't be relied on."
• Better: "The report arrived Wednesday instead of Monday, and I had to present without the numbers. I'd like to understand what happened, and to find a way I can count on the deadline."

Dominating behavior in meetings

• Instead of: "You never let anyone finish."
• Better: "In the planning meeting you answered three questions that were directed at Maria. It came across to me as if her assessment didn't count. I'd like her to represent her own topics."

Unclear communication

• Instead of: "Nobody understands your emails."
• Better: "With yesterday's email I had to ask twice what you needed from me. It would help me if the specific request came first."

Recognition that works

• Instead of: "Great job!"
• Better: "Having the numbers ready in the escalation call saved us the whole debate. That kind of preparation is what makes the difference for the client."

The pattern is always the same: concrete situation, observable behavior, impact in the first person, then a request or a question. Words like "always", "never", "typical", and remote diagnoses of motives ("you just want to look good") tip any conversation over, no matter how justified the underlying observation is.

Receiving Feedback: The Other Half of Feedback Culture

A feedback culture isn't built by good feedback givers alone; it needs receivers with whom feedback is in good hands. Four principles help on the receiving end:

• Listen without negotiating. The reflex to explain and correct immediately shuts down the flow of information. First fully understand what is meant, then evaluate. Clarifying questions are welcome; closing arguments are not.
• Ask until it's specific. Generic feedback ("that was unprofessional") only becomes useful once you have it made concrete: "What did you see that gave you that impression? What would professional have looked like to you?"
• Say thanks, even when it stung. If you answer feedback with justifications or counterattacks, you won't get any next time. A "thanks, I'll take that with me" commits you to nothing and keeps the channel open.
• Decide for yourself what to act on. Feedback is a perspective, not an order. Examine it, cross-check it against other signals, and consciously decide what you'll change and what you won't. You're allowed to report that decision back, too.

Managers play a special role here: someone who visibly handles critical feedback about themselves with composure lowers the threshold for the whole team. The question "what should I do differently?", asked seriously in a 1:1 and without consequences for the person answering, is the fastest route to a feedback culture worthy of the name.

Template: Prepare and Document a Feedback Conversation

You can copy this template straight into your notes tool. The first part structures your preparation, the second records the outcome.

# Feedback conversation – Preparation
Participants: [names] | When: [date, place]
Occasion: [the specific situation the feedback refers to]

## My preparation
- Observation (facts, no interpretation): [...]
- Impact (on me / the team / the client): [...]
- My request going forward: [...]
- My own share in the situation: [...]
- Chosen method: [SBI / WWW / Pendleton / ...]

# Feedback conversation – Outcome
## Key points discussed
- [...]

## The receiver's perspective
- [...]

## Agreement
- [Who] will do [what] differently starting [date]
- How we'll recognize progress: [...]

## Follow-up
- Next check-in: [date, e.g. next 1:1]

Two notes: the preparation section is your private note and doesn't belong in the conversation. The outcome, by contrast, should be shared with the other person promptly, so both of you remember the same agreement.

Common Mistakes in Feedback Conversations

• Saving feedback up. If you collect observations for months, you end up running a conflict conversation instead of a feedback conversation. Small, prompt feedback beats the grand reckoning.
• Giving it in the heat of the moment. Right after the annoyance, the observation is still unsorted and the tone sharper than intended. One night of distance rarely hurts; weeks of distance do.
• Criticizing in front of an audience. Critical feedback in the team meeting shames people and triggers solidarity effects. The content gets lost; the scene is what everyone remembers.
• Making the sandwich the default. If every criticism comes wrapped in praise, both lose value. Receivers quickly learn to hear praise as the announcement of a complaint.
• Addressing motives instead of behavior. "You're just covering yourself" is an accusation nobody can let stand. Staying with observable behavior is harder, and it's the only way to stay in dialogue.
• Ending without an agreement. A conversation that ends with "good talk" changes nothing. Without a concrete next step and a follow-up date, it was a venting session, not a feedback conversation.
• Never following up. The strongest agreement evaporates if nobody ever asks about it again. A short check-in at the next 1:1 signals: this was meant seriously.

How AI Supports Feedback Conversations

The feedback conversation itself is and remains relationship work; no tool will phrase a difficult message for you. Around the conversation, though, there are three places where AI meeting tools noticeably lighten the load: collecting concrete observations, documenting the agreement, and following up.

SuperIntern is a bot-free desktop app for Mac and Windows that captures audio directly from your device. No bot joins the call, so it works platform-independently in Zoom, Google Meet, Microsoft Teams, and Webex, as well as in the meeting room on site.

Four building blocks matter for feedback conversations:

• Concrete observations instead of vague memories. Feedback rule number one, specific instead of general, usually fails in practice for a mundane reason: memory. With searchable transcripts and summaries of the relevant meetings, you can retrieve the actual situation instead of generalizing from recollection.
• Agreements that write themselves down. The AI Canvas keeps a structured live note during the conversation, following your instructions, for example along the template in this article: points discussed, the other person's perspective, the agreement, the follow-up date. You stay present in the conversation instead of switching between listening and typing.
• Full attention for the dialogue. Step 3 of the sequence, truly hearing the other person's perspective, doesn't tolerate parallel typing. When documentation runs automatically, your attention belongs to the person across the table.
• Follow-ups with substance. Before the check-in, a chat across your own meetings answers what exactly was agreed and what has become visible in your shared meetings since.

One caveat belongs to an honest picture: a feedback conversation is a confidential conversation. Recording requires the consent of everyone involved, and especially with critical feedback, you should agree transparently whether and how the conversation is documented. Used openly, the record tends to create safety rather than distrust, because both sides remember the same agreement. A free plan is available, so you can test the workflow in your next 1:1.

Frequently Asked Questions

What is a feedback conversation, in short?

A planned conversation in which one person gives another a specific observation about behavior or work results: observation, impact, and request, followed by the receiver's perspective and a joint agreement. It's shorter and more event-driven than the annual performance review.

What's the difference between a feedback conversation and a performance review?

The performance review is a formal, usually annual conversation with a performance retrospective, goals, and often a rating. The feedback conversation is the smaller, more frequent format tied to a concrete occasion. Used well, it takes the pressure off the annual review: nothing should come up there that wasn't discussed before.

What are the most important feedback rules?

Specific instead of general, behavior instead of personality, separating observation from interpretation, I-statements, making it actionable, giving it promptly, choosing the right setting (criticism in private), and running it as a dialogue. The rules apply to critical and recognizing feedback alike.

What is the SBI model?

A three-part structure from the Center for Creative Leadership: Situation ("in Tuesday's client meeting..."), Behavior ("you referred to engineering three times..."), Impact ("which came across to me as unprepared"). It anchors feedback in one concrete situation and is often extended with a question about intent.

Is the sandwich method still recommended?

Not as a default. If you routinely pack criticism between two layers of praise, receivers learn to distrust genuine praise, and the actual message gets diluted. Separating recognition and criticism, and making both specific, works better.

How often should feedback conversations happen?

Recognition as promptly as possible; critical feedback whenever a pattern emerges. As a rhythm, it works well to anchor feedback as a fixed building block in the regular 1:1, so it happens before topics pile up.

Am I allowed to record a feedback conversation?

Only with the consent of everyone involved; covert recordings are legally risky and destroy exactly the trust the conversation is meant to build. Agreed transparently, automatic documentation can help both sides, because the agreement exists in writing.

Conclusion

The feedback conversation is the smallest and at the same time most effective tool of leadership and collaboration: one concrete observation, its impact, a request, the other side's perspective, and an agreement with a follow-up date. If you follow the eight rules, pick a fitting method, and raise criticism promptly and in private instead of saving it for the annual review, thirty minutes will change more than many a workshop.

The documentation part, retrieving concrete situations, recording agreements, and preparing the follow-up, can largely be automated today. That leaves your attention where it belongs in a feedback conversation: with the person on the other side of the table.

Try SuperIntern Free : Bot-free live meeting notes with speaker attribution, so feedback conversations end in documented agreements instead of diverging memories.