How to Give Feedback to Employees: Steps and Examples

Feedback to employees is not a verdict on a person. It is a short, planned conversation in which you describe one specific behavior, name its impact, and agree on what changes and by when. Knowing how to give feedback to employees comes down to that order: observation first, judgment never, agreement last. A performance review grades a year. Feedback steers next week.

Three things make the difference: an observation with a number, a question you do not know the answer to, and an agreement with a date. This guide walks through all three with Dana, a sales manager who leads six inside sales reps at a software reseller, and Luis, her top rep, who books more demos than anyone and loses almost half of them. You also get four steps for the conversation, a one-page prep template, twelve constructive feedback examples, eight positive ones, and a list of what not to say.

What feedback to employees is, and what it is not

Feedback has a trigger, a topic, and a result. The trigger is something you observed that affects a goal. The topic is one behavior, not the whole person and not the whole quarter. The result is an agreement both of you can repeat in one sentence. Drop any of the three and the conversation turns into something else: without a trigger it is small talk, without a topic it is a lecture, without a result it is venting.

Feedback is not only criticism, either. Anyone who schedules a feedback conversation only when something breaks teaches the team to dread every calendar invite. Positive feedback follows the same rules. It is specific, it names the impact, and it tells the person what to keep doing.

Four kinds of conversation tend to blur together. None of them is wrong, and each one is built for something else. The only question is: which one fits what you saw?

The feedback conversation is the smallest and fastest of the four. It needs no form from HR and no two weeks of notice. It only needs a trigger that is still fresh. Whoever saves feedback for the annual review delivers a bank statement in December about things nobody remembers clearly. That means: the review summarizes, feedback steers. How feedback, goals and the review fit into one yearly cycle is the subject of performance management.

Giving feedback to employees: how often and where

There is no magic number, but there is a rule of thumb. Give constructive feedback within a week of what happened and positive feedback the same day. On top of that, run a rhythm. For Dana's team of six, every rep gets at least one piece of goal-linked feedback a month, usually inside the weekly one-on-one. A separate meeting is only worth it when the topic needs more than five minutes or when it might sting.

Where? Criticism happens in private, always, in a room with a closed door or on a video call with nobody else in it. Never in a hallway, never in a team chat thread. Praise can be public if the person is comfortable with that. And how long? 15 to 30 minutes for one topic. Anyone who regularly needs longer has brought more than one topic or is circling the point.

Why most feedback misses: opinion is not feedback

Most feedback does not fail because of tone. It fails because an opinion is dressed up as feedback. “You need to slow down” is an opinion. The employee can agree or disagree, but there is nothing to do with it. An observation with a number gives them something to work with.

Here is what that looked like for Dana. Luis, 27, has been on her team for 14 months and tops the leaderboard for demos booked. Every demo he books goes to one of two account executives, who block 45 minutes for it. In late September Dana pulled the numbers from the CRM:

The table tells two stories. The first is good: Luis still holds more demos than the average rep. The second is expensive: eleven demos did not happen, and each one blocked 45 minutes of an account executive's calendar. That is more than eight hours of selling time in one month, gone. Dana then opened all eleven no-shows. Nine had no confirmation of any kind in the 24 hours before. Eight had been booked more than two weeks out.

Now Dana has a finding instead of a feeling. “You need to slow down” would have been wrong, because speed is not the problem. The problem is a behavior: Luis books far out and does not confirm. Whoever skips the counting before a feedback conversation criticizes the wrong thing and often praises the wrong thing too.

There is something else in the numbers. In August Luis ran a subject line test on cold emails, and the whole team now uses his winning version. Reply rates went from 4 to 7 percent. That deserves feedback as well, its own feedback, at its own time. When did Luis last hear a thank-you that was more specific than “great job”?

How to give feedback to employees in four steps

How do you give feedback to employees so that something actually changes? With a fixed order that you keep for every topic. The order protects both sides. It keeps you from judging too early, and it keeps the employee from defending against something you have not said yet. One topic takes 20 to 30 minutes.

1. 01

   Open with the topic, one minute

   Say what this is about and how long it will take in your first sentence. No small talk as padding, no compliment as a warm-up. Anyone who circles the topic for ten minutes builds the exact tension they wanted to avoid.

2. 02

   Describe the situation and the behavior, five minutes

   When and where, then what the person did, with a number if you have one. Use I-statements: “I looked at all eleven no-shows from September.” No adjectives about the person, no guesses about motives.

3. 03

   Name the impact, then ask, ten to fifteen minutes

   Say what the behavior caused for a customer, a colleague, or a goal. Then ask one open question and listen to the full answer without jumping in. Repeat back what you heard before you respond. This is where you learn whether the problem sits with the person or with the system.

4. 04

   Agree on one change and a date, five minutes

   Agree on exactly one change you can both measure, and put the follow-up on the calendar before you leave the room. Ask the employee to say the agreement in their own words. Whatever they cannot repeat was not agreed.

The example: Dana and Luis on a Tuesday at 10 a.m.

Dana opens without a detour: “I want to talk about demo no-shows. I have 30 minutes, and at the end I want us to agree on one thing.” Then the behavior: 26 demos booked in September, 15 held, a show rate of 58 percent against a team average of 81. Nine of the eleven no-shows had no confirmation, and eight were booked more than two weeks out. Then the impact: more than eight hours of account executive time lost, and the team's fourth-quarter goal, an 80 percent show rate, is out of reach if one of six reps sits at 58.

Then she asks: “What does a good week look like to you?” Luis does not hesitate. “Booked demos. That's what the leaderboard shows, and that's what the $25 bonus pays for.” That is the moment the conversation turns, and it turns the right way. The bonus pays for booked demos, not held ones. Dana set it up that way in January. Luis optimized exactly what she paid him to optimize.

The agreement is easy after that, and it has two sides. Luis books demos no more than seven days out and confirms each one the day before, by email with the invite and by text message. Dana switches the bonus to held demos starting October 1, for all six reps. The October goal for Luis: a show rate above 70 percent. The follow-up is in four weeks and takes 15 minutes. And the praise for the subject line test? Dana gave it on Monday in the team meeting, with the numbers. It does not belong in this conversation, where it would read as padding.

Length: 24 minutes. Result: one behavior, one number, one date. And one finding Dana did not expect, which was her own part in it. Whoever really listens in a feedback conversation almost always gets feedback back.

Ad

Prosp

Prosp · LinkedIn outreach

3 interested buyers in 30 days, or 3 months freeLinkedIn messages so personal, prospects actually replyYour campaign goes live within 48 hours

Try for free→

New reply

Hi Anna, your post on remote sales got me curious.

Sounds interesting. Does Thursday work?

How to prepare in ten minutes: a one-page template

Preparing for feedback does not mean writing a script. It means answering a handful of questions in writing before you send the invite. Ten minutes is enough when the numbers are already in front of you. Without numbers you do not need more time. You need a different trigger.

The open question row matters most and gets skipped most. Whoever walks in with a finished explanation only listens for agreement. Whoever walks in with a real question finds out why the behavior made sense to the other person. And it almost always made sense, otherwise they would not have done it.

Keep the invite short and name the topic. “I'd like 30 minutes on Tuesday to talk about demo no-shows” is fair. “Can we talk?” is not, because it leaves the employee alone with the worst case for two days. In short: the topic goes in the invite, the observation goes in the conversation, and the agreement goes in writing.

Constructive feedback examples: twelve situations, said well

What are good examples of constructive feedback? They all share one shape: a situation, a behavior, an impact, and a request or a question. The table shows twelve common situations, the sentence most managers reach for first, and a version that gives the employee something to act on. Swap in your own numbers.

Notice what the right column never contains: adjectives about the person. “Careless,” “rude,” and “unfocused” are verdicts. A verdict invites a defense. A number invites a fix. Anyone who catches themselves reaching for an adjective has not finished preparing yet.

Employee feedback examples: positive feedback that names what to repeat

Praise fails at the same spot as criticism: it is too vague to act on. “Great job” feels good for a minute, but it does not say what to keep doing. Positive feedback follows the same shape, and the request becomes: more of exactly this. Here are eight employee feedback examples you can adapt.

• “Your subject line test lifted our reply rate from 4 to 7 percent, and the whole team uses it now. Run one more test in October.”
• “You walked the new hire through the CRM without being asked. She logged her first demo in week two. That is exactly how I want onboarding to look.”
• “In Thursday's pricing call you raised the budget question before the client did. Do that again in next week's renewal.”
• “Your summary after the outage was out within an hour, with three next steps. Nobody had to ask twice.”
• “You pushed back on the launch date with data, not with a complaint. We moved it by a week and shipped clean.”
• “You closed the loop with the customer who complained in May. She renewed for two years.”
• “Your weekly notes are short and start with the decision. I read them first every Monday.”
• “You said no to the side project and kept the onboarding fix on track. That was the right call, and I noticed.”

Two rules keep praise useful. Give it the same day, while the person still remembers what they did. And keep it separate from criticism, so it does not become the opening act for a “but.” That means: praise that arrives on its own is believed, and praise that arrives right before bad news is discounted.

What not to say when giving feedback

Some sentences sound harmless and still wreck the conversation. Each line below has a reason it backfires and a better option to use instead.

The common thread is easy to spot. Every bad line either judges, generalizes, or hides the point. Every good line describes something both of you can check. Is there a line in the left column you used last month?

The three mistakes nobody notices

Most feedback does not fail because of bad intent. It fails because of well-meant habits, and none of these three feels like a mistake in the moment. Which one is yours? The most common one gets its own box, the other two follow below.

• Saving it up. Collecting observations for the annual review feels thorough. To the employee it feels like an ambush, because they never had a chance to change anything. Any observation older than four weeks has missed its feedback conversation.
• No follow-up date. The talk went well, both of you leave relieved, and four weeks later nobody remembers exactly what was agreed. An agreement without a date is a wish. The follow-up takes 15 minutes and goes on the calendar before you leave the room.

One more pattern deserves a name, even though it is not a mistake in the conversation itself. Some behavior is not a character trait. It is a reasonable answer to what gets measured and paid. Luis did not book far out because he was careless. He did it because the bonus paid for bookings. Anyone who fixes only the person and not the incentive will have the same conversation in three months with the next rep.

From feedback to goals: year, quarter, month, week, day

A feedback conversation ends with an agreement. Whether it holds is decided in the four weeks that follow, not in the room. For that, the agreement has to land where the work happens, in the week and the day. And it has to hang from something bigger than the conversation.

For Dana and Luis the chain looks like this. The team's goal for 2026: 140 new customers. The fourth-quarter goal: an 80 percent show rate across the team. Luis's October goal: a show rate above 70 percent. His weekly goal: every Friday, check next week's demos and reconfirm any booked more than seven days ago, 20 minutes. His daily goal: send confirmations for tomorrow's demos before 10 a.m.

Did it work? At the follow-up in late October, Luis had booked 22 demos and held 16, a 73 percent show rate, just above his monthly goal. In November he held 18 of 22, or 82 percent. He books fewer demos than before and holds more of them, and the account executives got back more than five of the eight lost hours. That means: the feedback did not slow Luis down. It pointed his speed at the number that pays.

Without the chain it would have gone differently. The agreement would have lived in a note, and nobody reads notes between meetings. With the chain, the daily step sits where Luis looks every morning. For how to phrase a step so it can be checked off at night, see the guide to daily goals. For how to turn a monthly goal into a number with a date, the SMART goals examples show the pattern.

In Gaapp those five levels are the core: every goal hangs from a bigger one, and progress per period is the share of goals done. Dana and Luis share a space where both see the same status, as described in shared goals in a space. The follow-up then starts with a number instead of “so, how's it going?” If you want the method behind the chain from the ground up, read how to achieve goals.

Three questions about your last feedback conversation:

• Could you back up the observation with a number or a date?
• Did you ask a question you did not already know the answer to?
• Is the follow-up on the calendar, and do you know which number you will look at?

Anyone who answers no to one of them was not too harsh or too soft, just too vague. In short: feedback to employees is not a verdict on what happened. It is an agreement about what happens next.

Frequently asked questions about giving feedback to employees