Giving and Receiving Feedback

Why Feedback Matters

• Accelerates growth and learning -- research shows people who receive regular feedback improve 39% faster than those who do not
• Builds stronger relationships -- honest communication creates deeper trust over time
• Improves performance -- you cannot fix what you do not know is broken
• Shows you care enough to help -- silence is not kindness when someone needs to hear the truth
• Creates a culture of excellence -- teams that exchange feedback openly outperform those that avoid it
• Prevents small issues from becoming big problems -- early feedback is a course correction, not a crisis

The Cost of Avoiding Feedback

When we withhold feedback, we are not being kind -- we are being comfortable. Consider what happens when feedback is absent:

• A colleague keeps making the same mistake in presentations because no one tells them
• A friend's behavior slowly pushes people away, but everyone stays silent
• A manager thinks they are doing great while their team quietly suffers
• A student never improves because the teacher only says "good job"

The discomfort of giving feedback lasts minutes. The consequences of withholding it can last years.

Breaking Down the SBI Model

S -- Situation: Anchor the feedback in a specific time and place. This prevents the recipient from feeling attacked with generalizations like "you always" or "you never."

"In yesterday's team meeting..." / "During our call with the client on Tuesday..." / "At lunch today when we were discussing the project..."

B -- Behavior: Describe what the person actually did -- only observable actions, not your interpretation of their motives. Stick to what a camera would have recorded.

"...you interrupted Sarah three times..." / "...you sent the report two days early..." / "...you raised your voice and used profanity..."

I -- Impact: Explain the effect the behavior had -- on you, on others, on the team, on the project. This is what makes the feedback meaningful.

"...which made it hard for her to finish her point, and we missed her insights." / "...which gave us extra time to review and catch two errors." / "...which made several team members uncomfortable and shut down the conversation."

Example 1 -- Meeting interruptions:

"In yesterday's project meeting (S), you interrupted Sarah three times while she was presenting her data (B), which made it difficult for the team to hear her analysis and she became visibly frustrated (I)."

Example 2 -- Missed deadline:

"Last Friday when the client report was due (S), the deliverable was submitted two days late without any advance notice (B), which damaged our credibility with the client and put the account renewal at risk (I)."

Example 3 -- Poor email communication:

"In your email to the marketing team this morning (S), you used all capital letters and exclamation marks throughout the message (B), which came across as aggressive and several people mentioned feeling uncomfortable (I)."

Example 4 -- Lack of preparation:

"During the client presentation on Wednesday (S), when the client asked about our Q3 projections, you said you hadn't looked at the numbers yet (B), which made us appear unprepared and the client questioned whether we were taking their business seriously (I)."

Example 5 -- Negative body language:

"In our brainstorming session today (S), you crossed your arms, sighed audibly, and rolled your eyes when Marcus shared his idea (B), which discouraged him from contributing further and the team lost a potentially valuable perspective (I)."

Example 6 -- Great teamwork:

"When the server went down on Friday afternoon (S), you immediately organized the response team and kept everyone calm with clear status updates every 15 minutes (B), which helped us resolve the issue in half the expected time and the client never even noticed (I)."

Example 7 -- Mentoring a colleague:

"Over the past month (S), you've been spending 30 minutes each morning walking Priya through the database queries (B), and she's now handling client requests independently, which has freed up the whole team and boosted her confidence (I)."

Example 8 -- Excellent presentation:

"In your quarterly review presentation yesterday (S), you used clear data visualizations and told a compelling story with the numbers instead of just reading bullet points (B), which kept the executive team engaged for the full 45 minutes and led to immediate budget approval (I)."

Common SBI Mistakes to Avoid

• Vague Situation: "Sometimes you..." -- Be specific about when and where
• Interpreting Behavior: "You were trying to show off..." -- Stick to observable actions, not assumed motives
• Exaggerating Impact: "Everyone hates when you..." -- Be honest and proportional
• Stacking Situations: Listing five different incidents at once overwhelms the receiver. Focus on one at a time.
• Using "always" or "never": These words trigger defensiveness. Use specific instances instead.

The Golden Rule: Praise in Public, Correct in Private

This simple principle prevents humiliation and maximizes the impact of both types of feedback.

• Public Positive Feedback: Recognizing someone's achievement in front of others amplifies the praise. It tells the person their work is valued and shows the team what good looks like. "I want to call out Maria's work on the client proposal -- her research was thorough and her presentation was outstanding."
• Private Constructive Feedback: Correcting someone in front of others causes shame, embarrassment, and resentment. It damages the relationship and makes the person less receptive to the message. Always find a private setting -- a closed office, a quiet walk, a one-on-one meeting.

Good Timing

• Soon after the behavior (within 24-48 hours) -- Details are fresh, and the connection between behavior and feedback is clear
• When both parties are calm -- Neither you nor they should be emotionally charged
• When there is enough time for a real conversation -- Do not rush feedback between meetings
• When the person is in a receptive state -- Not when they are stressed, hungry, rushing, or dealing with a personal crisis
• At a natural checkpoint -- After a presentation, at the end of a project phase, during a scheduled one-on-one

Bad Timing

• In the heat of the moment -- When emotions are high, feedback becomes a weapon, not a tool
• Weeks or months later -- "Remember that thing you did in March?" loses all relevance and feels like an ambush
• Right before they go on stage or into a big meeting -- This creates anxiety, not improvement
• At the end of a long, exhausting day -- Neither of you will bring your best selves to the conversation
• In front of an audience -- Constructive feedback in a group setting humiliates rather than helps
• Over text or email (for serious feedback) -- Tone is easily misread; important conversations deserve face-to-face or at minimum voice-to-voice

Setting the Stage

Before diving into feedback, set up the conversation for success:

• Ask permission: "I noticed something in the meeting today -- would you be open to hearing my perspective?"
• State your intent: "I'm sharing this because I care about your growth and our working relationship."
• Choose the right medium: Face-to-face for important feedback. Video call if remote. Never text for constructive feedback.
• Ensure privacy: A closed door, a quiet corner, a private Zoom call -- not the open office or a group chat.

The Sandwich Structure

Top Bread: "You did a great job on the report layout."

The Filling: "But the data analysis had several errors that need to be fixed."

Bottom Bread: "Overall though, you're a valuable team member."

Alternative 1: Direct SBI

Just use the SBI model directly. Adults can handle honest, respectful feedback without sugar-coating. "In the report you submitted Friday, the data analysis on pages 3-5 contained calculation errors, which means we cannot present these numbers to the client until they are corrected."

Alternative 2: Context + Feedback + Invitation

Share why you are giving the feedback, deliver it clearly, then invite their perspective. "I want to talk about the report because I know you're capable of excellent work. The data analysis section had several errors. Can you walk me through your process so we can figure out where things went wrong?"

Alternative 3: Separate the Conversations

Give positive feedback in one conversation and constructive feedback in another. This way, neither type contaminates the other, and both feel genuine.

Alternative 4: Feedforward

Instead of focusing on what went wrong in the past, focus on what to do differently in the future. "For the next report, I'd recommend double-checking all calculations against the source data and having a peer review before submission."

When the sandwich still works: With people who are new to receiving feedback, who are particularly sensitive, or in low-stakes situations, the sandwich can ease someone into the feedback process. Use it as a stepping stone, not a permanent crutch.

Weak Positive Feedback (Vague and Forgettable)

• "Good job."
• "Nice work on the project."
• "You're awesome."
• "That was great."
• "Keep it up."

These are not bad, but they are not memorable or motivating. The person does not know specifically what they did well or why it mattered.

Strong Positive Feedback (Specific and Meaningful)

• "The way you handled that angry customer on the phone -- staying calm, acknowledging their frustration, and offering a concrete solution -- turned a potential complaint into a five-star review. That's exactly the standard we want."
• "Your decision to stay late and re-check the numbers before the presentation meant we caught an error that could have cost us the contract. That kind of diligence sets you apart."
• "I noticed you went out of your way to include the new team member in today's discussion by asking for her perspective directly. That small act made her feel welcome and she shared an insight none of us had considered."
• "The executive summary you wrote for the board was outstanding. You distilled 40 pages of data into two pages of clear, actionable insights. Three board members commented on how useful it was."
• "When the project timeline got compressed, instead of complaining, you reorganized the task list, delegated effectively, and delivered on time. Your leadership in that moment was exactly what the team needed."

Five Rules for Powerful Positive Feedback

1. Be specific. Name exactly what they did and why it mattered.
2. Be timely. Give it as close to the event as possible while it is still relevant.
3. Be genuine. Only praise what you truly mean. People detect hollow compliments instantly.
4. Connect it to impact. Show them the ripple effect of their actions -- on you, the team, the client, the organization.
5. Vary your delivery. Sometimes say it in person, sometimes in a group meeting, sometimes in a handwritten note. Variety keeps it fresh.

Step 1: Prepare

• Clarify your intention: Are you trying to help them improve, or are you venting frustration?
• Gather specific examples -- do not rely on vague impressions
• Choose the right time and private setting
• Consider their perspective: What might they be dealing with that you do not know about?

Step 2: Open with Context and Care

• "I want to discuss something because I value our working relationship and your growth."
• "Can I share an observation? I think it will help us work together more effectively."
• "I have some feedback about [specific topic]. Is now a good time?"

Step 3: Deliver Using SBI

• State the situation, the specific behavior, and the impact
• Use "I" statements: "I noticed..." not "You always..."
• Stick to facts, not interpretations of motive

Step 4: Pause and Listen

• After delivering the feedback, stop talking. Let them respond.
• They may need a moment to process. Silence is acceptable.
• Listen to their perspective without interrupting

Step 5: Collaborate on a Path Forward

• "What do you think we can do differently going forward?"
• "How can I support you in making this change?"
• "Let's check in on this again next week."

Step 6: Follow Up

• Check in later to see if the change is happening
• Acknowledge improvement when you see it
• Be patient -- behavior change takes time

Words That Destroy Constructive Feedback

Avoid these words and phrases -- they trigger defensiveness and shut down the conversation:

• "You always..." -- Overgeneralization that invites argument
• "You never..." -- Same problem; the person immediately thinks of exceptions
• "You should have..." -- Sounds parental and condescending
• "That was stupid" -- Attacks the person, not the behavior
• "Everyone thinks so" -- Piling on with unnamed others feels like a gang-up
• "I'm not mad, but..." -- Passive-aggressive signals that undermine trust
• "No offense, but..." -- A guaranteed signal that offense is coming

The LEARN Framework for Receiving Feedback

L -- Listen Fully. Let them finish without interrupting. Even if you disagree, hear the complete message before responding. Your only job in this moment is to understand what they are saying.

E -- Exhale. Take a breath. Notice your emotional reaction without acting on it. Feel the defensive impulse rise and let it pass. This pause prevents reactive responses you will regret.

A -- Ask Questions. Seek to understand, not to challenge. "Can you give me a specific example?" "What would good look like?" "How did that impact you?" Questions show you are taking the feedback seriously.

R -- Reflect. Thank them sincerely: "Thank you for telling me this. I need some time to think about it." You do not have to agree with everything on the spot. Give yourself space to process what is true, what is partially true, and what you might see differently.

N -- Next Steps. Follow up later: "I've been thinking about what you said, and here's what I'm going to do differently..." This closes the loop and shows respect for the person who took the risk of being honest with you.

Defensive Reactions to Avoid

The Secret: Separate the Message from the Delivery

Sometimes feedback is delivered poorly -- the timing is bad, the tone is harsh, or the words are clumsy. That does not mean the content is wrong. Train yourself to look past imperfect delivery and extract the useful information.

Even if only 10% of the feedback is valid, that 10% is gold. The person who can extract value from imperfect feedback will always grow faster than the person who dismisses it because it was not delivered perfectly.

Proactively Seeking Feedback

The most growth-oriented people do not wait for feedback -- they ask for it. Here are ways to invite honest input:

• "What is one thing I could do differently to be more effective?"
• "If you could change one thing about how I lead meetings, what would it be?"
• "I'm working on improving my presentation skills. What did you notice?"
• "On a scale of 1-10, how well did I handle that situation? What would make it a 10?"
• "What's something I do that might be frustrating for you that you haven't told me about?"

Comparison 1: Work Quality

Bad: "Your work is sloppy."

Good: "In the report you submitted yesterday, there were three calculation errors on page 4 and two formatting inconsistencies. Can we set up a review process to catch these before submission?"

Comparison 2: Communication Style

Bad: "You're too aggressive in meetings."

Good: "In today's planning meeting, when you raised your voice and said 'that idea is ridiculous,' two people stopped contributing. I think your passion is an asset, but the delivery made others feel shut down."

Comparison 3: Punctuality

Bad: "You're always late. It's disrespectful."

Good: "In the last four team meetings, you arrived 10-15 minutes late. When that happens, we either wait for you and lose time, or start without you and you miss context. Can we figure out what's causing this?"

Comparison 4: Attitude

Bad: "You have a bad attitude."

Good: "When the team discussed the new process change this morning, you said 'this is pointless' and 'nothing ever works here.' I noticed several teammates looked discouraged after that. I understand change is frustrating -- can we talk about your specific concerns?"

Comparison 5: Teamwork

Bad: "You're not a team player."

Good: "When Alex asked for help with the data migration last week, I noticed you said you were too busy, even though your calendar showed availability. When team members feel they cannot count on each other, it affects morale. Is there something going on I should know about?"

Comparison 6: Leadership

Bad: "You need to be a better leader."

Good: "In the last sprint, three team members came to me saying they were unclear on priorities because they had not received direction from you. When the team is uncertain about what to focus on, productivity drops and stress increases. Can we talk about how to improve communication around priorities?"

Comparison 7: Presentation Skills

Bad: "That presentation was boring."

Good: "During your 30-minute presentation, I noticed you read directly from the slides without making eye contact, and the audience started checking their phones around minute 15. The content was solid -- if you practiced delivering it more conversationally and added a few stories, I think the audience would stay engaged throughout."

Comparison 8: Email Communication

Bad: "Your emails are terrible."

Good: "In the email thread with the client yesterday, your reply was one sentence without a greeting or sign-off. The client mentioned to me that it felt curt. For client-facing communication, adding a brief greeting and a closing line goes a long way in maintaining the relationship."

Comparison 9: Initiative

Bad: "You never take initiative."

Good: "Over the past month, I've noticed that you wait for me to assign tasks rather than identifying what needs to be done. For example, the monthly report was due Thursday and I had to remind you Wednesday night. I'd love to see you take ownership of recurring tasks without prompting. What would help make that happen?"

Comparison 10: Listening Skills

Bad: "You don't listen."

Good: "In our conversation yesterday, I noticed that while I was explaining the new process, you were typing on your laptop and then asked a question I had just answered. When that happens, I feel like my input is not valued, and we end up repeating information. Could we try putting devices away during important discussions?"

Comparison 11: Positive Feedback

Bad: "Good job on the project."

Good: "The way you structured the project timeline with clear milestones and buffer periods meant that even when we hit unexpected delays in phase 2, we still delivered on time. Your planning saved the team at least 20 hours of crisis management."

Comparison 12: Customer Service

Bad: "You need to be nicer to customers."

Good: "When the customer called about the delayed shipment today, I overheard you say 'That's not my department.' The customer then asked to speak with a manager. Next time, try saying 'Let me connect you with the right person to help,' which keeps the customer feeling cared for even when you need to transfer them."

As a manager, your feedback carries extra weight. Your words can motivate or devastate. Key principles:

• Be consistent. Do not only give feedback during annual reviews. Make it a regular habit.
• Balance the ratio. Research suggests a 5:1 ratio of positive to constructive feedback creates high-performing teams.
• Be specific about expectations. "I need the weekly report by end of day Friday" is better than "be more timely."
• Create psychological safety. If people fear punishment for mistakes, they will hide errors rather than learn from them.

Example: "I want to acknowledge the work you put into the Q3 forecast -- the level of detail was excellent and the board was impressed. Moving forward, I'd like us to add a risk analysis section. Want to brainstorm what that could look like?"

Giving feedback to someone with authority over you requires courage and tact. Key principles:

• Frame it as helping the team. "I've noticed something that might help our team meetings run more smoothly."
• Ask permission. "Would you be open to hearing a perspective on how we could improve the process?"
• Focus on impact, not personality. "When meeting agendas change last minute, the team struggles to prepare" -- not "You're disorganized."
• Suggest solutions, not just problems. Come with ideas, not just complaints.

Example: "I wanted to share something that I think could help our one-on-ones be even more productive. When I bring up a concern and the response is 'just figure it out,' I sometimes need more direction to know I'm heading the right way. Would it be possible to spend two minutes brainstorming together before I go off to solve it?"

Peer feedback can be the most authentic because there is no power dynamic. But it can also feel awkward. Key principles:

• Lead with the relationship. "I'm telling you this because I respect you and want us both to succeed."
• Be collaborative, not corrective. You are equals -- frame feedback as a shared observation, not a directive.
• Use "I" language. "I noticed..." or "I felt..." rather than "You did..."
• Offer help. "If you want, I can review the deck with you before you present."

Example: "Hey, I noticed in the client call today that when you were explaining the timeline, the client looked confused. I think the phasing might have been unclear. Want to run through it together before the follow-up call? I think we can make it tighter."

Feedback to children shapes their self-image, confidence, and relationship with learning. Key principles:

• Praise effort, not talent. "You worked so hard on that drawing" -- not "You're so talented." Effort praise builds a growth mindset.
• Be specific about behavior. "When you shared your toy with your sister, that made her really happy" -- not "Good boy."
• Correct behavior, not character. "Hitting is not okay" -- not "You're a bad kid."
• Keep the ratio heavily positive. Children need far more encouragement than correction to develop confidence.

Example: "I noticed you got frustrated with your math homework and wanted to quit, but you kept trying and figured out the last three problems on your own. That persistence is going to help you succeed at a lot of things in life. I'm proud of you for not giving up."

Friendship feedback often involves the most personal and sensitive topics. Key principles:

• Check your motive. Are you sharing this because it will genuinely help them, or because you want to be right?
• Ask if they want advice. "Do you want me to just listen, or would you like my honest opinion?"
• Be gentle but honest. "I care about you, and because I do, I need to tell you something difficult."
• Respect their autonomy. After sharing, let them decide what to do with the information.

Example: "I've noticed that the last few times we've gotten together, you've talked a lot about how unhappy you are at work but haven't taken any steps to change it. I say this as someone who cares about you -- I think you might be stuck in a pattern, and I wonder if it would help to talk to someone who could give you professional guidance. What do you think?"

Scenario 1: The Chronic Interrupter

Situation: Your colleague Alex interrupts others in every meeting. Today, he cut off three different people mid-sentence.

Guided Response (SBI): "Alex, in today's team meeting, I noticed you jumped in while Priya, Marcus, and Lisa were each mid-sentence. When that happens, their ideas don't get fully heard and some people stop contributing. I know you're enthusiastic and have great ideas -- could you try jotting your thoughts down and sharing them after the person finishes?"

Scenario 2: Excellent Customer Save

Situation: A customer called furious about a billing error. Your teammate Maya handled it with calm professionalism, resolved the issue, and the customer ended the call thanking her.

Guided Response: "Maya, I overheard your call with the billing customer just now. The way you acknowledged their frustration without getting defensive, walked them through the correction step by step, and followed up with a confirmation email -- that turned an angry customer into a loyal one. That's exactly the kind of service that sets our team apart."

Scenario 3: The Gossiper

Situation: Your coworker has been talking about another colleague's personal issues behind their back in the break room.

Guided Response: "Hey, I wanted to talk to you privately about something. In the break room earlier, when you were sharing details about Jordan's personal situation, I felt uncomfortable because Jordan wasn't there to speak for themselves. If that information got back to them, it could really damage their trust in our team. I'd appreciate it if we could keep personal matters private."

Scenario 4: Micromanaging Boss

Situation: Your manager checks on your work every hour, asks for updates on tasks that take 10 minutes, and reviews every email before you send it.

Guided Response: "I appreciate how invested you are in our work quality. I've noticed that with the frequent check-ins throughout the day, I sometimes lose focus switching between the work and the updates. Would you be open to trying a system where I send you a summary at the end of each day and flag anything that needs your input immediately? I think it could actually give you better visibility while freeing up time for both of us."

Scenario 5: Strong Work Ethic

Situation: A junior team member has been staying late every day this week to make sure a difficult project gets done right, even though no one asked them to.

Guided Response: "I've seen you here past 7 PM every night this week working on the Henderson project. The extra care you're putting into the data validation -- checking every entry against the source -- is the reason we can present these numbers with confidence. Your dedication does not go unnoticed, and it's raising the bar for the whole team. Also, make sure you're taking care of yourself -- I don't want you to burn out."

Scenario 6: Poor Hygiene

Situation: A colleague has noticeable body odor that is making others uncomfortable, but no one has said anything.

Guided Response (extremely private, one-on-one): "This is awkward for me to bring up, and I hope you know I'm saying this because I respect you. I've noticed a body odor issue a few times recently. I wanted to mention it privately because I'd want someone to tell me if the situation were reversed. It might be something simple to address, and I didn't want it to become something others notice. I hope this is okay."

Scenario 7: Taking Credit for Others' Work

Situation: In a meeting with senior leadership, your teammate presented an idea as their own that you had originally proposed in a brainstorming session last week.

Guided Response: "I wanted to talk about the leadership meeting today. When you presented the client segmentation idea, that was the same approach I proposed in our brainstorming session last Tuesday -- I have it in my notes. When my contribution is presented as someone else's, it affects my motivation and trust. Going forward, I'd appreciate if we credit ideas to where they originate. Can we agree on that?"

Scenario 8: Friend Who Is Always on Their Phone

Situation: Every time you meet your friend for dinner, they spend half the time scrolling their phone, responding to messages, and barely engaging in conversation.

Guided Response: "I love getting together with you, and I want to mention something. The last few times we've hung out, I've noticed you're on your phone a lot during our conversation. When that happens, I feel like I'm competing for your attention, and honestly, it makes me not want to make plans. I'm not trying to make you feel bad -- I just miss actually connecting when we're together. Can we try phones-away during dinner?"

Scenario 9: Student Who Improved Dramatically

Situation: A student who was struggling at the beginning of the semester has been putting in extra effort and their grades have gone from Ds to Bs.

Guided Response: "I want you to know that I've noticed the change in your work this semester. Your essays have gone from surface-level summaries to thoughtful analysis with strong evidence. The essay you wrote last week on the Civil War showed original thinking that surprised me. Whatever you're doing differently -- the extra study sessions, the office hours visits, the second drafts -- it's working. Keep going."

Scenario 10: Team Member Undermining Decisions

Situation: After the team agreed on a new process in a meeting, one team member has been openly criticizing the decision to other departments and doing things the old way.

Guided Response: "I need to discuss something important with you. After we agreed as a team to implement the new reporting process last Monday, I've learned that you told the marketing team 'it's a waste of time' and have continued using the old format. When a team member publicly undermines a group decision, it creates confusion across departments and erodes trust within our team. I understand you may have concerns -- and I genuinely want to hear them. But the place to raise those concerns is with the team, not behind our backs. Can you share what's bothering you so we can address it?"

Scenario 11: Receiving Harsh but Valid Feedback

Situation: Your manager says bluntly: "Your last three reports have been below standard. The analysis is shallow and the recommendations are generic. I expected better from you."

Guided Response (receiving): "Thank you for being direct with me. I want to do better. Can you show me a specific section where the analysis fell short so I understand what deeper analysis looks like? And could you point me to an example of a report that meets your expectations? I'd like to use it as a benchmark. I'll rework the last report and send it to you by Thursday for feedback before I submit the next one."

Scenario 12: Roommate Who Doesn't Clean Up

Situation: Your roommate consistently leaves dishes in the sink, clothes on the couch, and never takes out the trash.

Guided Response: "Can we talk about how we're splitting the household stuff? I've noticed that the last two weeks, there have been dishes in the sink for two or three days at a time, and the trash has been overflowing by the time I take it out. I'm not trying to nag -- I just want us both to feel comfortable at home. Can we set up a simple rotation that works for both of us? I'm flexible on how we divide it."

Key Takeaways from These Scenarios

• Every scenario uses specific, observable details -- not vague accusations
• Impact is always stated -- so the person understands WHY it matters
• The tone is respectful -- even when the topic is difficult
• A path forward is suggested -- feedback without direction is just criticism
• The relationship is preserved -- the goal is improvement, not punishment
• Positive feedback is just as specific as constructive -- "good job" is replaced with exactly what was good and why