How to take criticism at work: what to say and rehearse

Razen’s receiving difficult feedback rehearsal teaches how to take criticism at work: acknowledge the point, test the facts, and agree on a specific next action. Psychology Today recommends a maximum of 72 hours to process the emotion before Fast Feedback turns the exchange into future-focused coaching.

What should you say in the first five seconds of criticism at work?

I want to understand the specific behaviour you mean before I respond.” It acknowledges receipt without admitting fault or agreeing with the judgement, consistent with United Nations Ombudsman guidance on dealing with criticism.

Then use active listening, not automatic agreement. Mirror the key point and paraphrase it back:

“So you felt my client update was unclear because I changed the recommendation without explaining why. Have I understood that correctly?”

This slows the exchange and gives the other person one precise detail to confirm or correct.

Keep the subject observable. “I have a bad attitude” describes an identity judgement, not work you can examine. Say:

“I want to understand which words, action or moment gave that impression.”

That question moves the conversation from personality to evidence. It also leaves room for a fair correction if the label does not match what happened.

Add context with an I-statement, rather than a counterattack:

“I see the impact you mean. I also need to explain what happened from my side.”

The United Nations Ombudsman guidance separates acknowledging feedback from agreeing with it. That distinction matters during a Friday salary review, a client debrief or a formal performance conversation.

Finish with a testable next step:

“What would you like me to do differently in the next update, and when should we review it?”

Ask for the behaviour, expected change and review point. Do not chase emotional approval.

This script suits ordinary workplace feedback. It is not crisis support, legal advice or a discrimination investigation. It does not replace qualified HR, legal or counselling support when the situation requires it.

How can you prepare for difficult feedback?

Use those characteristics as a practical checklist, not as a claim that a fixed preparation time comes from Gallup. A short preparation can turn broad criticism into an accurate record and one testable next action.

Taking criticism well does not mean agreeing quickly.

One: define the exchange. Write the setting, speaker, likely criticism and desired outcome. For example: “Friday performance review; my manager says I am not strategic; I want one observable example and one agreed behaviour to practise.”

Two: split facts from labels. List what happened, what you can verify, what you do not know and what you dispute. Treat “not strategic” as a prompt for evidence, not as an established fact.

Three: test the pattern. A single example and a repeated pattern need different responses.

Four: prepare three lines. Write an acknowledgement, one clarifying question and one boundary or correction. Read each aloud. For criticism about personality, tone or attitude, use: “I can discuss the work clearly, but I will not guess at motives.”

Five: apply the Situation-Behaviour-Impact-Intent framework. Record the situation, the observed behaviour, the resulting impact and the intent or context that still needs checking. This keeps the conversation tied to work rather than character.

Six: prepare the written follow-up. Record the example, disputed facts, agreed action, owner and deadline. Use: “To confirm, you raised [example]. I will complete [action] by [deadline]. I recorded [disputed fact]. Please correct anything I have misunderstood.”

Treat this checklist as editorial guidance. It cannot decide whether criticism is fair. It cannot replace qualified HR, legal or counselling support.

What should you say when the criticism is valid, vague, wrong or unsafe?

Example scripts for different types of criticism

Situation	Say first: example words	Ask or correct: example words	Next move: example action
Valid criticism about an observable behaviour	“That example is fair. I missed the risk in that update.”	“Which part created the greatest problem?”	“I will add a risk check before the next client version.”
Partly valid criticism	“I accept that the handover was late. I do not accept that I ignored the deadline. I flagged the dependency on Tuesday. Let us separate those points.”	“Which part should change, and which part needs correcting?”	Agree the behaviour to change and how you will show it.
Vague criticism about attitude or tone	“I want to act on this, but ‘not collaborative’ is too broad.”	“Which words, action or moment gave that impression?”	Record the example before agreeing a change.
Factually wrong criticism	“I want to correct the record before we discuss improvement. The approval was sent on Tuesday, and I have the message here.”	“What concern remains after that fact?”	Include the correction in your written follow-up.
“I’m willing to discuss my work in a professional, constructive way.” I am not willing to discuss a character label.”	“Please describe the work behaviour, or let us pause and continue with an appropriate support person.”	If safe, move private. Document the exact words. Seek appropriate workplace support.
Public criticism	“I hear the concern. I will discuss the example with you privately after this meeting.”	“Can we review the evidence and expected standard privately?”	Send a written follow-up covering the example, disputed facts and agreed action.

These are example words, not findings about your performance.

The valid row names both the behaviour and the repair. A broad “sorry” can hide the action required. The partly valid row accepts useful feedback without accepting an inaccurate description. The factually wrong row corrects the record before a future promise quietly becomes an admission.

Use a simple rule for loaded language: challenge the work, the evidence or the requested standard, not the person. “The handover missed the deadline” is testable. “You are careless” is a character judgement. Ask the speaker to convert the judgement into an observable behaviour, a specific situation and a clear expectation.

Direct challenge does not justify a personal attack. A manager can be direct about a missed control without labelling your character. You can also disagree without becoming defensive.

They also support recording the agreed revision or action in writing. It does not assume that every complaint deserves agreement.

Discrimination, threats, retaliation, harassment and repeated personal attacks need documentation and appropriate support. They do not need a better-sounding reply. Internal procedures vary by employer and jurisdiction. Check your organisation’s corporate grievance procedures, employee representative route, HR process or Ombudsman and Mediation Services where available. Seek qualified legal or professional advice if the situation could affect your rights or formal employment record.

What pushback should you rehearse after you ask for specifics?

It also supports replacing reflexive apology with a specific commitment. Rehearse the reply after the first question, not only the opening line.

Manager: “That should have been obvious.”

You: “It was not obvious to me from the instruction I received. Please tell me the expected decision rule, and I will use it next time.”

Do not answer with “I know”. That closes the useful part of the exchange. Ask what standard the manager expected, then convert that standard into an observable action.

Manager: “You always do this.”

You: “I want to address a pattern if one exists. Please give me two specific examples, including the dates or situations, so I can compare them and act on the pattern.”

“Always” describes a judgement, not evidence. This reply neither accepts nor dismisses it. It asks for a pattern that you can examine.

Manager: “I do not have time to explain.”

You: “I can take the immediate action now, but I cannot reliably change an unnamed behaviour. Shall we book 20 minutes to review one example and agree the standard?”

A short follow-up meeting gives the criticism an owner and a review point. It also prevents a vague instruction from becoming a later allegation that you ignored feedback.

With a peer, use impact rather than rank:

“I hear that the handover made your work harder. Which part should I change, and what would a clean handover look like?”

With a direct report, protect the speaking space:

“Thank you for telling me. I want to understand the impact of my decision without making you manage my reaction. What should I do differently in the next one-to-one?”

Mirroring means repeating the key phrase before testing its meaning. If a manager says “not strategic”, answer: “You see the decision as not strategic. Which choice led you to that view?” Mirroring slows a fast defence. It does not require agreement.

Active listening is not submission. You can paraphrase, request evidence and correct the record without saying “I agree” or “I am sorry”. Treat the exchange as coaching, not a verdict.

Ask three closing questions: “What behaviour should change?” “When will we review it?” “Who owns the next step?” Rehearse the pushback, not just the ideal answer.

Which phrases derail the conversation, and when should you escalate?

Corporate grievance procedures become relevant when criticism becomes discriminatory, threatening, retaliatory, harassing or persistently personal. Not every criticism is justified.

Replace defensive phrases with useful requests. Do not say “That is not my fault.” Say, “Which part do you want me to address?” Replace “You never told me” with, “What expectation should I follow next time?” Replace “That is unfair” with, “Which example supports that view?” Replace “I know” with, “What would you like me to change?”

Do not apologise for a disputed fact just to end discomfort. Use: “I am sorry the outcome caused that impact; I want to check the facts before accepting responsibility for the cause.” Do not diagnose the critic’s motive or argue about character. Ask for the observable behaviour. If the person refuses to clarify, write down the exact words, date, setting and witnesses.

Send this follow-up afterwards:

To confirm our conversation, you raised [behaviour/example]. I understand [agreed action]. I recorded [disputed fact]. I will complete [owner/action] by [deadline]. Please correct anything I have misunderstood.

Written follow-up protects shared understanding. It does not prove the manager’s account or secure a favourable employment decision.

Treat a Performance Improvement Plan as a formal process, not casual coaching. Ask for the evidence, standard, support, review dates and consequences. Seek qualified HR, legal or employee-representative advice where needed. Ombudsman and Mediation Services, a corporate grievance procedure or an appropriate safeguarding route can provide the next step.

How do you rehearse taking criticism out loud before the meeting?

A practical Role-play protocol uses three passes: cooperative feedback, partial disagreement and adversarial pushback. Aim to practise recovery, not memorise a speech.

Use a timer as a rule of thumb. Keep each first response short enough for the other person to answer. A long defence removes the information you need.

Round one: Gentle difficulty. Say your opening line. Paraphrase the criticism. Ask for one example. State one next action. Record your voice, not just your words. Did your pace speed up? Did the ending drop away? Did you sound apologetic?

Round two: Realistic difficulty. Add one fact you partly dispute. Practise this sentence:

“I accept the impact; I need to separate that from the cause.”

Then read your written follow-up email aloud. Listen for missing dates, unclear ownership and promises without a review point.

Round three: Adversarial mode. Use one interruption:

• “You always do this.”
• “That should have been obvious.”
• “I do not have time to explain.”

Pause. Recover. Return to the work. Do not chase a perfect answer. Performance reviews combine improvement advice, pay, promotion, accountability and possible termination.

Use this five-part debrief after every pass:

1. Clarity of the observable behaviour.
2. Active listening.
3. Factual accuracy.
4. Boundary-setting.
5. Future action.

Mark one line to keep and one line to shorten. Use those qualities as your review test. A useful line identifies the behaviour. A useful next step names the action and the review point.

Change viewpoint for the final pass. Role-play as the employee, then the manager, then the peer. The same criticism sounds different when you own the decision or receive its impact. From the manager viewpoint, test whether your wording describes an observable behaviour rather than a character judgement. From the peer viewpoint, test whether your response recognises the work impact without surrendering disputed facts.

Keep the scenario specific. Use the Friday performance review, a client handover or a public comment from your manager. Write the setting, speaker, criticism and desired outcome before you begin. If the criticism concerns a disputed event, place the relevant date or document beside your script. Do not rehearse a confident response to an unknown fact pattern.

It cannot decide whether criticism is fair, replace qualified professional advice, or determine what will happen in the workplace.

End by saying: “Start the receiving difficult feedback rehearsal.” Use a voice coach or a trusted person for the second voice. The practice should expose interruption, disagreement and recovery, not reward a polished monologue.

Razen Rehearsal Sandbox: Friday performance review: correcting a false criticism

It is Friday at 10 a.m., and Maya’s quarterly review could decide whether she enters a formal Performance Improvement Plan. Daniel says she is not strategic because a client recommendation changed late, while Priya from HR is present to record the discussion and confirm any next steps.

Setting. A small meeting room at 10 a.m. on Friday. Maya, Daniel and Priya sit around a table with the client timeline open on screen.

Cast

• Maya, Employee receiving the criticism. At stake: She needs a fair review and must avoid accepting a false record.
• Daniel, Manager leading the review. At stake: He must justify the review outcome and decide whether to start a Performance Improvement Plan.
• Priya, HR partner recording the review. At stake: She must keep the process specific, documented and procedurally fair.

The Wrong Way

Daniel: The client update showed the same problem again. You changed the recommendation without explaining the risk, and that tells me you aren't thinking strategically.

(Daniel taps the printed review, keeps his eyes on Maya and speaks without pausing.)

Maya: You're right. I should have caught that. I need to be more strategic.

(Maya nods quickly, folds her hands under the table and drops her voice on “right.”)

Daniel: This isn't just one update. The handover was late too.

(Daniel leans back and adds the second criticism before Maya can ask a question.)

Maya: I know. I'm sorry. I'll improve the handovers and make sure this doesn't happen again.

(Maya speaks faster, glances at Priya and writes “improve” in the margin.)

Priya: So the agreed issue is judgement and reliability, with improvement needed across both areas?

(Priya types the words into her notes and turns the screen slightly away from Maya.)

Maya: Yes, I suppose so. Could we review it again in a month?

(Maya gives a small shrug, then looks down at the table.)

Daniel: We can review it in four weeks, but I need you to own the problem first.

(Daniel closes the folder and points to the review date.)

Maya: Understood. I'll work on it.

(Maya exhales through her nose and stops looking at either colleague.)

Why it fails. Maya’s lines “You’re right” and “I’m sorry” turn a disputed cause into an accepted finding before anyone tests the facts. Her broad promise to “improve” gives Daniel no observable standard and lets Priya record “judgement and reliability” as agreed, even though Maya never meant to concede both labels.

The Right Way

Daniel: The client update showed the same problem again. You changed the recommendation without explaining the risk, and that tells me you aren't thinking strategically.

(Daniel taps the printed review and holds his gaze on Maya.)

Maya: Thanks for raising it. I want to understand the specific behaviour before I respond. Do you mean the changed recommendation, the missing risk explanation, or both?

(Maya plants both feet, takes one breath and lifts one finger for each possibility.)

Daniel: Both. The handover was late as well. You keep making decisions without thinking through the impact.

(Daniel folds his arms and uses “keep” as he looks towards Priya.)

Maya: I accept the impact of the late handover. I don't accept that I ignored the deadline: I flagged the dependency in Tuesday's 10:14 message. Let's separate those two points.

(Maya keeps her hands on the table, speaks slower on the date and turns the message thread towards Priya.)

Priya: I can see the Tuesday message. Daniel, what specific behaviour do you want changed in the next client update?

(Priya checks the timestamp, then looks from Daniel to Maya without typing yet.)

Daniel: I want the risk and the reason for any recommendation change stated before the client sees it.

(Daniel uncrosses his arms and writes one sentence on the review form.)

Maya: That is specific. I will add a risk-and-rationale check before the next client version on 28 June. Can we review that update together on 1 July?

(Maya repeats the standard, writes both dates and keeps her voice at the end of the sentence.)

Priya: I'll record the agreed action and the disputed point separately: late handover accepted, ignored deadline not accepted. Please send the message thread with the follow-up.

(Priya reads the wording aloud, types it into the notes and pauses for Daniel's response.)

Maya: I will send it today. I can discuss the work clearly, but I won't guess at motives.

(Maya meets Daniel's eyes, then closes the message thread without pushing it across the table.)

Why it lands. Maya acknowledges the impact without agreeing that she lacks judgement, then corrects the date with a document. Priya changes the dynamic by separating the accepted behaviour from the disputed claim, while Daniel has to name a testable standard. Maya gives up the comfort of a quick apology, but leaves with an accurate record, an owner and two review dates.

<aside class="razen-coach-card" data-razen-scenario="friday-performance-review-correcting-a-false-criticism"> <p class="razen-coach-card__title"><strong>Practice this live.</strong></p> <p><a class="razen-coach-card__button" href="https://razenai.com/coach?scenario=friday-performance-review-correcting-a-false-criticism&amp;article=practise-receive-feedback&amp;utm_source=razen_blog&amp;utm_medium=rehearsal_sandbox&amp;utm_campaign=practise-receive-feedback">Click here to boot up the Razen AI voice coach for this exact scenario.</a></p> </aside>

Delivery playbook

Tone shifts

• Start with a low, measured tone on “Thanks for raising it,” then become more precise when separating the late handover from the disputed deadline claim.
• When Daniel uses “you keep,” do not match his force. Shift to a slower, firmer tone for “I accept the impact” and “I don't accept that I ignored the deadline.”
• End with a practical, forward-facing tone when naming 28 June and 1 July; this prevents the correction from sounding like a refusal to improve.

Pause placement

• Pause for 2 seconds after Daniel's opening criticism before asking whether he means the changed recommendation, the missing explanation or both.
• Pause for 2 seconds after saying “Tuesday's 10:14 message” so Priya and Daniel can register the specific evidence.
• Pause for 1 second after “That is specific” before stating the action and review date.
• Pause for 2 seconds after Priya reads the disputed point aloud. Do not fill the silence or soften the record.

Physiological cues

• Keep both feet flat when Daniel adds “You keep”; press the toes down once, then release instead of folding your shoulders.
• Breathe out before saying “I don't accept.” Keep the jaw loose and let the final word land without raising pitch.
• Keep the message thread in front of you rather than waving it. Look at the document for the date, then return your gaze to Daniel.
• Suppress the quick nod, apologetic smile and hand-to-mouth gesture that could make agreement look broader than it is.

Recovery moves

• If you say “You're right,” correct it immediately: “Let me be more exact. I accept the impact, but I need to check the cause against the record.”
• If Daniel interrupts with “That should have been obvious,” say: “It wasn't obvious from the instruction I received. Please state the decision rule you want me to use next time.”
• If Daniel says “You always do this,” say: “I want to address a pattern if one exists. Please give me two dated examples so we can separate the pattern from today's disputed point.”
• If the room moves towards a Performance Improvement Plan, say: “Before we agree that step, I need the evidence, standard, support, review dates and consequences recorded separately.”

Frequently asked questions

What is the best first sentence when my manager criticises me?

Say: “Thanks for raising it. I want to understand the specific behaviour you mean before I respond.” Then paraphrase the criticism and ask for one concrete example. This acknowledges the feedback without admitting fault, agreeing with a disputed claim or starting a public argument.

How do I take criticism when I think it is factually wrong?

Do not replace correction with a vague promise to improve. Say: “I want to correct the record before we discuss improvement,” then give the relevant fact or document calmly. Ask what concern remains and record the disagreement in your written follow-up.

How can I rehearse criticism at work without sounding scripted?

Practise the same scenario three times: twice with a cooperative speaker and once with tougher pushback. Rehearse the opening, paraphrase, factual correction and next action, rather than memorising every possible sentence. Score clarity, listening, accuracy, boundaries and future action.

When should workplace criticism become a grievance?

Consider formal support when criticism becomes discriminatory, threatening, retaliatory, harassing or repeatedly personal, or when the speaker refuses to discuss observable work. Document the words and setting, then use your organisation's grievance route, Ombudsman and Mediation Services or qualified HR and legal support.