How to Handle Criticism: What to Say, Ask, and Do Next

Use this sequence when you need a response before you have had time to think everything through. Your immediate goal is to understand the complaint and agree on what happens next.

1. Listen to the full point. Let the person finish. If you are ready to interrupt, write down your question instead. A short pause gives you room to choose your opening sentence.
2. Ask for one example. Say, “Which part are you referring to?” or “Can you walk me through one instance?” Ask about the work or behavior, rather than guessing what the person means.
3. Summarize the concern. Say, “You needed the recommendation before the background, and my update made you search for it. Is that right?” Check the meaning before offering a defense or a solution.
4. Choose a next step. Name a correction, request time to check the facts, or explain the point you dispute. Add a time for returning to the conversation if it cannot be resolved now.

Example: a manager criticizes a project update. These sample exchanges are practice scripts to adapt to your circumstances.

Manager: “Your updates are hard to follow. I never know what you need from me.”

You: “Can you show me where that happened in yesterday's update?”

Manager: “The supplier decision was buried under three paragraphs of background.”

You: “So the main issue is that the decision request came too late, rather than that the background was inaccurate?”

Manager: “Yes. I need to see the decision first.”

You: “Understood. I'll put the decision and deadline at the top of Friday's update. Could we check afterward whether that gives you what you need?”

The University of Waterloo Centre for Teaching Excellence's guidance on receiving feedback recommends listening without interrupting, clarifying and restating key points, reflecting before choosing an action, and following up. Use that sequence as a conversation structure; you still decide which feedback merits action.

Separate the useful information from the way it was delivered. A complaint can contain an accurate observation and an unfair conclusion in the same sentence. Respond to those parts separately instead of treating the whole statement as either right or wrong.

Example: a mixed statement. A classmate says, “You never contribute. I had to finish the slides last night.” You might answer, “I completed the research notes, but I didn't add them to the slides before you started. Let's look at the handoff and agree when each part needs to be ready.” That recognizes a coordination problem without agreeing that you never contribute.

If you cannot yet classify the feedback, stay in the clarification stage. “I want to understand the example before deciding what to change” is a complete response. You do not need an immediate verdict on your performance or character.

For a closer look at the difference between an observation and a judgment, see these constructive criticism examples.

Ask what happened, what was expected, and what a better version would look like. Choose the missing detail first; a rapid series of questions can turn a useful clarification into an interrogation.

Before: an exchange that stays vague.

Tutor: “Your argument needs more depth.”

Student: “But I worked really hard on it.”

Tutor: “You still need to go deeper.”

Neither person has identified a change the student can make. Effort may matter to the student, but it does not explain which part of the argument needs work.

After: an exchange with a next action.

Student: “Could we look at one paragraph where the reasoning is incomplete?”

Tutor: “Here, you state the conclusion without explaining the evidence.”

Student: “Would adding the comparison and explaining why it supports the conclusion address that gap?”

Tutor: “Yes. Make that connection explicit.”

Student: “I'll revise this paragraph first, then use the same check on the others.”

At work, useful follow-ups include “What information was missing?” and “What would you want to see in the next version?” With a friend, ask “When did you feel I wasn't listening?” rather than demanding proof that you ever interrupt.

The SBI feedback model offers a useful lens: identify the situation, the behavior, and its impact. You can ask for those details even when the other person has not organized the feedback that way. If no example is available, agree to discuss the next concrete instance rather than inventing one together.

Acknowledge your action, explain the repair, and name when you will do it. Keep the apology proportionate to what happened. A specific admission gives the other person something to respond to; a long description of your intentions may leave the practical problem untouched.

Example: an omitted meeting invitation. “You're right: I left you off the invitation, so you didn't have the chance to give input before the decision. I'm sorry. I'll send you the notes this morning and ask the group to hold the decision until you've responded by tomorrow afternoon.”

If you cannot reverse the outcome, say what you can still repair. For example: “The meeting has already happened. I'll send the decisions and open questions today, then arrange a separate review of the part that affects your work.” Avoid promising to undo something outside your control.

Use this template when you need to prepare a concise response:

You're right that I [specific action or omission].
That meant [concrete effect]. I'm sorry.
I will [repair within my control] by [date/time].
For the next [task], I will [changed process].
Let's check [specific item] on [follow-up date].

Include context only if it changes the solution. “I used the old distribution list; I'll update it before the next invitation” explains a repair. “I was busy and everyone kept asking me things” leaves the recipient unsure what will change.

If the requested repair conflicts with another commitment, negotiate the timing explicitly: “I can correct the figures by two, or rebuild the full report by tomorrow morning. Which do you need first?” Taking responsibility includes giving a workable plan.

State the part you accept, identify the part you dispute, and bring the conversation back to evidence. You can be receptive to feedback while withholding agreement with an inaccurate account.

Keep facts, interpretations, and requests separate. A fact might be the timestamp on a submitted file. An interpretation might be that you did not care about the task. A request might be to provide an earlier progress update next time. Each needs a different answer.

Example: a disputed deadline.

Colleague: “You ignored the deadline and held everyone up.”

You: “I understand the team needed the file earlier. The deadline in our message thread is Thursday at noon, and I sent it Thursday at ten. Were you working from a different agreement?”

Colleague: “I thought we changed it to Wednesday during the call.”

You: “I didn't record that change. Let's check the call notes. For the next handoff, could we put any revised deadline in the shared message?”

This response leaves room for missing information. If the notes show that you missed the change, acknowledge it. If they support your account, you can say, “The notes still show Thursday. I don't agree that I missed the agreed deadline, but I can send an interim version earlier next time.”

When the disagreement is about quality, compare a specific example with the agreed criteria. Ask someone to identify what the draft lacks instead of collecting competing opinions about whether it is “good.” Waterloo's guidance also suggests considering a second opinion when you disagree. Choose someone who can review the relevant work and expectations, and explain the context without asking them to take sides.

Propose a specific boundary and a practical way to continue. You can address an urgent correction in the room while moving a longer discussion about your performance to a private conversation.

Example: criticism during a team meeting. “The number on that slide is wrong; I'll correct it before we send the deck. I'd like to discuss the broader concern about my preparation privately after this meeting.” The first sentence deals with the shared task. The second names where the remaining conversation should happen.

For personal remarks, make the distinction explicit: “I'm ready to discuss the missed handoff. I want us to keep the discussion about what happened and what needs to change.” If the comment continues, offer a time to resume: “I'm going to pause here. We can return to the task at three if we can discuss it without personal comments.” Choose wording and a next step that fit your situation and responsibilities.

With a friend, the boundary might be simpler: “I want to hear why you're upset. Can we talk about the cancelled plan without calling me selfish?” Then listen to the actual complaint if the conversation returns to it.

The DESC script can help you organize the behavior, its effect, and your request. If the conversation repeatedly returns to personal attacks, consider asking an appropriate manager, tutor, or support contact to help arrange a more workable discussion. Describe the words and events rather than diagnosing the speaker's motives.

Choose one observable change, the next opportunity to use it, and a way to review it. “Be more confident” is difficult to check. “Open the next project update with my recommendation and one reason” gives both people something concrete to assess.

Example: turn a complaint into a plan. The concern is that colleagues cannot find your request in a long email. Your next action is to put the request, owner, and deadline in the first two lines. The review point is Friday's update, and the question is whether the recipient could identify the decision without reading the background.

A short follow-up email can capture that agreement:

Subject: Next steps from our feedback conversation

Hi [name],

My understanding is that [specific behavior] made [task] harder.
For [next task/date], I will [observable change].
I will send [item] by [date/time].
Could we review [specific question] on [date]?
Please let me know if I have missed or misunderstood anything.

Thanks,
[name]

If a point remains disputed, record it neutrally: “We agreed on the new update format; we still need to confirm which deadline applied to last week's file.” That preserves the distinction between an agreed improvement and an unresolved account of events.

At the review, bring the revised work and ask a narrow question. If the change helped, decide whether to keep it. If it did not, ask which detail still gets in the way. The What-So What-Now What framework offers a structure for reviewing what happened, why it mattered, and what to try next.

Use SayNow AI to say your response aloud, review feedback, and practice a clearer version before a difficult conversation. SayNow AI offers personalized speaking practice and AI conversations for professional situations, including interviews, presentations, and negotiations. It gives real-time feedback on delivery, structure, clarity, and persuasiveness, with communication frameworks to support your practice.

Choose one response from this guide and reduce it to three cues: the concern, your position, and the next action. Say it aloud in a practice conversation. Review the feedback with a specific goal, such as making your request easier to follow or reaching your main point sooner.

Revise one part of the response, then say it again. For example, replace a long account of your workload with a direct acknowledgment and a correction date. On the next attempt, check whether you can keep that structure when you add a follow-up question.

Try the performance-review scenario to rehearse your next feedback conversation.

Run a short rehearsal that tests your judgment as well as your wording. Choose a recent comment and write the exact behavior it refers to. If you cannot identify one, make clarification your first task rather than preparing a detailed rebuttal.

Use these checks before you speak:

• Can I summarize the concern without adding a judgment about myself?
• Have I chosen one question that would resolve the most important uncertainty?
• If I made a mistake, have I named a repair and a realistic date?
• If I disagree, can I point to evidence and say what remains uncertain?
• Do I need to request a private conversation or set a boundary?
• Can I name the next action and the point when we will review it?

Ask a practice partner to add one follow-up, such as “Why didn't you do that earlier?” Respond to the question you hear before returning to your plan. If you keep cutting in, use the exercises in how to stop interrupting people to work on leaving space for the full concern.

Learning how to handle criticism means making a usable decision about feedback: accept it, clarify it, or disagree with reasons. Choose one response above, adapt it to a real situation, and rehearse the next action you want to agree on.