Receiving feedback well means understanding the claim before deciding whether it is accurate or useful. Pause, ask for examples, summarize what you heard, and separate impact from intent. You can acknowledge another person's experience without agreeing with every interpretation, then seek evidence and choose a concrete response.
Who this is for: Managers, specialists, and emerging leaders who receive challenging feedback from colleagues, reports, customers, or supervisors.
- Regulate the immediate response so surprise does not decide the quality of the conversation.
- Ask for specific behavior, context, and impact instead of debating a broad label.
- Evaluate patterns and relevant evidence after the conversation, then communicate what you will do or why you see it differently.
Create a useful pause
Unexpected feedback can narrow attention toward rebuttal, explanation, or withdrawal. You do not need to resolve the claim immediately. Slow the exchange with a breath, a note, or a simple statement that you want to understand. If you cannot listen productively, request a specific time to resume rather than ending indefinitely.
Avoid performing agreement merely to appear receptive. A quick 'you're right' can close the conversation before either person examines the facts. The immediate goal is accurate understanding. Appreciation for the effort of speaking up is compatible with uncertainty about the conclusion, especially when the feedback is broad, secondhand, or emotionally charged.
Turn labels into information
Ask for a recent example: what happened, what the person observed, and what effect followed. If someone says you are dismissive, learn which words, timing, or decision created that experience. Do not cross-examine minor details to make the conversation exhausting. Seek enough specificity to understand and test the concern.
Summarize the claim in neutral language and check it. Distinguish intent from impact: you may have intended efficiency while another person experienced a closed decision. Explaining intent can add context, but it does not erase the effect. Likewise, one person's interpretation is information, not automatic proof of a stable trait.
Evaluate after listening
Consider the source's access to the behavior, the precision of examples, consistency with other evidence, and whether role or power affects what is being said. Look for patterns without running a campaign to recruit people to your side. A trusted colleague can help interpret the feedback if you share it accurately rather than framing the giver as unreasonable.
Some feedback conflicts because stakeholders want different things. A direct report may want more consultation while an executive wants faster decisions. The answer is not to choose the more powerful voice automatically. Clarify decision boundaries, communicate tradeoffs, and identify behavior that can respect both needs, such as earlier input followed by a stated decision point.
Respond with an honest commitment
Choose a small observable action tied to the evidence. Ask the giver what improvement would look like, but retain responsibility for your response. If you disagree, explain the relevant facts calmly and acknowledge any part that remains valid. You can say that you need more examples rather than promising a personality transformation.
Follow up after trying the change. Ask about a specific situation instead of seeking reassurance that you are now a good listener. If feedback is abusive, discriminatory, retaliatory, or part of a serious workplace concern, use the organization's reporting and support routes. General communication advice is not a substitute for qualified employment guidance.
Receive feedback about rushed decisions
A direct report says the manager asks for ideas in meetings but has already chosen an answer, making participation feel staged.
- Pause the impulse to list decisions that did change and ask for a recent meeting where the pattern was visible.
- Summarize the concern as unclear consultation rather than accusing the employee of calling the manager dishonest.
- Review the example and recognize that the decision boundary was not stated even though the manager believed it was implied.
- Commit to labeling future discussions as input, recommendation, or final decision and ask for feedback after a relevant meeting.
Feedback reflection note
Use this private note to understand a difficult message before choosing a response or seeking another perspective.
- Claim and example: what the person observed, in which context, and the impact they described.
- My initial reaction: explanations, emotions, or assumptions to examine rather than send immediately.
- Evidence check: corroborating or conflicting examples, source access, role expectations, and missing context.
- Response: behavior to test, support needed, follow-up situation, or a respectful statement of disagreement.
Common mistakes
- Explaining intent before the other person finishes describing impact.
- Treating every criticism as objective truth and promising a broad change without evidence.
- Asking multiple colleagues whether the feedback giver is wrong instead of examining the behavior.
Try one
Your supervisor says your updates contain too much detail, but your project partners ask for more context. How should you process the conflicting feedback?
A strong answer asks each audience which decisions the update must support, identifies examples where detail helped or obscured action, and separates a shared core from audience-specific depth. It proposes a concise summary with linked context, tests that format in real updates, and follows up with both groups. It does not frame either request as proof that the other audience is unreasonable.
Sources
- CIPD performance appraisal factsheetProfessional guidance on fair, useful performance conversations and review processes.
- Atlassian one-on-one playA practical format for recurring conversations between managers and team members.