How to Give Feedback That Lands

Tunde, a new support manager in a 160-person SaaS company, waited six weeks to tell an agent that her customer handoffs were confusing. By then, five customers had complained, two teammates were quietly rewriting her notes, and the agent felt ambushed. His first sentence was, "This has been an issue for a while." Her answer was the one every manager dreads: "Why am I only hearing this now?"

Feedback that lands is timely, specific, and tied to the work. It does not require a perfect script. It requires a manager who respects the employee enough to be clear.

Use SBI, then add the next step

The SBI model is simple because it keeps feedback anchored in evidence:

Weak feedback:

You need to communicate better.

Useful feedback:

In yesterday's implementation call with BrightBank, when the client asked about the migration risk, you said, "I am not sure, engineering owns that." The client looked worried and asked for a second meeting. Next time, say what you know, name the owner, and commit to a follow-up time. I can help you prepare the risk language before Thursday's call.

That feedback is not softer. It is clearer. The employee knows the moment, the behavior, the business impact, and the next move.

Stop using the praise sandwich

The praise sandwich sounds kind: compliment, criticism, compliment. In practice, it trains employees to distrust praise. They hear the opening compliment and brace for the real message.

Use separate conversations. Give praise when something is worth repeating. Give corrective feedback when something needs to change. If the issue is serious, do not cushion it so much that the employee misses the point.

Praise still matters. A strong manager says, "The way you handled that angry customer helped us keep the account. You paused, summarized their concern, and gave a concrete next step." That is feedback too.

Match the timing to the stakes

Real-time feedback is best when the behavior is fresh and the change is small. Scheduled feedback is better when the issue is emotional, pattern-based, or tied to career development.

Use real-time feedback for presentation clarity, meeting behavior, missed context, strong customer handling, or small quality issues. Use scheduled feedback for repeated missed deadlines, interpersonal friction, underperformance, promotion readiness, or anything that may trigger defensiveness.

Betterworks reported in 2024 that employees who consistently receive one-to-ones and peer feedback are at least three times more likely to feel supported in their work, skills, and career development. The practical lesson is not "buy software." It is: feedback cadence shapes whether employees feel abandoned or coached.

Choose written or verbal deliberately

Verbal feedback is better when tone matters. Written feedback is better when details matter. Serious performance issues often need both.

Use verbal feedback first when the employee may feel exposed, when the topic involves interpersonal tension, or when you need dialogue. Follow up in writing with a short summary if the issue affects goals, deadlines, or expectations.

Example follow-up:

Thanks for talking today. We agreed that the weekly dashboard will be sent by 10 a.m. Lagos time every Monday, with blockers flagged by Friday afternoon. I will review the first two drafts with you and we will check progress in our next two one-to-ones.

That is not bureaucratic. It protects both people from memory drift.

Make remote feedback more explicit

Remote teams lose hallway context. A short message can sound cold, and silence can feel like judgment. Managers need to over-communicate intent without turning every note into a long essay.

For quick positive feedback in Slack or Teams, be specific:

Your summary in the client channel made the decision easy. The "open questions" section was especially useful.

For corrective feedback, avoid dropping a tense paragraph into chat. Write:

I want to talk through the handoff notes from today's call. Nothing is on fire, but I want us to tighten the format before the next client meeting. Are you free at 3:30?

Then have the conversation by voice or video. Remote feedback should still feel human.

The employee's role is not passive

Receiving feedback gracefully is not the same as agreeing with everything. Employees should listen, ask for examples, clarify the expected change, and follow up. Leaders have to model this first.

A manager can say:

I am going to ask for feedback on how I handled the rollout. I may need a minute to process it, but I want the direct version.

When leaders do that, feedback becomes less theatrical. It becomes normal work.

Avoid the common failure modes

Vague feedback fails because the employee cannot act. Late feedback fails because the employee cannot fix the past. Public corrective feedback fails because shame blocks learning. Personal feedback fails because it attacks identity instead of behavior.

Replace personality labels with observable evidence:

• "Defensive" becomes "You interrupted twice before Mara finished explaining the data issue."
• "Not strategic" becomes "Your plan lists activities, but it does not say which customer segment we are prioritizing."
• "Needs executive presence" becomes "In the leadership meeting, your update had 19 slides and no recommendation. Next time, lead with the decision you need."

If a manager cannot translate a label into behavior, the feedback is not ready.

Put feedback into the operating rhythm

The best feedback cultures are boring in a good way. Managers have weekly or biweekly one-to-ones. Goals are visible. Employees know what good work looks like. Feedback arrives close to the moment. Reviews contain no ambushes.

For a 50-person company, start with three habits: every manager holds biweekly one-to-ones, every employee has three to five quarterly priorities, and every manager gives one piece of reinforcing feedback and one piece of coaching feedback each month. That is enough to change the climate.

For a 500-person company, add manager training, calibration, feedback prompts in the HRIS, and skip-level listening so HR can spot teams where feedback is missing or unsafe.

Use scripts until managers build muscle

Managers often avoid feedback because they think the first sentence must be perfect. Give them scripts. Scripts are not meant to make managers sound robotic; they reduce panic enough for the real conversation to happen.

For reinforcing feedback:

"I want to call out something from the partner meeting. When Finance challenged the timeline, you paused, showed the dependency map, and gave two options instead of defending the original plan. That helped the room make a decision. Keep using that structure."

For corrective feedback:

"I want to talk about the handoff notes from the last three customer calls. In each one, the action owner was missing. The implementation team had to ask follow-up questions, which delayed setup by a day. From today, every handoff needs owner, deadline, risk, and next customer touchpoint."

For values feedback:

"In the incident review, you named your own missed escalation before discussing the team's mistakes. That made it easier for others to be honest. That is what accountability looks like here."

These examples work because they are not moral speeches. They name a real moment and the standard that matters.

Adjust feedback by employee experience level

A new employee needs more context. A senior employee needs more autonomy and a clearer link to scope. A manager needs feedback on the effect they have on others.

For a new hire, say:

"This is a normal first-month miss. The important thing is learning the review path. Here is the checklist we use before sending payroll changes."

For a senior specialist, say:

"At your level, I expect you to flag the trade-off before the deadline is at risk. The issue is not that the timeline moved; it is that stakeholders learned it too late."

For a people manager, say:

"Your team delivered the project, but two people told me priorities changed without explanation. At manager level, the communication path is part of the work."

The standard rises with level. Feedback should make that visible without humiliating people.

Measure whether feedback is working

HR can track feedback quality without spying on every conversation. Use pulse questions, review audits, and manager routines.

Useful signals include employees being able to name their top priorities, review forms containing specific examples, low ratings arriving without surprise, high performers receiving development feedback, and managers holding one-to-ones consistently.

If one department has glowing reviews but high regrettable attrition, investigate. If another department has harsh ratings and low psychological safety, investigate. Feedback is a management behavior, and management behavior leaves data.

Use Atlas to draft structured review language from specific evidence, then edit it so the final feedback sounds like the manager and fits the employee's context.

Teach employees to ask for better feedback

Feedback culture is not only a manager responsibility. Employees can learn to ask for useful input instead of waiting for a vague annual summary.

Good prompts include:

• What is one thing I should repeat from that project?
• What is one thing I should do differently next time?
• Where did my communication create work for someone else?
• What would make my next version promotion-ready?
• Which stakeholder should I involve earlier?

HR can include these prompts in onboarding, manager training, and quarterly check-in templates. When employees ask better questions, managers often give better answers.

Keep a light feedback record

For meaningful feedback, managers should keep short notes: date, topic, expectation, support offered, and follow-up. The note does not need to be legalistic. It should help both people remember what was agreed.

Example:

"May 6: discussed late client handoffs. Standard is owner, deadline, risk, next touchpoint. Manager will review two examples this week."

That record becomes valuable during reviews because the manager can discuss patterns instead of relying on memory.

Key takeaways

• Use Situation, Behavior, Impact, and a next step.
• Stop hiding corrective feedback inside a praise sandwich.
• Give small feedback quickly and pattern-based feedback in a scheduled conversation.
• Use written follow-up when expectations, deadlines, or performance documentation matter.
• In remote teams, use chat for light feedback and voice/video for sensitive feedback.
• Translate labels into observable behavior before you speak.