Giving Respectful Feedback on a Colleague’s Work

Give feedback on a colleague’s work by describing a specific observation, its effect and a useful question or next step. Focus on the artefact or behaviour rather than guessing motives. Respectful feedback can be direct: the aim is to make improvement possible, not to hide the concern behind vague praise or turn a work discussion into a judgement of the person.

A practical approach to the situation

Check the purpose and context before commenting. Are you the reviewer, a collaborator or someone affected by the output? Choose an appropriate time and channel, especially for sensitive concerns. Describe what you observed in concrete terms and explain the practical impact. Distinguish a requirement from a personal preference.

Invite the colleague’s perspective because you may be missing a constraint or decision. Discuss an option or desired outcome rather than assuming your preferred solution is the only valid one. Give positive feedback with the same specificity when it helps someone understand what worked. Avoid public embarrassment, exaggerated words such as always and never, or claims about intention that the evidence does not support.

A fictional workplace or interview example

Fictional example: a reviewer finds that a report’s chart uses a different date range from the summary. Instead of saying, “You are careless,” she identifies the two ranges and explains that the mismatch could change the interpretation. She asks whether the difference was intentional and suggests reconciling the period or labelling the distinction.

The colleague explains that one source arrived late, and they agree on a clearer note and a revised comparison. The feedback addresses a real issue without inventing a motive. The discussion also reveals context that the reviewer would have missed if she had treated her first interpretation as certain.

Observation

Show: Name the specific work or behaviour you saw

Check: Avoid labels about personality or intention

Impact

Show: Explain the effect on the task, reader or team

Check: Distinguish a real consequence from speculation

Dialogue

Show: Ask for context and agree a useful next step

Check: Do not present preference as the only acceptable solution

Apply the process to your own material

1. Check: Understand your role, the work’s objective and the appropriate channel.
2. Describe: State a specific observation and why it matters.
3. Listen: Invite context and examine alternatives without personal blame.
4. Agree: Clarify the change, owner or next review step where needed.

Practise with a genuine experience you can discuss appropriately, or use an explicitly fictional scenario. Ask a partner to describe what they understood, including the decision or next action. Compare their interpretation with your intention and revise the part that caused confusion. Keep facts, assumptions and proposed actions distinct. If the situation involves a real employer, follow its assessment instructions or workplace processes rather than treating a practice example as permission to ignore them.

1. Check

   Understand your role, the work’s objective and the appropriate channel.

2. Describe

   State a specific observation and why it matters.

3. Listen

   Invite context and examine alternatives without personal blame.

4. Agree

   Clarify the change, owner or next review step where needed.

Use the sequence as a guide, then adapt it to the actual question, people and constraints. Clear communication should make the next decision easier.

Check the result and the next action

Before giving feedback, check whether you can point to the evidence and explain why it matters. Remove personal labels and unsupported assumptions. After the discussion, clarify any agreed action and ownership. If the issue involves serious conduct or a process beyond peer review, use the appropriate workplace route rather than expecting an informal feedback formula to resolve every situation.

A closer check that improves the approach

Prepare the feedback in two versions: the raw reaction and the observable statement. A raw reaction might be that a document feels careless; the observable statement might be that two totals use different periods and the difference is not labelled. Use the second version in the discussion. It gives the colleague something to inspect and correct, while leaving room for context you do not yet know. This exercise does not require making the issue sound smaller than it is. It makes the concern more precise, which can support a firmer and fairer conversation about its actual impact.

Common questions

Should feedback always begin with praise?

Not necessarily. Genuine positive feedback can be useful, but formulaic praise may obscure the concern. Be respectful and clear about the purpose. Describe what worked when it matters, and address the issue directly with evidence. Do not use a compliment as a disguise for a personal criticism or a way to avoid explaining the actual problem.

How do I distinguish a preference from a requirement?

Connect the comment to the brief, audience, standard or agreed constraint. If it is your personal preference, label it as an option rather than a mandatory correction. Ask about the reasoning behind the current choice. This helps the colleague evaluate the feedback instead of treating every taste difference as a defect in the work.

Can I give feedback to someone more senior?

It may be appropriate when the issue affects the work and you use a respectful, suitable channel. Describe the evidence and impact rather than challenging status. Organisational context matters, so use the relevant process for sensitive concerns. The goal is a clearer decision or correction, not proving authority over the other person.

What if I do not know why they made the choice?

Ask before assuming. State the observation and the effect you are concerned about, then invite the missing context. There may be a constraint or decision you have not seen. Feedback becomes more accurate when it distinguishes what you observed from the motive or reasoning you are only inferring.

Should criticism be given in a group meeting?

Consider whether the discussion needs the group and whether the comment can be made without unnecessary embarrassment. Technical review of shared work may belong in a group, while a sensitive personal concern may need another channel. Focus on the task and follow workplace practices. Public visibility is not a substitute for a thoughtful feedback decision.

How specific should positive feedback be?

Explain the behaviour or decision that helped and its effect. “The summary made the requested decision clear” gives more useful information than “great job” alone. Specific positive feedback can help someone repeat an effective approach. It should remain genuine and proportionate rather than becoming exaggerated praise intended to soften every other comment.

What if the colleague rejects the feedback?

Listen to their explanation and check whether you have missed relevant evidence. If a material issue remains, clarify the decision owner or review process rather than escalating the tone. You do not need to win every disagreement personally. Keep the discussion focused on the work’s requirements and consequences.

When should I use a formal process instead?

Use the appropriate workplace route when the issue involves serious conduct, safety, confidentiality or another matter beyond ordinary peer review. A communication technique does not replace organisational procedures or specialist support. Keep facts clear and avoid unsupported accusations. The correct route depends on the actual issue and the responsibilities in your workplace.

Sources and further reading

Reviewed 7 November 2026. Examples and exercises are original editorial guidance. University, employer and professional guidance reflects its own context; actual assessment instructions and workplace processes take priority.

• Center for Creative Leadership — Feedback guidance
• CIPD — Performance management
• GitLab Handbook — Communication