7 Good Feedback Examples for 2026

Your next one-on-one starts in ten minutes. You need to address a missed deadline, recognize strong client handling, or correct a pattern that is starting to affect the team. The hard part is rarely knowing that feedback is needed. The hard part is saying it in a way that is clear, respectful, and useful.

Managers usually drift into one of three mistakes. They wait too long and let a small issue become a habit. They soften the message until the employee leaves unsure what needs to change. Or they come in so blunt that the person hears threat instead of guidance.

Good feedback is a skill, not a personality trait.

You do not need polished, perfect phrasing. You need a structure you can trust under pressure, plus language that fits the moment and the person in front of you. That is especially true in remote teams, where a quick Slack message can sound colder than intended and an async note can create confusion instead of clarity.

That is what this guide is built to solve. You will see seven practical feedback models, each paired with example scripts in supportive, direct, and developmental tones so you can adjust your wording without watering down the message. You will also get a practical way to adapt each approach for Zoom, email, Slack, and async check-ins.

Strong feedback also depends on delivery habits outside the conversation itself. If you are working on that foundation, these leadership communication strategies for managers will help you stay clear under pressure.

Use these examples as working language, not rigid templates. The goal is not to sound scripted. The goal is to help your employee hear what matters, know what to do next, and leave the conversation with trust intact.

1. SBI Model

You are in a one-on-one. You need to address something that happened yesterday, but you do not want the conversation to turn into an argument about attitude, intent, or personality. SBI helps because it keeps the discussion anchored to three things the employee can hear and use: the situation, the behavior, and the impact.

That structure sounds simple. In practice, it prevents one of the most common manager mistakes. Feedback gets vague fast.

A weak version sounds like, "Your communication needs work." A stronger version sounds like, "In yesterday's client meeting, you interrupted three colleagues before they finished speaking, and after that, the room got quieter and fewer people contributed."

What good SBI feedback sounds like

SBI is flexible. The structure stays the same, but the tone should change based on the person, the stakes, and whether you are correcting, coaching, or reinforcing.

Supportive tone:

"During yesterday's client meeting, when Priya was outlining the timeline, you stepped in before she finished. After that, she pulled back and the team shared less. I know you were trying to keep the meeting moving. Next time, pause and let each person finish before you respond."

Direct tone:

"In the Q3 review, you answered questions over your teammates several times. That made it harder for them to explain their own work. I need you to stop interrupting in shared meetings."

Developmental tone:

"During the launch debrief, you jumped in quickly with solutions before the team finished naming the problem. That shortened the discussion and we missed a few useful details. In the next debrief, write down your first response and wait until two other people have spoken."

You can use the same model for positive feedback.

"During the Q3 project review, you documented each decision with the rationale behind it. That stopped the team from reopening settled questions later, and we moved faster because of it."

Use actions, not labels. "Interrupted twice" gives you something concrete to discuss. "Came across as dismissive" invites a fight over interpretation.

Where managers go wrong with SBI

The first mistake is cramming a pattern into one sentence. If the issue has happened five times, start with the clearest recent example. Once the employee understands that example, you can say, "This is part of a pattern I have seen in a few meetings this month."

The second mistake is naming behavior without naming consequence. "That was not helpful" does not tell the person what changed. Say what happened next. The client looked confused. The team stopped contributing. The work had to be redone. The meeting ran over.

The third mistake is using the right structure with the wrong tone. A high performer who made a one-off mistake usually needs a coaching conversation. Someone repeating the same behavior after prior feedback may need a firmer script. The model does not make that decision for you. Your judgment does.

Use this quick filter before you speak:

• Situation: Name the meeting, project, or moment.
• Behavior: Describe what the person did or said.
• Impact: Explain what happened because of it.

SBI is even more critical for remote teams. In Slack, email, and recorded comments, people cannot rely on body language or quick clarification. Specific wording matters more. Instead of "You were abrupt in the thread," write, "In the product channel this morning, you replied 'this makes no sense' without explaining the issue. After that, the discussion stalled." For higher-stakes points, move from async to live conversation.

If you want to connect SBI feedback to a concrete development plan, this guide to SMART goals for performance management will help. If you want sharper delivery in the moment, this guide to leadership communication strategies is a useful next step.

2. SMART Goals Framework for Development Feedback

Development feedback often dies in the follow-up. The conversation feels thoughtful, both people nod, and then nothing changes because the next step was too broad. "Be more strategic" isn't a plan. SMART goals turn feedback into behavior people can practice and track.

This model works best after you've already discussed the issue. Don't use SMART too early. If the person still doesn't agree on the problem, a goal won't fix the conversation.

Turn advice into a real target

Weak feedback:

"I'd like you to be more proactive."

SMART version:

"By the end of Q2, bring three process issues to our team meeting, along with a proposed fix for each. We'll review which ideas moved forward and what you learned from each one."

Weak feedback:

"Improve your presentations."

SMART version:

"Present in three team meetings this quarter. After each one, ask for feedback on clarity and engagement, then use those notes to improve the next presentation."

Here are three versions you can borrow.

Supportive tone:

"You've got strong ideas. I'd like to help you show them earlier and more consistently. For the next month, bring one recommendation to each planning meeting and include the trade-off you see."

Direct tone:

"We've talked about missed deadlines more than once. For the next six weeks, I need every project update sent by the agreed time on Friday. If something slips, flag it before the deadline, not after."

Developmental tone:

"You're ready for more visibility. Over the next quarter, lead two cross-functional updates and send the recap after each one. We'll review what landed well and where you want to improve."

What makes SMART useful

The best SMART goals build capability, not only compliance. If you only set task goals, you might get short-term improvement and no real growth. Focus on the skill under the issue. Is the person struggling with prioritization, stakeholder communication, preparation, or decision-making?

Keep the list short.

• Specific: Define the behavior, not a vague intention.
• Measurable: Agree on what progress looks like.
• Achievable: Stretch the person without setting them up to fail.
• Relevant: Tie the goal to the role or current team need.
• Time-bound: Put a review date on the calendar.

A good reference for framing these goals is this guide to SMART goals for performance management.

One more practical point. Goals work better when the employee helps shape them. In startup teams, people often accept a manager's wording in the meeting and then ignore it later because they never felt ownership. Build the goal together and ask, "What feels realistic from your side?"

3. Radical Candor Framework

Some managers hide behind kindness. Others hide behind bluntness. Radical Candor asks for both care and direct challenge at the same time. If one side is missing, the message breaks.

This model is useful when the issue matters, the relationship matters, and a soft script would feel evasive. It works well with high performers, peers, and experienced employees who value honesty. It fails when you use "I'm only being honest" as cover for poor delivery.

Direct, without becoming harsh

Supportive tone:

"I care about your success here, so I want to be clear. That presentation wasn't ready. Your data was solid, but the story wasn't easy to follow and you weren't prepared for likely questions. I'd like us to do a dry run before the next one."

Direct tone:

"I'm going to be straightforward because this matters. Your recent code reviews have stayed at the surface level. You're catching style issues, but you're missing bigger risks. That's affecting team quality, and I need you to review with more depth."

Developmental tone:

"I know you're capable of a stronger standard than what I saw. You're moving fast, but speed is hurting clarity. Let's slow the prep slightly, tighten the structure, and build a repeatable review process."

Ask permission when the topic is sensitive. A simple opener helps.

"Can I give you direct feedback on something important?"

That short question changes the tone. It signals respect and prepares the other person to listen.

Care doesn't mean softening the point until it disappears. Care means telling the truth in a way the person can use.

The trade-off managers miss

Radical Candor takes relationship credit. If trust is thin, direct feedback lands as threat, not respect. New managers often borrow the words before they've built the trust.

This matters even more in startups and SMBs, where teams are small and every relationship carries more weight. An underserved angle in the market is the need for examples that balance psychological safety with directness for new managers in high-pressure environments, highlighted in negative 360 feedback examples from Jop.

Use this model when you can also offer support. That support might be coaching, a clearer example, a practice run, or tighter prioritization. If you drop the hard message and walk away, you didn't practice candor. You delivered judgment.

For remote delivery, don't choose Slack for high-stakes corrective feedback if nuance matters. Use video or voice when possible. If you need async communication, state your intent early. Write, "I'm sharing this because I want to help you improve before the next review cycle," then move into specifics.

4. START Feedback Model

Your one-on-one starts with a defensive employee and a problem you both know is real. If you open with a verdict, the conversation turns into an argument. START gives you a better path. It stands for See, Tell, Ask, Respond, Thank.

The order matters. You start with their view, add your observation, ask them to examine the gap, agree on a response, and close by recognizing their honesty or effort. That structure works well when you need the employee engaged in solving the issue, not just listening to your summary.

I use START when an employee is likely to tense up, or when they already sense something went wrong and need help naming it clearly. It slows the conversation just enough to get past surface-level answers.

Scripts you can adapt by tone

Supportive version:

Manager: "How do you think the project wrap-up went from your side?"

Employee: "Messy. I think I lost track of scope."

Manager: "I saw the timeline slip after extra requests came in. What made it hard to push back in the moment?"

Employee: "I didn't want to seem unhelpful."

Manager: "Fair concern. For the next project, what boundary could you set earlier so you stay helpful without absorbing every request?"

Direct version:

Manager: "How do you think the client handoff went?"

Employee: "Pretty well, I think."

Manager: "I saw several open questions in the handoff notes, and the client had to follow up twice for missing details. What happened?"

Employee: "I rushed the final update."

Manager: "That gap created extra work for the client and the team. Next time I need a complete handoff. What check will you use before you send it?"

Developmental version:

Manager: "What part of the sprint felt strongest to you?"

Employee: "Execution, once priorities were clear."

Manager: "I agree. Delivery was solid. I also noticed some hesitation during planning. What would help you lead that discussion with more confidence next sprint?"

Each version uses the same sequence, but the tone shifts. Supportive language lowers heat. Direct language names impact faster. Developmental language keeps the focus on skill building. That flexibility is the core strength of START.

Where managers get this wrong

Some managers turn START into a soft conversation with no clear point. Others rush through the employee's perspective and use the model as a longer way to deliver criticism. Both approaches fail.

The standard is simple. Let the employee speak first, but do not let the conversation stay vague. Your "Tell" step should include a concrete observation. Your "Respond" step should end with one clear next action, not a general promise to improve.

Adapting START for remote and async feedback

START also works well in remote teams because it gives structure to conversations that can easily drift or escalate in writing. The trade-off is speed. Async reflection often improves honesty, but it can also slow resolution if the issue is urgent.

Use written START prompts before a one-on-one when the topic needs thought, not immediate correction. For example, ask the employee to send a short note on what they saw, then reply with your observations before the meeting. That gives both of you a cleaner starting point and reduces the instinct to react defensively on the call.

If you need to do this asynchronously, keep each step short:

• See: "How do you think the launch went from your side?"
• Tell: "I noticed the approval step was skipped before the file went out."
• Ask: "What got in the way?"
• Respond: "Let's add a final pre-send check and test it this week."
• Thank: "Thanks for being open about it."

For sensitive issues, avoid long written feedback blocks. Send the "See" and "Tell" briefly, then move to video or voice for the "Ask" and "Respond" steps. That keeps the structure without forcing a high-stakes conversation into a format that strips out tone.

START is a strong choice when you want candor with participation. The employee leaves with more than a correction. They leave with a plan they helped build.

5. Micro-feedback and Feed-Forward Model

A rep finishes a client call. The meeting was mostly solid, but they buried the key recommendation until the last two minutes. If you wait until next week's one-on-one, the moment is gone. A short note sent that day is more useful: name what happened, explain what to do on the next call, and keep it easy to act on.

That is the job of micro-feedback and feed-forward. Micro-feedback stays close to the event. Feed-forward points to the next attempt. Used together, they help you coach in real time without turning every correction into a formal performance conversation.

This model works best when the behavior is small, repeated, and fixable within days, not months. The trade-off is that speed can make feedback feel constant if your tone is off or your team only hears from you when something needs correction. Good managers balance quick course correction with visible recognition.

Short scripts you can use right away

After a meeting, supportive tone:

"You handled the escalation calmly and kept the customer focused on next steps. Do that again in the next call. Open with the same steady summary."

After a meeting, direct tone:

"You had the right recommendation, but you brought it in too late. Next time, state your position in the first five minutes so the group can react while options are still open."

Developmental tone before the next meeting:

"In tomorrow's client call, lead with the problem statement before you offer solutions. Then pause and confirm the client agrees with the framing."

For a remote employee in Slack:

"Nice work on the status update. It was clear and easy to scan. In the next one, add one line on risk and one line on needed support."

After a missed moment:

"You had a strong point in the meeting, but you waited until the end to raise it. In the next discussion, speak up while the team is still shaping options."

A simple pattern to follow

Keep the message short, but do not make it vague. I use a three-part pattern:

• Name the behavior: "You opened with background instead of the recommendation."
• State the impact: "That slowed the decision."
• Give the next move: "Next time, start with your recommendation, then add context if needed."

That last step matters. Many managers are comfortable pointing out what went wrong. Fewer are precise about what the person should try next. Feed-forward closes that gap.

How to adapt it by tone

The same point can land very differently depending on the employee and the moment.

Use a supportive tone when confidence is shaky but effort is strong: "You were prepared, and that showed. Next time, trim the setup and get to your main point sooner."

Use a direct tone when the pattern is clear and needs to change now: "You interrupted twice while Priya was answering. In the next review, wait until she's finished before you add your point."

Use a developmental tone when the employee can handle nuance: "Your analysis was strong, but the headline got lost. For the next deck, put the recommendation on slide one and use the rest to support it."

What makes it work

Micro-feedback works when it feels normal, specific, and proportionate to the issue. It fails when every message reads like monitoring.

A few rules help:

• Send it while the moment is still fresh: Same day is usually best.
• Focus on one behavior: Do not stack three corrections into one note.
• Point to the next repetition: Give the person a clear behavior to repeat, stop, or test.
• Save bigger issues for fuller conversations: Patterns tied to role scope, trust, or performance still need a one-on-one.

A useful outside example comes from Contentsquare. Karl and Lucy's e-commerce team combined user feedback surveys with session replays to catch checkout friction early. After those fixes, conversion improved, according to Contentsquare's user feedback examples. The management lesson is practical. Small signals caught early are easier to fix than larger failures discovered weeks later.

Adapting micro-feedback for remote and async teams

This model is especially useful in distributed teams because you often see the output before you see the struggle behind it. A quick written note can correct course fast, but written feedback also strips out tone. That means the smaller the message, the more careful the wording needs to be.

For async feedback, use this structure:

• Observation: "The update covered progress clearly."
• Gap: "It did not mention the approval risk."
• Next step: "In the next update, add one sentence on risk and one on what you need."

If the topic is sensitive, do not stretch micro-feedback past its limit. Send a short note that names the issue, then move to video or voice. Use text for clean, low-stakes coaching. Use conversation for emotion, ambiguity, or repeated problems.

6. Situation-Complication-Resolution Model

A manager gives clear feedback on a missed risk in sprint planning. The employee nods, says they understand, and then makes the same mistake two weeks later. Usually the problem is not resistance. It is missing context. They heard what happened, but not why it mattered enough to change.

That is where the Situation-Complication-Resolution model helps. It works well when the issue has a second-order effect such as a customer miss, a cross-team delay, or a bad decision made with incomplete information. Use it for feedback that needs consequences and a path to repair, not for every small correction.

Use SCR when the stakes need to be explicit

The structure is simple:

• Situation: Name the specific event or behavior.
• Complication: Explain the consequence it created.
• Resolution: State what to do next time.

The trade-off is real. SCR gives people useful context, but it can also sound heavier than the issue deserves. If you use it on minor points, employees start hearing drama instead of coaching.

Here are a few scripts you can adapt.

Direct tone:

"During sprint planning, you stayed quiet about the timeline risk. The complication is that we committed to a date we cannot hit, and sales is now planning around it. Next time, if the scope looks off, raise it in the meeting before we agree to the date."

Developmental tone:

"I reviewed your code comments. You caught style issues, but the deeper architecture and security questions were mostly untouched. The complication is that we can merge cleaner-looking code that still creates performance or risk problems. In your next review, start with architecture, performance, and security. Leave style for the second pass."

Supportive tone:

"In the handoff doc, the key decisions were missing. The complication is that the next team had to infer what was settled and what was still open, which slowed their work. For the next handoff, add a short decisions section and a separate list of unresolved questions."

A good SCR conversation does one more thing. It matches the tone to the employee and the moment. A steady performer who made one miss may need a calm explanation. Someone repeating the same pattern may need firmer language. If you want more examples of how to adjust that tone, this guide on how to give feedback to employees in real conversations is a useful companion.

Why SCR works well for remote and async feedback

SCR is especially useful in distributed teams because people often see only their slice of the work. They do not hear the side conversation with sales, they do not sit in the customer call, and they do not watch another team scramble to recover from a missing detail. The complication fills in that missing line of sight.

For written feedback, label each part so the message stays clear and does not read like blame.

Async example, neutral tone:

Situation: "The weekly update came in after the leadership review."

Complication: "They made a resourcing decision without your latest status, so the project now has the wrong support."

Resolution: "Send the update before the review deadline, even if one item is still in progress. If a detail is pending, mark it as provisional."

If the issue is sensitive, use SCR in a live conversation first and document the resolution after. Text is good for clarity. Voice or video is better when you need to judge reaction, answer questions, or reset trust.

If the person does not understand the consequence, the resolution will sound optional.

That is the essential value of SCR. It helps people connect one behavior to the wider system around them, then gives them a specific correction they can use the next time the same pressure shows up.

7. Reinforcement-Based Feedback

A manager says, "Great job," after a hard week. The employee smiles, then goes right back to guessing what actually earned that praise.

Reinforcement-based feedback fixes that problem. It shows people the exact behavior you want repeated, ties it to a result, and makes the standard easier to recognize next time. Used well, it is one of the fastest ways to strengthen judgment, ownership, and team habits.

Recognition that strengthens performance

The quality of the praise matters more than the warmth of it. Vague recognition feels good for a moment. Specific recognition teaches.

Use the model in three parts:

• Behavior: What the person did
• Effect: What changed because of it
• Repeat signal: What you want to see again

That gives you a script you can adapt to the person and the moment.

Supportive tone:

"I want to call out how you handled the bug this morning. You diagnosed the issue quickly, kept the customer updated, and coordinated with the team without creating panic. Keep working that way in high-pressure incidents."

Direct tone, still positive:

"In the meeting, you asked the question nobody else raised about the feature requirement. That prevented us from building the wrong thing. Keep doing that, even when the room is rushed."

Developmental tone:

"Your recap after the client call was strong. You summarized decisions clearly and flagged one unresolved risk. Use that same structure in cross-functional updates. It will help you lead bigger discussions."

Make positive feedback specific enough to stick

Specific praise directly impacts engagement and retention. It also sharpens performance because people can repeat what they understand.

I tell managers to avoid generic approval and name the move itself. Do not say, "You were great with the client." Say what great looked like. Did they slow down a tense call, clarify a vague request, or surface a risk early? Each version reinforces a different skill.

This model also works well across channels, but the channel changes the wording.

For remote teams, short written praise works for clear, visible wins: "Your handoff note was clear and complete. It saved the engineering team time and prevented follow-up questions. Keep using that format."

For async situations, recorded audio or video is better when tone matters or the contribution was nuanced: "You handled a difficult stakeholder calmly, and you kept the decision moving without dismissing their concern. I want the team to learn from that approach."

Public recognition can reinforce team standards, but use it carefully. Some employees like visible praise. Others find it uncomfortable or performative. Ask, or pay attention to how they respond.

If you want more examples of specific praise and correction in real conversations, this guide on how to give feedback to employees is a useful companion.

One caution. Do not turn every compliment into a setup for criticism. If praise always comes with a hidden correction, people stop trusting it. Reinforcement-based feedback works only when recognition stands on its own and clearly marks behavior worth repeating.

Comparison of 7 Feedback Models

Turn Feedback into Your Management Superpower

It is 4:55 p.m. on Friday. A team member has handled a client call poorly, you know the conversation cannot wait until next week, and you are tempted to either soften it so much that nothing changes or come in too hard and create defensiveness. That moment is where management skill shows up.

Feedback gets easier when you stop treating it like a personality test and start treating it like a repeatable practice. Strong managers do not rely on instinct alone. They choose a model, adjust their tone, and say the hard thing clearly enough that the employee can act on it.

Start small and get reps. Use one model this week in a low-stakes moment. Try SBI after a meeting, reinforcement-based feedback after a strong customer interaction, or micro-feedback right after a handoff slips. The goal is not to sound polished. The goal is to make behavior visible so good work gets repeated and weak spots get corrected early.

This is also where adaptation matters.

The same feedback point can be supportive, direct, or developmental depending on the person and the situation. A new employee may need more context and reassurance. A senior performer may prefer a shorter, more direct version. A remote teammate may need the message in writing first, followed by a live conversation so tone does not get lost.

Use the model that fits the job in front of you. SBI gives you clarity on a specific behavior. SMART turns feedback into a development plan with deadlines and ownership. Radical Candor helps in high-stakes conversations where care and challenge both need to be obvious. START works well when you need the employee to reflect and help shape the next step. Micro-feedback keeps small issues from becoming patterns. SCR connects behavior to business consequences. Reinforcement-based feedback shows people exactly what strong performance looks like so they can repeat it.

Trade-offs are real. Too much empathy can blur the message. Too much directness can shut a person down. Too much structure can make you sound scripted if you read from a template instead of using it as support. The practical standard is simple: be clear enough to act, calm enough to hear, and specific enough to remember.

Remote and async feedback need tighter execution. State your intent in the first line. Name the situation, the impact, and the next step. If the topic has emotional weight, do not leave it sitting in Slack without context. Use written feedback for clarity, then move to video or live conversation when nuance matters. If you manage across time zones, summarize agreements in writing so nobody has to reconstruct the conversation later. That is where multi-tone scripts help. You can keep the structure consistent while changing the language to fit the channel and the employee.

If preparation is what slows you down, use a tool to build your first draft. PeakPerf is one option for drafting feedback conversations, development plans, and one-on-ones with frameworks like SBI and SMART. Used well, it helps you get from a blank page to a usable outline faster. If you are comparing options, a feedback management app can also support consistency and documentation.

Managers get better at feedback the same way employees get better at performance. Practice, review, adjust, repeat. Use the models in this article as working tools, not theory. Start with one conversation, choose the tone on purpose, and keep going until clear feedback feels like part of how your team works every day.

If you want a faster way to prepare for your next tough conversation, PeakPerf helps you build structured, editable drafts for feedback, reviews, and development plans using frameworks like SBI and SMART, with tone options for supportive, direct, and developmental conversations.