Giving Practical and Effective Feedback to Peers

The Appreciate Step

Starting feedback by recognizing what has been done well is not just politeness. It signals that you have genuinely reviewed the work and makes your colleague more open to hearing what comes next. Identifying real strengths first gives your suggestions a foundation to build on rather than appearing as a list of complaints.

The Build Step

Building on strengths means proposing specific changes that extend what is already working. Rather than vague praise followed by a pivot to problems, you connect your suggestion directly to the existing effort. For example, recommending clear headings for milestone updates turns a strength in content into better structure and readability.

The Challenge Step

The challenge step is where you name a problem clearly and suggest how to fix it. Effective challenges are specific: group related updates, add a short summary after each section, make progress easier to track. Communicating clearly in team discussions helps you frame this as a practical recommendation rather than a criticism of the person.

Keeping Feedback Work-Focused

Effective peer feedback stays directed at the output, not the individual. Pointing to the report itself, not habits or intentions, keeps the conversation constructive. Pairing this with active listening during feedback conversations helps you respond to your colleague's reactions without the discussion becoming personal.

Feedback as a Trust-Building Tool

When feedback is structured, specific, and practical, it does more than improve one deliverable. It shows your colleague that you are invested in their success, which builds the kind of trust that makes future collaboration easier. This connection between good communication and professional conduct at work applies across all peer relationships.

Sam, a business associate, is approached by a teammate who asks for help improving a project update report. Sam decides to use the Appreciate, Build, and Challenge approach to give helpful feedback instead of simply pointing out mistakes. He begins by appreciating the effort and the key updates in the report. He recognizes what has been done well before suggesting improvements. Sam then builds on these strengths by suggesting clear headings for the milestone updates to make the report easier to read. He then points out an area for improvement. He explains that the report is not well organized. This makes it harder to track progress and understand the updates. Next, Sam gently challenges his teammate and offers constructive feedback. He recommends grouping related updates and adding a short summary after each section to make the report easier to read. Throughout the conversation, Sam keeps the discussion focused on the report and offers practical ways to improve it. As a result, Sam helps his teammate improve the report, builds trust, and encourages better teamwork.