Constructive feedback describes a specific work issue, explains its effect and agrees a practical next step. Give the other person a chance to explain the context before deciding why it happened. Avoid turning an observation about one task into a judgement about their character.
This guide concerns an ordinary work conversation. Serious misconduct, harassment, safety concerns or formal performance action may require a separate process. Follow the appropriate organisational route rather than trying to settle every issue through informal coaching.
1. Choose the issue and check the facts
Identify the behaviour or output you observed and the relevant expectation. Check dates, records and context where appropriate. Separate what you directly know from what someone else reported.
“Two required fields were missing from the draft submitted on Tuesday” is more precise than “You are careless”. If the expectation was unclear, recognise that before criticising the result. Do not collect unrelated mistakes to make the conversation feel more forceful; focus on the issue that needs attention.
2. Choose a suitable setting
Arrange a private, practical time where both people can discuss the work without unnecessary exposure. Explain the topic sufficiently so the person is not ambushed by an apparently casual meeting.
Do not deliver sensitive criticism in a group chat merely because it is convenient. If an immediate operational correction is needed, address that clearly and separate it from the fuller discussion. Consider the person’s role and your authority; a peer suggestion and a manager’s formal instruction are different conversations.
3. Describe the observation and its effect
State what happened and why it matters to the task or team. Keep the effect proportionate and supported. Avoid claiming that one mistake damaged the whole business when you cannot establish that.
Hypothetical wording: “The handover did not identify who owned the next action, so the receiving colleague needed clarification before continuing.” This connects the issue to a practical consequence. It does not assume the omission was deliberate or that the employee lacks commitment.
4. Ask for their account
Pause and invite the person to explain what happened. Listen for missing information, conflicting instructions, workload or a skill gap. Asking is not the same as accepting every explanation without review; it helps establish the relevant context.
Use a neutral question such as “What was happening when you prepared it?” rather than “Why did you ignore the instructions?” If accounts differ, identify what needs checking. Avoid demanding an immediate admission simply to conclude the conversation quickly.
5. Agree the expected change
Describe what should happen next time and how the person will recognise an acceptable result. If a correction is needed now, distinguish it from the longer-term habit. Keep the expectation realistic and within the person’s role.
For the handover example, the change might be to name the next owner and action before sending. Avoid vague instructions such as show more initiative. Ask the person to explain their proposed approach so misunderstandings can be resolved before the next task.
6. Identify support and responsibilities
Discuss what will help the change: a clear template, example, review, access or practice. Assign responsibilities on both sides. If the manager needs to clarify conflicting instructions, record that action too.
Do not promise resources you cannot authorise. State what you will confirm and by when. A useful conversation distinguishes the employee’s action from a process problem the team must fix, rather than placing every part of the solution on the person receiving feedback.
7. Follow up on the agreed evidence
Set a proportionate review point and explain what will be checked. Acknowledge improvement when the work meets the agreed standard. If the issue continues, examine the evidence and follow the appropriate process.
Keep any notes factual and handle them through the organisation’s approved arrangements. Do not turn an informal conversation into a secret collection of character judgements. The purpose of follow-up is to understand whether the change worked and what remains needed, not simply to repeat the criticism.
A worked fictional conversation
Observation: a report omitted the agreed definition of a measure. Effect: the reviewer could not tell which records were counted. Employee context: two templates were circulating. Agreed action: the manager confirms the current template; the employee checks the definition section before the next submission. Review: inspect the next draft together.
This example shows why listening matters. The solution includes both an individual check and a document-control correction. It does not assume that the original omission proves a broader performance problem.
Should I soften every message with praise?
Be respectful and specific. Unrelated praise can obscure the point; genuine recognition can be given on its own merits.
What if the person disagrees?
Clarify the factual difference and what evidence or process will resolve it. Do not force agreement by repeating an unsupported interpretation.
For clearer expectations, use the performance-goal checklist.
