Employee feedback: how to talk about results so the work gets better
Team8 min read
Employee feedback: the SBI model and the fact-impact-agreement model, sample phrases for praise and criticism, how often to give it and where to get facts.

Employee feedback is a conversation between a manager and an employee about specific actions and their results, aimed at reinforcing what works and fixing what doesn't. It differs from an evaluation: an evaluation sums things up, while feedback helps do better next time.
Feedback in a minute
| Principle | What it looks like |
|---|---|
| Specificity | "On Tuesday a client waited 3 hours for a reply," not "you reply slowly" |
| Timeliness | Within 1–2 days of the situation |
| About actions, not the person | "You didn't ask about the budget," not "you're inattentive" |
| Impact | What happened because of that action |
| Agreement | What we do differently next time |
| Balance | Praise just as specifically and regularly |
Why feedback doesn't work
- Vague words. "You need to try harder" — it's unclear what exactly to do.
- Judging the person. The person gets defensive instead of listening.
- Being late. A conversation a month later about a situation the employee no longer remembers.
- Only criticism. Feedback starts to feel like punishment.
- No facts. The manager says "it seems to me," the employee answers "it seems to you."
- No agreement. You talked, and nothing changed.
The SBI model: situation — behavior — impact
| Step | What to say | Example |
|---|---|---|
| Situation | When and where | "Yesterday in the conversation with the kitchen renovation client…" |
| Behavior | What exactly the employee did | "…you sent the price list but didn't ask about budget and timing…" |
| Impact | What it led to | "…the client replied that it was too expensive and vanished" |
After that comes a question and an agreement: "What do you think you could have asked? Next time let's start by clarifying budget and timing."
The "fact — impact — agreement" model
A simplified version for everyday conversations:
- Fact: "This week you have 7 overdue tasks."
- Impact: "Three clients didn't get the documents they were promised on time, and one wrote a complaint."
- Question: "What's going on? What's getting in the way?"
- Agreement: "Let's redistribute some of your clients, and every day at 5:00 PM you'll check the list of tasks for tomorrow."
Sample phrases
Praise
| Weak | Strong |
|---|---|
| "Well done" | "You replied to the new client in 4 minutes and immediately offered three options — he paid the same day" |
| "Good work" | "You won back a client who left for competitors six months ago — that's a rare result" |
| "Thanks for helping" | "Thanks for picking up Olga's clients while she was ill — nobody was left without a reply" |
Criticism
| Bad | Better |
|---|---|
| "You're constantly late with replies" | "Yesterday three clients waited more than two hours for a reply. What happened?" |
| "You're rude to clients" | "In the conversation with Elena you wrote: “It's written on the website.” She took that as rude. How could you have answered differently?" |
| "You can't sell" | "In the last five refusals, clients left after hearing the price. Let's go through one of those conversations together" |
Where to get facts for feedback
A manager's main problem is that they have no time to read all the conversations and follow all the tasks. So feedback is often built on impressions: who complained loudest, what happened to catch their eye.
| Source of facts | What it gives |
|---|---|
| Conversations with clients | Specific examples of replies |
| Tasks and overdue items | Discipline, workload |
| Response time | Speed of working with leads |
| Conversion and refusal reasons | Where clients are lost |
| Client complaints and ratings | Quality of service |
When this data is collected in one system, the manager comes to the conversation with facts, not feelings. More in the article on controlling sales reps.
How often to give feedback
| Format | Frequency | Example |
|---|---|---|
| Short, in the moment | Right away or within 1–2 days | "Great reply to the client today" |
| In a one-on-one meeting | Every 1–2 weeks | Review of the week, development |
| Summary | Once a quarter or every six months | Evaluation of results, goals |
The more often you give short feedback, the fewer surprises there are in the summary. More on regular meetings in the article on one-on-one meetings.
Feedback from the employee to the manager
Feedback works both ways. Ask regularly:
- what should I do differently;
- which of my decisions are unclear to you;
- where am I getting in the way instead of helping.
If employees are afraid to speak honestly, start small: thank them for any criticism and show that you change something after it.
How to react if the employee disagrees
- Listen. They may have information you don't.
- Go back to the facts. A specific conversation or number settles the "seems — doesn't seem" argument.
- Separate fact from interpretation. Fact — the client waited two hours; interpretation — why.
- Agree on the next step, even if you don't fully agree.
Feedback in writing and for remote teams
When a team works remotely, feedback is often given in writing. It is easy to go wrong here: text without intonation comes across harsher than something said aloud.
| Situation | What's best |
|---|---|
| Praise | In writing is fine, ideally publicly in the team chat |
| A short remark | In writing, but with a question, not a conclusion |
| Serious criticism | Only by voice or video |
| A recurring problem | In a one-on-one meeting, with facts |
An example of a short written remark:
"I looked at the conversation with Elena from Vector LLC — the client asked about timing, and the reply only had the price. Next time, shall we include the timing right away too? If it suits you, we can discuss it at the meeting on Thursday."
Feedback for a newcomer and for an experienced employee
| Newcomer | Experienced employee | |
|---|---|---|
| Frequency | Every day in the first weeks | Every 1–2 weeks |
| Focus | Standards, product, basic skills | Results, development, complex cases |
| Format | Reviewing specific conversations | Discussing approach and goals |
| Tone | More support and explanation | More questions and independence |
It is important for a newcomer to get feedback right away — before a mistake becomes a habit. For an experienced employee, what matters more than instructions are questions that help them see the solution themselves.
Common mistakes
- The "sandwich": praise — criticism — praise. Employees quickly recognize the trick, and the praise loses value.
- Feedback in front of everyone. Criticism is for one-on-one only.
- Comparing with colleagues. "Look at how Anna works" causes resentment, not a desire to grow.
- Too much at once. One or two points that can realistically be fixed.
- No follow-up. A week later nobody remembers the agreement.

How it works in Mestra
Mestra gives the manager facts for feedback without making them read every conversation:
- AI checks reply quality. It flags weak spots in agents' conversations — a rude tone, a missed question, no next step offered — and shows them to the manager.
- Unhappy clients in plain view. AI finds signs of dissatisfaction in conversations — there is a specific example for the discussion.
- Analytics per employee. Response speed, conversion, overdue items, refusal reasons.
- Full history. The employee's conversations, tasks and actions with a client are in the client card.
- Agreements become tasks. What you agreed on in the conversation becomes a task with a deadline and a check.
- AI draft replies. They help the employee write to the company standard right away.
Frequently asked questions
How do I give an employee feedback properly?
Specifically, promptly, about actions and not the person: describe the situation, the behavior and its impact, ask a question and agree on the next step.
What is the SBI model?
A three-step feedback model: situation (when and where), behavior (what the employee did) and impact (what it led to).
How often should I give feedback?
Short feedback right after the situation, detailed feedback in one-on-one meetings every 1–2 weeks, a summary once a quarter or every six months.
How do I praise employees?
Specifically: what exactly the person did and what result it produced. "Well done" works far less well than a description of a specific action.
What if an employee doesn't accept criticism?
Listen to them, go back to the facts, separate fact from interpretation and agree on the next step even without full agreement.
Summary
Good feedback is specific, timely, about actions, with a clear impact and an agreement. Its foundation is facts from the work: conversations, tasks, numbers. Then the conversation is not an argument about feelings but a joint search for a solution.
In Mestra, AI flags weak spots in conversations and unhappy clients, and analytics per employee gives the manager facts for the conversation. Try Mestra free for 15 days at mestra.chat.


