Bahasa Melayu

Giving Feedback: Models and Examples

Two professionals in a feedback conversation, one offering constructive input with a speech bubble loop

Giving feedback effectively is one of the highest-leverage skills anyone in a team environment can develop. Done well, it accelerates growth, builds trust, and closes the gap between current performance and what's actually possible.

What is giving feedback?

Giving feedback is the practice of sharing specific, observable information about someone's behavior or work so they can understand its impact and adjust accordingly. Positive feedback reinforces what's working; constructive feedback (sometimes called developmental or corrective feedback) identifies what could be improved and points toward how. Both are essential. A team that only receives praise misses growth opportunities. A team that only hears criticism loses motivation fast.

Feedback differs from evaluation (a formal rating) and advice (a suggested solution). It's a focused, real-time input tied to a specific situation, delivered to help someone move forward.

Key facts: giving feedback

  • Employees who receive regular feedback are 3.6x more likely to be engaged at work compared to those who receive little or none. (Gallup, 2022)
  • Only 26% of employees strongly agree that the feedback they receive helps them do better work. (Gallup, 2022)
  • 92% of respondents agree that appropriately delivered negative feedback is effective at improving performance. (Zenger/Folkman, 2014)

Feedback models compared

Different situations call for different structures. Here's how the most commonly used models stack up:

Model What it stands for Best for Watch-out
SBI Situation - Behavior - Impact Day-to-day feedback, quick corrections Can feel mechanical if overused without warmth
COIN Context - Observation - Impact - Next steps Formal or high-stakes feedback sessions Longer structure; avoid rushing the "Next steps"
STAR/AID Situation/Task - Action - Result / Action - Impact - Do differently Performance reviews, behavioral interviews "Do differently" step requires prep to be useful
Feedback sandwich Positive - Critical - Positive Low-trust or unfamiliar relationships Critical message often gets buried or diluted
Radical candor Care personally + Challenge directly Ongoing coaching cultures, trusted teams Requires psychological safety already in place

No model is universally best. SBI works for most everyday situations. COIN adds structure when the stakes are higher. Radical candor is a culture, not just a technique.

Why feedback skills matter

Feedback isn't just a nicety. It's an operational lever.

When managers give consistent, specific feedback, team members know what's expected and can self-correct without waiting for a performance review. That's less managerial overhead, faster skill development, and fewer surprises at review time.

Peer-to-peer feedback matters too. Teams that can give each other honest, respectful input without escalating to a manager tend to resolve problems faster and build stronger working relationships. Interpersonal skills like empathy and self-awareness directly enable this.

There's also an emotional intelligence dimension. Giving feedback requires reading the other person's state, managing your own reactions, and choosing words that open a conversation rather than close it. That's a learned skill, not an innate trait.

And from a communication standpoint, feedback is one of the clearest tests of whether someone can translate an observation into a message that lands with the intended meaning intact.

Common feedback mistakes

Even well-intentioned feedback fails when it falls into these patterns:

Being vague. "Your presentation could be better" tells someone nothing actionable. What specifically could improve? Which slide? Which moment? Vague feedback signals to the receiver that you haven't thought it through.

Delaying too long. Feedback loses relevance fast. Waiting until a quarterly review to mention something that happened in week two means the person can't connect the feedback to their actual behavior. Timely means within 24-48 hours of the event when possible.

Burying the message. The feedback sandwich (positive-critical-positive) sounds polite but often backfires. People remember the praise and discount the criticism, or they sense the "real" message is sandwiched in there and stop trusting the positives. If you have constructive input, lead with it clearly.

Making it personal. "You're disorganized" attacks identity. "The report you submitted was missing three sections that were on the brief" describes behavior. One invites defensiveness; the other opens a conversation.

Dumping. Listing six things at once overwhelms the receiver. Pick one or two key points per conversation.

Skipping the dialogue. Feedback isn't a monologue. If you don't invite the other person to respond, you miss their perspective and lose the chance to reach a shared understanding.

How to give effective feedback

Follow this structure for any feedback conversation, formal or informal.

Step 1: Choose the right moment

Feedback works best when both parties are calm and have a few minutes of focused attention. Avoid giving critical feedback right before a big presentation, in a public setting, or when either person is visibly stressed. Pull someone aside, open a quick chat, or schedule a brief 1-on-1.

Step 2: Use a model to structure your message

Pick SBI for quick situations: state the Situation ("In yesterday's client call"), describe the Behavior ("you interrupted the client twice before they finished their question"), and name the Impact ("they seemed to disengage, and we lost the thread of what they were asking").

For more complex situations, use COIN and add a Next steps discussion at the end.

Step 3: Focus on behavior, not personality

Describe what you observed, not what you've concluded about who the person is. "You missed the 9am deadline three times this month" is observable. "You don't care about deadlines" is a judgment. The first invites accountability; the second invites denial.

Tie your active listening skills here too. After you share your observation, pause and actually listen to their response before moving to solutions.

Step 4: Make it timely

As close to the event as possible. Real-time or same-day feedback is the most actionable. If there's a systemic pattern worth raising, you can address it in a 1-on-1 with reference to multiple recent examples, but even then, name specific incidents rather than speaking in generalities.

Step 5: Agree on next steps

Effective feedback ends with clarity about what changes. This doesn't have to be a formal action plan. It can be as simple as "Does that make sense? What would you do differently next time?" The goal is shared understanding and commitment, not just delivery of your message.

If you're in a mentoring or coaching relationship, this step naturally connects to longer-term goal-setting conversations.

Feedback examples

Here are concrete, scripted examples across different feedback scenarios.

Type Situation Example script
Positive (manager to report) After a strong client presentation "In the client meeting this morning, you stayed calm when they pushed back on pricing and redirected the conversation to value. That kept the deal moving. I noticed the client's tone shifted positively after that."
Constructive (manager to report) Missed deadline with no heads-up "The brief was due Monday and I received it Wednesday with no advance notice. That put the designer in a tight spot and we nearly missed the client deadline. Going forward, if you're at risk of missing a deadline, flag it to me by end of day the Friday before."
Peer-to-peer Colleague dominating team discussions "I've noticed in our last few standups that by the time you've finished sharing your update, we don't have time for the rest of the team to go deep on blockers. Could we try capping individual updates at 2 minutes so everyone gets airtime?"
Upward (report to manager) Manager not providing clear priorities "I want to flag something that's affecting how I work. When I get three urgent requests on the same day without a sense of which one matters most, I end up making that call myself and sometimes I get it wrong. Could we establish a quick check-in at the start of the week to align on priorities?"

Notice that each example names a specific situation, describes a behavior, and either explains the impact or suggests a concrete change. None of them attack the person's character.

Best practices

Do:

  • Prepare your key message before the conversation
  • State the specific situation and behavior first
  • Name the impact clearly, including how it affected you or the team
  • Invite the other person to respond
  • Connect feedback to shared goals where possible
  • Follow up to acknowledge when someone acts on your input
  • Give positive feedback publicly when appropriate; give critical feedback privately

Don't:

  • Open with "I feel like you always..." (sweeping generalizations)
  • Deliver feedback via text or Slack when a live conversation is possible
  • Pile on multiple critiques in one session
  • Use the feedback sandwich for anything important
  • Assume the person knew what the expected behavior was
  • Forget to close with next steps

Frequently asked questions

How often should managers give feedback? The short answer: regularly and in real time. Annual or quarterly reviews aren't a substitute for ongoing feedback. Most research suggests that weekly or biweekly 1-on-1s that include specific observations are the baseline. High-performing teams tend to have cultures where feedback flows continuously, not just in formal settings.

What's the difference between feedback and criticism? Criticism focuses on what's wrong, often without offering a path forward, and frequently blurs behavior with identity. Feedback is specific, tied to observable behavior, and oriented toward improvement. "That report was sloppy" is criticism. "The executive summary was missing the cost comparison the brief asked for" is feedback.

How do you give feedback to someone more senior than you? Lead with your relationship and intent. Frame your input as something you noticed that you wanted to raise directly rather than let simmer. Use the same behavioral language you'd use with anyone else. Most senior professionals respect directness more than vagueness. Conflict resolution skills help here too, especially when you're anticipating resistance.

What if someone gets defensive? Stay calm and name the dynamic without escalating. Something like: "I can see this landed hard. I'm raising it because I want us to work well together, not to criticize you." Give them a moment. Acknowledge their perspective if they share it. The goal isn't to win; it's to be understood and to understand.

Can feedback be given in writing? Yes, especially for documenting agreed-upon changes or sharing detailed observations before a 1-on-1. But written feedback lacks tone and body language, which makes it easier to misread. For anything sensitive or high-stakes, have the conversation live and use writing to confirm what was discussed.


Giving feedback is a skill like any other, which means it gets better with deliberate practice. Start with the models, but don't let structure become a crutch. The goal is a real conversation between two people who both want the work to be better. That's what effective feedback, at its best, actually looks like.