Feedback has a bad reputation, and almost always for the same reason: it arrives late, all at once, and wearing the face of a verdict. The moment someone hears "we need to talk about your performance," their body goes on guard before you say a single word. And a body on guard doesn't learn, it defends.
The good news is that giving feedback doesn't have to feel like an evaluation. It can become something everyday, specific, and genuinely useful for the person receiving it. In this guide you'll see why the annual review doesn't work, how to bring continuous feedback into your 1:1s, a simple model to structure it, how to handle the hard conversations with care, and why it's worth keeping a person's growth separate from any grade.
Why once-a-year feedback doesn't work
The annual review started with good intentions, but it collides with how people actually work. Here are the core problems:
- It arrives too late. Commenting in December on something that happened in March helps no one. The person no longer remembers the context and neither do you, so you end up talking about impressions, not facts.
- It looks backward. A review goes over what already happened. Useful feedback looks forward: what to try next time.
- It creates anxiety. If a whole year of conversation gets squeezed into one meeting with a score attached, that meeting feels like an exam, not like help.
- It runs on memory. Without a record of what really happened, the conversation fills up with bias and the two or three moments you happen to recall.
The fix isn't a better annual evaluation. It's to stop concentrating everything into a single moment and spread feedback out over time.
Continuous feedback: its natural home is the 1:1
Continuous feedback means commenting on things close to when they happen, in small doses, as a normal part of the work. You don't need to invent a new process: you already have the ideal space, which is the frequent 1:1.
When feedback lives inside a weekly or biweekly conversation, everything changes:
- You talk about something recent, with the context fresh for both of you.
- The person can adjust course right away, not six months later.
- Feedback stops being a solemn event and becomes part of the relationship.
- The hard stuff gets said in small portions, not stockpiled into one annual bomb.
When feedback is frequent, it stops being a sentence and becomes a conversation. No one is surprised, because no one waited a year to find out.
The secret is preparing that 1:1 well. If you walk in with the week's real progress on the table, the conversation starts from facts instead of feelings. This is where a copilot like Vogata helps: it sets the agenda with what actually moved and keeps previous commitments visible, so the time goes into growing instead of reconstructing what happened.
A simple model to structure it: SBI
If you don't know how to start a feedback sentence, the SBI model (Situation, Behavior, Impact) is the simplest and most honest one out there. Created by the Center for Creative Leadership, it orders your message into three parts that steer clear of judging the person:
- Situation: when and where did it happen? Give concrete context.
- Behavior: what did they do, observable and label-free? Describe the action, not the character.
- Impact: what effect did it have? Spell out the real consequence.
The beauty of SBI is that it separates the fact from your interpretation. Instead of "you're disorganized," you describe what you saw and the effect it had. It's hard to argue with a fact, and that lowers the listener's defenses.
A positive feedback example with SBI
"In Thursday's demo (situation), you explained the customer's problem before showing the solution (behavior). That helped the whole team grasp the why, and the meeting ran much shorter (impact). Keep doing it exactly like that."
A growth feedback example with SBI
"In Monday's meeting (situation), you cut off two teammates while they were presenting (behavior). I noticed they spoke up less afterward and we lost a few ideas (impact). How do you see it?"
Notice that closing question. Feedback doesn't end at your mouth: it ends when the other person responds. That's why it helps to frame it as a conversation ("I noticed," "I wonder if") rather than a verdict ("you always," "you are").
How to give difficult feedback with care
Difficult feedback isn't avoided by being soft, and it isn't solved by being harsh. It lands well when the person walks away feeling helped, not punished. A few things that work:
- Talk about the behavior, not the person. "These designs came in late" is something you can work on. "You're unreliable" only stings.
- Do it privately and soon. Close to the event, no audience, in a calm tone. The sooner it comes, the less severe it feels and the faster it gets fixed.
- Be specific. One concrete example beats ten generalities. Vague feels like an attack; specific feels like help.
- Leave room to respond. Maybe there was context you couldn't see. Listening first often changes the feedback you were about to give.
- Close with a next step. Difficult feedback that doesn't end in a concrete agreement just evaporates. Agree on what to try and when you'll check back.
And forget the old "sandwich" of tucking criticism between two compliments. People smell it and stop trusting your praise. It's more honest, and kinder, to say things clearly, with warmth, and focused on getting better.
Separating growth from grading
Here's the nuance that changes everything. Feedback feels like an evaluation when the person senses that every conversation feeds a score. If growing and being graded are the same thing, no one will admit out loud where they struggle, because admitting it lowers the grade.
The way out is to separate the two. A person's growth is supported, not graded. Development goals are tracked over time, talked through, adjusted, but never turned into a number. That's precisely the condition for honesty: when owning a weakness carries no penalty, people own it, and only then can they work on it with you.
What gets graded gets hidden. What gets supported gets better. Track development goals, don't turn them into a grade.
This isn't going soft. You can be very demanding about the outcome and very generous with the room to learn how to reach it. In fact, teams that separate development from evaluation tend to be more honest with themselves, because the conversation stops being a negotiation over a score and becomes a plan to improve.
A good development goal is written clearly: what you want to achieve, by when, and how you'll know you made progress. That clarity makes it easy to track without ever stamping a grade on top.
Feedback is a conversation, not a verdict
If you take away one idea: feedback works when it's frequent, specific, and aimed at growth. It lives in the 1:1s, it leans on facts (not impressions), it's said with care, and it never confuses supporting someone with grading them.
The enemy isn't high standards: it's the chaos and the cold surprise of an evaluation that comes out of nowhere. When you turn feedback into an ongoing conversation, that surprise disappears.
Vogata is the AI copilot for startups that does exactly this: feedback lives in frequent 1:1s, and an AI ecosystem sets the agenda with real progress and gets the commitments ready, so the conversation is about growing, not judging. It's not an HR tool: it's a copilot that makes leading people feel human again. Vogata takes care of the rest.
Start giving feedback that feels like help, not a grade
Take your 1:1s to the next level and let AI prepare the conversation for you.
FAQ
How do you give positive and negative feedback at the same time?
Don't blend them into a fake sandwich, because people stop believing your praise. Give positive feedback when something went well, with a concrete example, and growth feedback in its own moment, close to the event. If you have to cover both in one 1:1, use the SBI model for each and keep them clearly separate: first acknowledge what worked, then address what to adjust with an agreed next step.
What is the SBI feedback model?
SBI stands for Situation, Behavior, Impact. It's a model from the Center for Creative Leadership for giving clear, judgment-free feedback: you describe when and where it happened (situation), what the person did in observable terms (behavior), and the effect it had (impact). By talking about facts rather than personality, it lowers the listener's defensiveness and keeps the conversation focused on improving.
Why don't annual performance reviews work?
Because they arrive late, look only backward, and run on memory. Commenting in December on something from March helps no one course-correct, and squeezing a whole year of feedback into one meeting with a score creates anxiety instead of learning. The fix isn't a better annual review, it's continuous feedback in small doses, mainly in frequent 1:1s.
How do you give difficult feedback without the person getting defensive?
Talk about the behavior, not the person, do it privately and soon, be specific with a concrete example, and leave room for them to respond, because there may be context you couldn't see. Always close with an agreed next step. Framing it as a conversation ('I noticed,' 'I wonder if') instead of a verdict ('you always,' 'you are') dramatically lowers defensiveness.
Should you grade a person's development goals?
No. A person's growth is supported, not graded. Development goals are tracked over time, discussed, and adjusted, but they're never turned into a score. That's the condition for honesty: when owning a weakness carries no penalty, people own it and can work on it. What gets graded gets hidden; what gets supported gets better.