Useful feedback identifies a specific situation and observable behavior, explains the work-related impact, and opens a conversation about context and next steps. Give it close enough to the event to be useful, but after checking the facts. Feedback is not a verdict about character, and serious matters may require the organization's formal process.
Who this is for: Managers and team leads who need to address effective or problematic work without making vague judgments about personality.
- Separate what you directly observed from your interpretation of motives, attitude, or personality.
- Connect the behavior to a concrete effect on the work, customer, team, or agreed expectation.
- Pause for the recipient's account, then agree on a specific action or reinforcement instead of delivering a monologue.
Prepare from evidence
Before speaking, identify the event, what was said or done, and the relevant expectation. Check whether your account comes from direct observation, reliable records, or secondhand interpretation. If key facts are uncertain, ask questions first. Confidence and seniority do not convert an assumption about intent into evidence.
Choose the right setting and timing. Recognition can sometimes be public if the recipient welcomes it, while corrective feedback is usually private. Do not wait for a distant annual review if the person could act now. For allegations, safety concerns, discrimination, discipline, or other consequential matters, follow policy and seek appropriate internal guidance.
Describe behavior and impact
Anchor the message in a bounded situation. Quote or paraphrase the observable behavior accurately rather than using labels such as careless or difficult. Then explain the impact you can support. 'The approval request omitted the testing note, so the reviewer sent it back for clarification' is clearer than 'you do not care about quality.'
Keep the impact proportionate. A single missed detail may require correction without proving a pattern. If there is a pattern, bring examples and explain the common expectation. Avoid piling unrelated history into one conversation. The recipient should be able to tell exactly which behavior to continue, change, or examine.
Make it a conversation
After stating the observation and impact, ask for the other person's view. New information may alter the interpretation, reveal a system problem, or confirm the issue. Listening does not require abandoning the standard. It helps the manager respond to the actual cause rather than prescribing effort when the obstacle is unclear authority, missing information, or conflicting priorities.
Discuss a next action at the right level. The person may need to repeat an effective approach, repair an immediate effect, practice a skill, clarify a process, or request earlier review. The manager may also own a change. Feedback loses credibility when employees are asked to compensate indefinitely for a preventable organizational problem.
Follow through fairly
Summarize what each person understood and what will happen next. A brief work note can help when follow-up matters, but follow organizational requirements for documentation and access. Do not create informal records filled with speculation. The purpose is continuity and fairness, not collecting language that makes a person look bad.
Notice subsequent behavior and close the loop. If the agreed change occurs, acknowledge it specifically. If it does not, return to the expectation and evidence rather than escalating the emotional tone. Repeated or serious performance concerns should move through the organization's established process with qualified support, not an improvised sequence of threats.
Address an interrupted review
During a design review, a team lead repeatedly answers questions directed to a junior designer, leaving the designer unable to explain the work.
- Meet privately and name the review, the questions directed to the designer, and the observed interruptions without assigning a motive.
- Explain that the designer could not present their reasoning and reviewers could not tell who owned the decisions.
- Ask for the lead's perspective and listen for context, including any concern about accuracy or meeting pressure.
- Agree that future questions go first to the presenter, with the lead adding context after the presenter finishes or requests help.
Feedback preparation card
Draft the core facts before the conversation, then use the card as a prompt rather than reading it as a prosecution.
- Situation: the bounded event, date or context, participants, and relevant expectation.
- Behavior: observable words, actions, or omissions separated from inferred intent and personality labels.
- Impact: supported effect on work, people, customers, risk, or an agreed result.
- Dialogue and next step: question for context, desired behavior, support, owner, and follow-up point.
Common mistakes
- Calling someone careless, uncommitted, or aggressive instead of describing the event.
- Exaggerating a single incident into an enduring pattern without supporting examples.
- Delivering a rehearsed speech and leaving no room for context that could change the response.
Try one
A colleague submits a report with missing source notes. Draft the substance of behavior-based feedback without assuming why it happened.
A strong answer identifies the report and the missing notes, states that reviewers could not verify several claims, and links the issue to the agreed review standard. It asks what affected the submission, confirms whether the expectation was clear, and agrees on a repair and a method for including sources next time. It avoids labels about care, competence, or honesty.
Sources
- CIPD performance appraisal factsheetProfessional guidance on fair, useful performance conversations and review processes.
- CIPD line management factsheetProfessional guidance on the people-management responsibilities and support needs of line managers.