Feedback often gets delayed because a manager is trying to find the perfect words. In the meantime, a strong piece of work goes unrecognized, a missed expectation becomes a pattern, or an employee is left guessing about where they stand. Useful feedback does not require a polished speech. It requires attention to a real moment and enough clarity for the other person to do something with it.

The examples in this guide are starting points, not scripts to recite word for word. The goal is to help a manager describe what happened, explain why it mattered, and invite a productive next step. That approach gives people information they can use without turning every conversation into a formal review.

That rhythm matters. Gallup reports that employees who say they received meaningful feedback in the previous week are far more likely to be engaged, and its guidance defines meaningful conversations as including recognition, goals, priorities, strengths, and collaboration. Gallup’s research on effective feedback is a useful reminder that feedback is part of everyday leadership, not an annual event.

Start with a simple feedback structure

Before choosing an example, use a structure that keeps the conversation tied to the work: name the situation, describe the behavior you observed, explain the impact, and agree on what happens next. This Situation, Behavior, Impact approach gives people a factual frame instead of a vague label, and it keeps the conversation focused on a clear standard rather than a manager’s general impression.

For example, “You need to communicate better” leaves a person to interpret the problem. “In Tuesday’s project update, the deadline change was not mentioned until the last minute. The design team lost a day of planning time. Before the next update, send the changed date and the reason as soon as you know it, then let’s review the handoff Friday” gives the person something concrete to understand and act on.

A strong feedback conversation has room for the employee’s view. Ask, “What was happening from your perspective?” or “What would make this easier to do next time?” That question does not erase the standard. It helps the manager learn whether the issue is unclear expectations, a missing resource, a competing priority, or something else that needs attention.

Positive employee feedback examples

Specific recognition tells people which behaviors to repeat. It should not sound like a generic compliment pasted into a performance review. Notice the action, connect it to the outcome, and make the value visible to the person and the team.

When someone solves a problem early

“I noticed you raised the supplier risk before it affected the delivery date. That gave the team time to adjust the plan instead of reacting at the last minute. Thank you for bringing forward a solution, not just the problem.”

When someone helps a teammate succeed

“You took time to walk Jordan through the reporting process even though you had a full week. That helped them get confident faster and kept the work moving. Your patience made a real difference.”

When someone improves the quality of their work

“The client summary was much clearer this time. You led with the decision, showed the key risk, and made the next step easy to find. That made it easier for everyone to respond quickly.”

When someone handles a difficult customer or colleague well

“In that tense conversation, you stayed calm, listened without interrupting, and brought the discussion back to the issue we needed to solve. That helped protect the relationship while still moving the work forward.”

Recognition works best when it is close to the moment. It also becomes more credible when a manager can name the actual behavior instead of only the outcome. Michael’s guide to effective communication for managers offers more ways to make day-to-day expectations and follow-up clear.

A manager recognizing a colleague’s contribution during a team meeting

Constructive employee feedback examples

Constructive feedback is not a softer word for criticism. It is information meant to help someone improve a behavior or result. Keep it private when the concern involves a mistake, performance gap, or sensitive situation. Focus on what you saw, not a conclusion about the person’s attitude or character.

When a deadline is missed

“The draft was due Thursday and arrived Monday, which meant the team could not complete its review on time. I want to understand what got in the way. Going forward, let me know as soon as the date is at risk, then we can decide what to adjust before the delay affects others.”

When work lacks the needed detail

“The proposal covered the main idea, but it did not include the budget assumptions or a recommendation. Without those details, the leadership team could not make a decision. For the revision, add those two pieces and send me a short outline before you draft the next one.”

When someone interrupts or dominates a meeting

“In today’s meeting, you stepped in before two colleagues had finished explaining their view. That made it harder for the group to hear the full picture. In the next discussion, pause after someone speaks and ask one question before offering your own recommendation.”

When communication is unclear

“Your update included useful background, but the decision and the owner were not clear. The team left with different assumptions about what would happen next. For future updates, start with the decision, the owner, the due date, and the next check-in.”

Being direct does not mean being cold. The American Psychological Association notes that people often underestimate how much others want constructive feedback, which helps explain why managers avoid conversations that could be useful. The APA’s summary of this research is a helpful nudge to have the conversation while the details are still fresh.

Two colleagues having a respectful constructive conversation at an office table

Examples for feedback in common leadership moments

After a presentation

“Your opening made the recommendation clear, and you handled the questions with confidence. One opportunity for next time is to pause after the data slide so the audience can absorb the main point before moving into the details. Let’s build that pause into the next presentation together.”

During a one-to-one

“You have been carrying a heavy workload and still meeting the core commitments. I also noticed that the longer-term planning work has slipped. Which responsibility should we adjust so you have enough room to do both well?”

When a new employee is learning the role

“You handled the customer call with a steady tone and asked the right questions. For the next call, practice summarizing the customer’s request before offering options. That will help them feel heard and make the handoff cleaner.”

When teamwork breaks down

“The handoff between your teams was not clear, and the work was duplicated. Rather than assigning blame, let’s map what each team needs before the next handoff. You can start by agreeing on one owner, one due date, and one place to record the decision.”

For situations where a conversation has already become tense, use Michael’s guide to difficult conversations at work. It can help a manager prepare, describe the issue plainly, listen for the other person’s view, and leave with a workable agreement.

A short checklist before the conversation

Take two minutes to prepare before you speak. First, identify one situation rather than a general impression. What happened, and when? Second, separate what you observed from the story you are telling yourself about why it happened. “The update arrived after the deadline” is an observation. “They do not care about the project” is an assumption that will make the conversation harder to start well.

Third, decide what outcome you need. You may want to reinforce a behavior, clarify a standard, understand an obstacle, or agree on a new approach. A conversation with a clear purpose feels more respectful than a collection of disconnected comments. Finally, prepare one genuine question and one next step. The question invites useful context. The next step makes it clear that feedback is connected to real work, not just a manager’s opinion.

If you are frustrated, give yourself enough time to get specific before the conversation. Waiting a few minutes to organize your thoughts is different from avoiding the issue for weeks. The goal is not to remove emotion or make the conversation sound mechanical. It is to arrive able to describe the work fairly, listen carefully, and stay focused on a useful outcome.

What to avoid when giving feedback

Feedback loses its value when it is too vague, too late, or too broad to act on. Skip labels such as “lazy,” “unprofessional,” or “great attitude.” They force people to guess which behavior you mean. Replace them with what happened, where it happened, and the effect it had on the work.

Avoid collecting several months of small frustrations and delivering them in one sitting. That can feel less like coaching and more like a surprise case against the employee. Address patterns when you see them, then use a later review to notice progress and set broader goals.

Do not use praise as a disguise for an unrelated correction. “You are doing great, but…” often teaches people to wait for the criticism. Recognition and course correction can both be direct. Give each its own clear moment.

Finally, do not end with a vague request to “do better.” Decide together what good looks like, what support is needed, and when you will check back. For a manager, that follow-through is part of the feedback. For an employee, it is proof the conversation was meant to help, not simply to document a problem.

Turn examples into a reliable habit

Choose one weekly moment to notice what is working, what is unclear, and where someone needs support. A five-minute check-in can be enough if it is specific and honest. Before the conversation, write down the situation, the behavior, the impact, and one question you need answered. That simple preparation keeps a manager from rambling or reacting in the moment.

Then close the loop. If you agreed on a next step, ask about it at the next check-in. If the employee raised a barrier, provide the promised answer or say when it will be available. These small acts of follow-through build the kind of manager-employee communication that makes people more willing to raise concerns early.

For a broader framework, see Michael’s guide to manager-employee communication and his practical article on improving management communication. Both help leaders turn clear conversations into a dependable team rhythm.

How Michael helps teams build better feedback habits

Feedback becomes easier when a team has a shared language for communication, expectations, and differences in work style. Michael’s leadership training gives organizations practical ways to build those habits across managers and teams. His DISC training for teams helps colleagues better understand how different people prefer to receive information, raise concerns, and make decisions.

For leaders who need focused support around a people challenge or a new level of responsibility, Michael’s coaching and consulting creates space to practice these conversations and build a clear next step.

Make feedback a tool for growth, not guesswork.

Explore leadership training, DISC workshops, and coaching with Michael R. Morgan.

Book Michael

Frequently asked questions

What is an example of good employee feedback?

Good employee feedback names a specific action, explains why it mattered, and gives the person a clear sense of what to continue or change. For example: “In yesterday’s client meeting, you paused to confirm the decision before moving on. That kept the team aligned and prevented a later misunderstanding. Keep using that same check when the plan changes.”

How do you give constructive feedback without discouraging someone?

Keep the conversation tied to an observable situation and the work, not the person’s character. Explain the impact, ask for their perspective, and agree on one next step. Direct feedback can still be respectful when it gives someone a fair chance to understand and improve.

How often should managers give employees feedback?

Managers should not save feedback only for formal reviews. Useful feedback happens close to the work, when details are fresh and a person can still act on it. A dependable weekly check-in gives managers a natural rhythm for recognition, priorities, support, and course correction.