7 Essential Feedback Examples for Colleagues

You need to give a colleague feedback, but you hesitate. You worry about sounding unclear, too harsh, or causing a defensive reaction. This common hesitation allows small issues to become significant problems, which negatively affects team morale and project outcomes. Delivering effective feedback is a core skill. It separates competent colleagues from great ones. Vague statements like "be more proactive" or "nice job" do little to reinforce positive behaviors or correct negative ones. They lack the specific detail your coworker needs to understand what to change or continue doing.

This guide provides clear, structured feedback examples for colleagues that you can adapt and use immediately. You will learn how to deliver messages that are direct and supportive. This ensures your points are understood and acted upon. We will break down each example using frameworks like the SBI (Situation-Behavior-Impact) model to show you why they work. Many feedback failures stem from broader communication issues. Learning core principles helps you improve workplace communication and build a better foundation for these specific conversations.

The goal is to move from anxiety to action. These methods help you build trust and improve your team's collective performance. They turn difficult conversations into opportunities for growth and collaboration. You will find specific templates for common workplace scenarios, from recognizing outstanding work to addressing missed deadlines. No more generic advice. It is time for clear, constructive, and actionable communication.

1. SBI Model (Situation-Behavior-Impact)

The SBI model, from the Center for Creative Leadership, is a structured framework for delivering clear, objective, and actionable feedback. It deconstructs your message into three simple parts: the Situation (when and where an event occurred), the specific Behavior you observed, and the tangible Impact it had. This method removes judgment and interpretation. It focuses on observable facts and their consequences. Using SBI is one of the most effective ways to provide helpful feedback examples for colleagues because it separates the person from the problem.

Why This Model Is Essential

The SBI model prevents feedback from sounding like a personal attack. Instead of a vague accusation like, “You dominate meetings,” you present a factual sequence. This approach reduces defensiveness. It opens the door for a productive conversation about solutions. It works well for positive reinforcement and constructive criticism. This makes it a versatile tool for any manager.

How to Use the SBI Model Effectively

Follow this simple structure to build your feedback. Before your conversation, write down each component to ensure you remain focused and objective.

• Situation: Start by setting the context. Be specific about the time and place.
  • Example: “During this morning’s client kickoff call…”
• Behavior: Describe only what you saw or heard. Stick to observable actions, not your interpretation of them.
  • Example: “…when you presented the project timeline, you included specific milestones for their team to review.”
• Impact: Explain the result of the behavior. This can be an impact on you, the team, the project, or the client.
  • Example: “…the client’s marketing director said she felt confident in our plan. This helped us get immediate approval on the first phase.”

Key Takeaway: The power of SBI is in its simplicity and focus on facts. By removing subjective words like "good," "bad," or "disrespectful," you create a neutral ground for discussion. The goal is to describe what happened, not to assign motive.

Actionable Tips for Implementation

To make your SBI feedback successful, consider these tactical points:

1. Deliver it promptly. Feedback is most effective when given close to the event. The details are fresh for both you and your colleague.
2. Use a neutral tone. Your delivery matters. Present the SBI statement calmly and factually, without sarcasm or emotional charge.
3. Pause for a response. After you state the impact, stop talking. Give your colleague space to process the information and share their perspective. This turns a monologue into a dialogue.
4. Prepare for a follow-up. The SBI model is the starting point. Be ready to discuss next steps, ask questions like “What are your thoughts on this?”, or collaborate on a solution.

2. Radical Candor Framework (Care Personally + Challenge Directly)

The Radical Candor framework, created by author and executive Kim Scott, is built on a simple principle: Care Personally while you Challenge Directly. It is a philosophy for giving feedback that balances genuine personal warmth with clear, direct criticism. This approach moves beyond being "nice" to being kind and effective. Providing this type of feedback is a great way to generate actionable feedback examples for colleagues because it builds trust and drives performance at the same time.

Why This Model Is Essential

Radical Candor helps leaders avoid common feedback traps. One trap is Ruinous Empathy, where you care but fail to challenge. This leads to unresolved issues and stagnant growth. Another is Obnoxious Aggression, where you challenge without showing you care. This damages relationships and morale. By combining both dimensions, you create psychological safety. This allows your colleague to hear difficult feedback without feeling attacked. It fosters an environment of trust and continuous improvement.

How to Use the Radical Candor Framework Effectively

Start by establishing your intent to help. Then deliver the feedback directly. Your care for the person gives you permission to be candid about their work.

• Care Personally: Begin by showing you see them as a human being. This creates a foundation of trust.
  • Example: "I value your problem-solving skills, and I want to see you succeed here."
• Challenge Directly: Address the specific issue without sugarcoating. Be clear and to the point.
  • Example: "Your technical work is strong, but how you dismissed Sarah's idea in yesterday's meeting made her hesitant to contribute today."
• Impact + Offer to Help: Explain the consequence and show you are a partner in finding a solution.
  • Example: "I'd like to help you develop your collaborative skills. Let’s talk about some strategies."

Key Takeaway: Radical Candor is not a license for unchecked criticism. It is a commitment to guide and support your colleagues by being honest. Your genuine care must be as evident as your direct challenge.

Actionable Tips for Implementation

To apply Radical Candor successfully, integrate these practices into your communication:

1. Lead with genuine care. Before offering criticism, express your appreciation for the person or their contributions. This sets a supportive tone.
2. Ask for permission. A simple question like, “Can I share something I observed?” respects your colleague’s autonomy and prepares them to listen.
3. Use “I” statements. Frame the feedback from your perspective to show your caring intent. An example is, “I am bringing this up because I care about your growth.”
4. Offer concrete support. Follow up the feedback with tangible help, resources, or a plan. Show you are invested in their improvement, not just pointing out a flaw.

3. Feedback Sandwich (Modified: Strength-Growth-Strength)

The modified Feedback Sandwich is an updated approach to an old method. It delivers constructive criticism without crushing morale. This modern version, often called "Strength-Growth-Strength," sandwiches a single, specific area for development between two genuine and observable strengths. It moves beyond the classic praise-criticism-praise model, which is often insincere. The goal is to provide balanced feedback examples for colleagues. These examples reinforce confidence while clearly identifying a path for improvement. This structure is useful for managers who want to guide their team members constructively.

Why This Model Is Essential

This model works because it frames developmental feedback within a context of recognized value and capability. Starting with a specific strength makes the recipient more open and less defensive. Concluding with a forward-looking statement of confidence reinforces your belief in their ability to succeed. This makes the growth feedback feel like a supportive challenge, not a complaint. It helps maintain a positive relationship while still addressing important areas for improvement.

How to Use the Strength-Growth-Strength Model Effectively

Structure your conversation with this three-part approach. Being prepared helps ensure your message is balanced and the growth point is clear.

• Strength: Start with a specific, sincere compliment about their work.
  • Example: “Your attention to detail on this project is exceptional. I noticed you caught three edge cases the team missed.”
• Growth: Introduce a single, actionable area for improvement. Frame it as a future-focused goal.
  • Example: “For the next sprint, I'd like you to build in a check-in at 50% completion. This will let us adjust the timeline early if needed.”
• Strength: End by expressing confidence in their ability to incorporate the feedback and succeed.
  • Example: “I know you deliver quality work on schedule, and I want to support you in that.”

Key Takeaway: The effectiveness of this model depends on authenticity. The strengths must be real and specific, not generic praise. The growth area should be a single, clear point. Your confidence in their ability to improve must be genuine.

Actionable Tips for Implementation

To make your Strength-Growth-Strength feedback land well, follow these guidelines:

1. Be Highly Specific. Vague praise like “You’re doing great” will make the growth feedback feel like the “real” message. Point to concrete examples of their strengths.
2. Focus on One Growth Area. Piling on multiple criticisms will negate the model’s benefits. Stick to the most important point for that conversation.
3. Tie Confidence to Capability. When expressing your belief in them, connect it to their known skills. For example, “Your problem-solving skills make me confident you can master this.”
4. Use for Regular Check-ins. This model is excellent for ongoing development in 1-on-1s, not just for addressing problems. This normalizes developmental feedback.

4. SMART Goals Framework (Specific, Measurable, Achievable, Relevant, Time-bound)

The SMART framework transforms feedback from a simple observation into a forward-looking development plan. While feedback identifies a gap, SMART goals build the bridge to close it. The acronym stands for Specific, Measurable, Achievable, Relevant, and Time-bound. This creates clear, trackable outcomes. This structure is essential for turning abstract feedback like "you need to improve communication" into a concrete action plan. It is one of the most effective tools for providing helpful feedback examples for colleagues.

Why This Model Is Essential

Effective feedback loses its value if it does not lead to action. The SMART framework provides the structure to ensure that a constructive conversation results in a tangible plan. It shifts the focus from a past problem to a future solution. It gives the employee a clear path to improvement. This method promotes ownership and accountability because the goals are well-defined and progress can be objectively tracked.

How to Use the SMART Model Effectively

Use this structure to convert feedback into a clear, actionable goal. The key is to collaborate with your colleague to define each element. This ensures their buy-in.

• Specific: Clearly define what needs to be done. Who is involved and what is the desired outcome?
  • Feedback: "Your code reviews are too brief."
  • Specific Goal: "Provide written feedback on 100% of assigned pull requests."
• Measurable: How will you track progress and success? Use numbers, percentages, or frequencies.
  • Goal Element: "...with at least 2-3 specific observations per review."
• Achievable: Is the goal realistic given the person’s skills and available resources? The goal should be a stretch but not impossible.
• Relevant: Does this goal align with the employee's role, team objectives, and the company's needs?
• Time-bound: When will the goal be completed? Set a clear deadline or timeline.
  • Goal Element: "...within 24 hours of assignment, for the next quarter. We'll track this in our monthly check-ins."

Key Takeaway: SMART goals provide the "how" after the "what." They are a shared roadmap created after a feedback discussion. They ensure both manager and employee are aligned on the exact steps needed for growth.

Actionable Tips for Implementation

To make your SMART goals successful, consider these tactical points:

1. Involve the employee. Co-creating the goal is critical. Ownership drives commitment, so ask them for ideas on how to address the feedback.
2. Schedule regular check-ins. Do not wait until the end of the quarter. Weekly or biweekly meetings to review progress keep the goal top-of-mind and allow for adjustments.
3. Link goals to business impact. Explain how achieving this personal goal contributes to the team's or company's success. This adds motivation and context.
4. Celebrate progress. Acknowledge when milestones are met. Recognizing the effort maintains momentum and reinforces positive changes. To better understand how to apply this to performance management, you can find more information about SMART goals here.

5. Feedforward Approach (Focus on Future Potential vs. Past Mistakes)

The Feedforward approach, developed by executive coach Marshall Goldsmith, shifts feedback from a review of past mistakes to a collaborative discussion about future potential. Instead of analyzing what went wrong, this method asks, "What could go right?" It positions you as a coach helping your colleague envision and achieve success. This technique offers productive feedback examples for colleagues. It is useful in developmental contexts where growth is the primary goal.

Why This Model Is Essential

Feedforward bypasses the defensiveness that often accompanies criticism about past actions. The past is unchangeable, so feedback can feel like an accusation. This approach is constructive and empowering. It focuses on future possibilities the employee can control. It is effective for high-potential team members. It promotes a growth mindset and maintains positive momentum.

How to Use the Feedforward Approach Effectively

Frame the conversation around future aspirations and solutions. Acknowledge a strength first, then pivot to what is possible next.

• Acknowledge a Strength: Start by recognizing a positive quality or skill.
  • Example: “You have great individual technical skills.”
• Pose a Forward-Looking Question: Ask an open-ended question that prompts brainstorming about future actions. Avoid disguised criticism.
  • Example: “The next level for you is amplifying others. What's one way you could bring others into your problem-solving process in the next sprint?”
• Collaborate on a Vision: Work with your colleague to define what success looks like and what support they need.
  • Example: “You clearly care about quality. Moving forward, what support would help you deliver on time and maintain your quality standards? How could we adjust our process?”

Key Takeaway: Feedforward is about coaching for future success, not critiquing past performance. The focus is entirely on "what's next." This makes it a positive, motivating tool for professional development.

Actionable Tips for Implementation

To apply the feedforward method successfully, keep these points in mind:

1. Lead with genuine appreciation. Start by recognizing a real strength to build trust and show you see their potential.
2. Ask open-ended questions. Use prompts like “What if…” or “How could…” to invite creative thinking and co-ownership of the solution.
3. Partner in planning. Work together to create a vision for the future. The conversation is about shared goals, not top-down directives.
4. Connect to concrete goals. Pair the feedforward discussion with SMART goals to ensure the ideas translate into measurable actions and clear follow-through. You can explore detailed strategies on how to give feedback effectively for more guidance.

6. Observation-Based Feedback (What I Noticed vs. What I Think)

This method separates what was objectively observed from your interpretation or judgment. It creates space for dialogue rather than a one-sided declaration. Instead of labeling a colleague’s behavior, you describe what you noticed and then invite their perspective. This approach is rooted in frameworks like Nonviolent Communication. It is valuable for reducing personal bias and promoting psychological safety, especially when giving difficult feedback examples for colleagues.

Why This Model Is Essential

Observation-based feedback prevents you from making assumptions about a person's intent. When you lead with an interpretation like, “You seem disengaged,” your colleague’s natural response is to defend their internal state. By starting with a factual observation, you present neutral data that is hard to dispute. This opens a conversation about their experience and context. This is effective for sensitive topics where your perception might not match their reality.

How to Use Observation-Based Feedback Effectively

Frame your feedback as a two-part statement: a neutral observation followed by a genuine question. This structure shows respect for your colleague's perspective.

• Observation: State the specific, observable behavior you witnessed. It should be something you could record on video.
  • Example: “I noticed in the last week you submitted your project components without checking in with the frontend team.”
• Curiosity: Ask a question to understand their point of view. Avoid leading questions that imply a correct answer.
  • Example: “Help me understand. Was there a time constraint, or did you have a different approach in mind?”
• Invitation: Open the floor for collaboration on a solution.
  • Example: “What would a more collaborative process look like to you?”

Key Takeaway: The goal is to describe what happened and then ask for clarity. This transforms a potential confrontation into a problem-solving session. You are not an accuser. you are a curious partner seeking to understand.

Actionable Tips for Implementation

To make your observation-based feedback productive, follow these guidelines:

1. Stick to the facts. Describe actions, not attitudes. Instead of saying, “You have a bad attitude,” try, “I observed your tone shifted when the budget was discussed.”
2. Use "I" statements. Begin with “I noticed…” or “I observed…” to own the perception as yours without presenting it as an absolute truth.
3. Pause and genuinely listen. After you ask your question, give your colleague ample time to respond. Their context is the missing piece of the puzzle.
4. Be prepared to adjust your view. Your observation is only one data point. The colleague's explanation might change your understanding of the situation completely. Improving your coaching skills as a manager helps you navigate these conversations effectively.

7. Appreciation + Development (A+D) Model

The Appreciation + Development (A+D) Model is a framework that separates feedback into two distinct conversations. Instead of combining positive and negative points in a single meeting, you deliver Appreciation to recognize what works and Development to address growth areas in separate, dedicated interactions. This approach builds psychological safety. It prevents the "feedback sandwich," where praise feels like a setup for criticism. Using A+D provides clear and impactful feedback examples for colleagues by ensuring each message has a singular, focused purpose.

Why This Model Is Essential

Mixing appreciation and development often dilutes both messages. Employees may brace for the "but" after hearing praise, which undermines the recognition. The A+D model allows appreciation to be genuine and fully absorbed. It also ensures developmental feedback is given the focus it deserves. This leads to a more productive dialogue about growth without the emotional confusion of mixed signals.

How to Use the A+D Model Effectively

Structure your feedback by intentionally planning separate conversations for each purpose. This requires a conscious effort to decouple recognition from critique.

• Appreciation Conversation: Dedicate a specific time to recognize a positive contribution.
  • Example: "I wanted to take a moment to recognize your work on the client proposal. Your attention to detail and how you anticipated their questions showed real thought and professionalism. This is the kind of work that builds client trust."
• Development Conversation (Held Separately): Schedule another time to discuss an area for improvement.
  • Example: “I want to discuss something I've noticed about our project timelines. In the last two sprints, you submitted your work at the last minute. This puts pressure on the QA process. Let's talk about what would help you build in a buffer.”

Key Takeaway: The A+D model's strength comes from its intentional separation. By creating dedicated spaces for both appreciation and development, you build trust and ensure each type of feedback is received clearly and constructively.

Actionable Tips for Implementation

To make your A+D feedback successful, consider these tactical points:

1. Establish a rhythm. Make appreciation a regular habit, such as weekly or biweekly. Schedule development conversations monthly or as needed, so they feel like a normal part of performance management.
2. Make appreciation detailed. Do not just say "good job." Explain the specific behavior and its positive impact. This makes the recognition more meaningful.
3. Set clear expectations. Let your team know this is your approach. You can say, "My role is to recognize what's working and help you grow, so we will have separate conversations for each."
4. Use clear subject lines for remote teams. Label communications to manage expectations. For example, use "Recognition: Your Impact This Week" for appreciation and "Development Conversation: Let's Discuss Upcoming Goals" for growth talks.

Comparison of 7 Feedback Approaches

Turn Your Feedback into Action Today

You now have a complete toolkit of frameworks for giving better feedback. This article provided numerous feedback examples for colleagues. It moved beyond simple praise or criticism. It detailed structured methods like the SBI model, Radical Candor, and the feedforward approach. Each framework offers a specific path to turn potentially difficult conversations into productive, growth-oriented discussions.

The core lesson is this: effective feedback is a skill, not an innate talent. You develop it through preparation and practice. The examples we analyzed demonstrate how a clear structure removes ambiguity and reduces defensiveness. Whether you are recognizing a major success or addressing a missed deadline, your delivery determines the outcome. A well-prepared message builds trust. A poorly delivered one erodes it.

From Theory to Practice: Your First Step

The goal is not to master all seven frameworks at once. The key is to start small and build momentum. Your immediate next step is to choose one method and apply it.

• For positive reinforcement: Try the Appreciation + Development (A+D) model to celebrate a win while also suggesting a future opportunity.
• For corrective feedback: Use the SBI (Situation-Behavior-Impact) model to provide objective, non-confrontational observations.
• For future-focused goals: Apply the SMART framework to help a colleague define clear, actionable objectives for their next project.

Select the framework that best fits your immediate need and your personal communication style. Before your next one-on-one, spend ten minutes preparing your talking points using that structure. Notice how it changes your confidence and the conversation's tone. You are no longer just reacting. You are leading a constructive dialogue.

Building a Culture of Continuous Feedback

Giving great feedback is only one side of the equation. Creating a team culture where feedback is expected and welcomed is the ultimate goal. When feedback becomes a regular, normalized part of your workflow, it loses its intimidating edge. It becomes a tool for continuous improvement, not a prelude to a problem.

Consider these strategic actions to build this culture:

1. Model the Behavior: Actively ask for feedback on your own performance from your colleagues and direct reports. When you receive it, thank the person and act on their suggestions where appropriate. This shows you value their perspective.
2. Systematize Recognition: Make appreciation a formal part of your team's process. The "Appreciation" component of the A+D model is critical. To implement this systematically, consider using an effective employee recognition program template to ensure positive contributions are consistently highlighted.
3. Train Your Team: Share these frameworks with your colleagues. When everyone speaks the same language, like SBI, feedback sessions become more efficient and less personal. It creates a shared understanding of how to communicate effectively.

By taking these steps, you transform feedback from a dreaded annual review event into a daily practice of mutual support and growth. You build psychological safety, where team members feel secure enough to take risks, admit mistakes, and help each other improve. The actionable feedback examples for colleagues in this guide are your starting point for building that environment. Your commitment to applying them is what will make the difference.

Stop worrying about finding the right words for tough conversations. PeakPerf guides you through proven feedback frameworks like SBI and SMART goals. It helps you draft clear, fair, and effective messages in minutes. Turn preparation anxiety into leadership confidence with PeakPerf.