How to Ask a Coworker for an Example After Feedback

How can you reopen the conversation without conceding the criticism?

After a defensive reaction, reopen the exchange by taking responsibility for that moment before deciding whether the criticism is fair. You might say: “I got defensive and interrupted you earlier. I’m sorry I cut you off. Could you walk me through one recent moment you meant?” The first two sentences address what you did. The question asks for information about the feedback. You can regret interrupting while still needing to understand whether the criticism fits. That distinction keeps the next move small. Imagine the coworker said your replies in project discussions can feel dismissive. An immediate rebuttal might be, “I was trying to keep us on schedule.” That may explain your intent, yet it leaves the claim unexamined. A blanket apology—“You’re right, I’m terrible at listening”—goes too far in the other direction. It turns one comment into a verdict about your character without identifying what happened. A bounded request asks for one recent moment, giving both of you something more specific to discuss. A request for an example can sound like a challenge if it arrives before any repair. “When have I ever done that?” asks the coworker to defend the accusation. “Could you walk me through one recent moment you meant?” signals that you are willing to hear a particular account. You do not have to promise agreement; you do have to let the answer arrive before arguing for your intent. If you are too activated to listen, say you want to return to it and suggest a time, rather than asking and rebutting each detail. The Center for Creative Leadership’s “How To Give Feedback Most Effectively” recommends feedback tied to a specific situation, observable behavior, and impact. Its guidance is written for the person giving feedback; adapting it into a recipient’s question is a practical inference, not a tested repair formula. The review “To Seek or Not to Seek: Is That the Only Question?” treats feedback seeking as shaped by context and possible costs as well as benefits. Together, they support a modest aim: reopen the conversation to learn what the coworker means, while leaving your assessment of the criticism until you have heard an example.

Sources: How To Give Feedback Most Effectively | Center for Creative Leadership; To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature | Annual Review of Organizational Psychology and Organizational Behavior

What should the one-example request contain?

Ask for one recent situation, the action your coworker observed, and the effect they noticed. For example: “Could you walk me through one recent moment? What was happening, what did I do that you noticed, and what changed for you or the work?” The three parts keep the conversation close to something both people can examine. They also leave room for the coworker to describe an effect you did not intend.

The Center for Creative Leadership’s “How To Give Feedback Most Effectively” says effective feedback gives specific information about what someone did in a particular situation and the impact that behavior had on others. Its Situation–Behavior–Impact approach names those parts: the setting, an observable action, and the consequence. CCL presents the framework as guidance for giving feedback. Turning it around into questions for the person receiving feedback is an adaptation, not a tested use of the model. Still, it gives a practical shape to a request that might otherwise invite another broad judgment.

The wording matters because a label can blend an action with a conclusion about character. “You were dismissive” may describe how the exchange felt, but it does not yet identify what happened. “During the handoff, I started answering before you finished explaining the change” points to an action someone could recall. “You do not respect my work” goes further: it assigns a motive that the event alone may not establish. CCL’s guidance advises describing observed behavior rather than psychoanalyzing motives, and recommends avoiding generalized catchphrases. Asking “What did you hear me say or see me do?” makes that distinction easier to discuss without insisting the coworker prove a case.

Keep the request bounded. “Can you give me one example?” is usually a clearer opening than asking for every occasion or a complete explanation of what is wrong. If “you interrupt people” is the feedback, a useful follow-up is: “Which recent conversation comes to mind, and what did I do in it?” That wording narrows the claim to an event while allowing the other person to answer in their own terms. It does not challenge whether they are entitled to feel frustrated, and it does not require you to agree in advance that interruption is a repeated habit.

You can then listen for the three pieces without treating them as a checklist to administer. What was the situation? Which words or action did the coworker observe? What effect did they experience, or what changed in the work? CCL recommends concise, behavior-focused feedback and cautions against piling on similar examples. In this recipient-led conversation, that supports asking for one concrete instance first; it does not mean you should interrogate the coworker until every detail fits a framework. If one part is still unclear, ask a single neutral follow-up, such as “What happened next?” The aim is to locate the feedback well enough to consider it. An example makes a concern more discussable; it does not, by itself, settle what the event means or whether it represents a wider pattern.

Sources: How To Give Feedback Most Effectively | Center for Creative Leadership; Problem Employees: A Research Paper

How do you listen after asking?

After asking for an example, give your coworker room to recall it. Resist filling a pause with a defense or reasons the criticism seems unfair. Your immediate task is narrower than deciding whether the feedback is right: learn what happened from their point of view. Listen for a situation, an action they observed, and an effect they experienced. A phrase such as “you shut people down” is a conclusion; it does not yet identify the exchange they mean.

If the account stays general, ask one neutral question to locate the event. “Can you think of a recent meeting where you noticed that?” invites a particular memory; “When do I ever do that?” challenges the claim before its basis is clear. If they name a meeting but not the action, ask what they saw or heard you do. Then let them answer. Several questions in a row can feel like cross-examination, even when your aim is to understand. Keeping the inquiry focused is a practical judgment, not a tested rule about the ideal number of questions. The aim is information about the event, not a defense of your reputation; once it is located, the coworker has answered the request and you can move on.

The Center for Creative Leadership’s Situation–Behavior–Impact guidance gives feedback givers a way to tie comments to a particular situation, observable behavior, and impact. A recipient can adapt those parts as listening prompts: Where were we? What did you observe? What effect did it have? This applies giver-oriented guidance to a recipient’s follow-up; the source does not show that this adaptation improves a conversation. It can still help distinguish a remembered event from a judgment about character or intent.

After hearing the account, summarize it briefly: “So, during the handoff, I answered before you had finished, and you had to repeat the point.” Leave out motives you cannot observe, such as taking control or not caring. A summary checks whether you heard the description; it does not require agreement about what happened or what its impact means. Let the coworker correct your version, and hear the correction before explaining your intention.

The Annual Review article “To Seek or Not to Seek: Is That the Only Question?” describes feedback seeking as information gathering shaped by context and carrying possible benefits and costs. That framing supports curiosity without assuming every detailed account is accurate. It does not establish that paraphrasing makes a coworker more candid. Once you can state the event and reported effect in terms both people recognize, consider the claim. If it remains broad, ask for the missing detail; if it is specific but you remember it differently, note the difference for the next part of the conversation instead of arguing over intent now.

Sources: How To Give Feedback Most Effectively | Center for Creative Leadership; To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature | Annual Review of Organizational Psychology and Organizational Behavior

Does asking for detail mean accepting the criticism?

Asking for an example does not mean agreeing that the criticism is fair. It means learning what the coworker has in mind before deciding how much weight to give it. You can reflect their account, recognize the effect they describe, and reserve judgment about its interpretation or whether it represents a pattern. After a defensive reaction, a quick rebuttal can shut down useful detail; blanket agreement can turn a broad label into a conclusion before you know which event it refers to. Separate three things: what happened, what the coworker says they observed, and what they believe it means. You might say, “I hear that you experienced my reply as dismissive. I want to understand the moment you mean before I decide what I think about the broader point.” This acknowledges the reported impact without claiming that every part of the criticism is established. If the coworker describes a specific action, summarize it neutrally and check that you understood. The review “To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature” places feedback seeking in organizational interactions and considers links with learning, adjustment, impression management, and potential costs as well as benefits. Its accessible abstract does not test this conversation or tell us how often asking for detail helps. It cautions against treating inquiry as a consequence-free route to improvement. An INFORMS study examined nearly 11,000 feedback instances from four organizations using real-time feedback applications. In those settings, people who sought feedback received lower scores, alongside more comments and comments that were longer, more positive, and more subjective. The authors also report that feedback seeking enhanced constructive communication among colleagues. They describe methods to address endogeneity, the possibility that factors related to seeking feedback also shape the feedback received. The study concerns app-based feedback; it does not test a private conversation after defensiveness. The mix of lower scores and richer, more subjective comments resists a tidy success story. More detail gives a person material to examine, but length and positivity do not make an account more accurate. A lower score alone does not establish worse performance in an objective sense. The app context, rating practices, and reasons people sought feedback matter. The study cannot tell us whether one coworker's example is representative or whether asking caused the differences reported. Suppose a coworker says you interrupted before they finished explaining a proposal. You can reflect that observation and check whether you understood. Later, you might agree that you interrupted and decide to wait before responding next time. You might instead remember the sequence differently or need context to judge the effect. Those conclusions come after hearing the account; the request opens it for examination. A response could sound like this: “I understand that you saw me begin answering before you had finished, and that made it harder to explain your concern. I’m going to think about that. I may remember some context differently, but I wanted to hear the example first.” This illustrative wording is not a validated script. It shows how acknowledgment and evaluation can happen in sequence. You can remain receptive without accepting every inference attached to the feedback. The outcome is a clearer claim: a reported action, a reported effect, and room to check whether the interpretation fits. If the example changes your view, choose a behavior to practice. If it does not, explain the relevant difference after showing you understood. You have asked for information without treating the coworker's account as unquestionable fact or something to defeat.

Sources: To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature | Annual Review of Organizational Psychology and Organizational Behavior; How feedback-seeking affects feedback: Evidence from real-time feedback applications

What can feedback research support—and what remains an inference?

Research supports a modest claim: feedback seeking and feedback effects depend on the question and setting. It does not establish that this repair script will improve a coworker conversation. Asking for one example makes a broad criticism discussable; whether the example is fair, representative, or useful still requires judgment.

The guidance most directly relevant to the wording comes from the Center for Creative Leadership’s Situation–Behavior–Impact approach. It advises feedback givers to locate a situation, describe observable behavior, and explain its impact, rather than judge character or guess at motive. Asking a coworker to supply those same parts turns the advice around: “Which moment do you mean, what did you see me do, and what effect did it have?” That adaptation is an editorial inference. CCL’s guidance is not a trial of recipients’ questions; it cannot show that this phrasing repairs defensiveness or changes later behavior.

The review “To Seek or Not to Seek: Is That the Only Question?” describes feedback seeking in everyday organizational interactions and examines its contexts, benefits, and potential costs, including its relationship to impression management and adjustment. Its scope makes a simple rule such as “always ask” hard to defend. The review maps a field; it does not estimate the effect of reopening one difficult exchange with one coworker.

A study in “Seek and Ye Shall Find” analyzed nearly 11,000 feedback instances from employees in four organizations using real-time feedback applications. People who sought feedback received lower scores, were more likely to receive comments, and received comments that were longer, more positive, and more subjective. The authors used instrumental-variable, matching, and Heckman-type approaches to address endogeneity, but the setting remains application-mediated organizational feedback. It differs from a private conversation after a defensive reaction. Seeking detail may elicit more material to consider, yet added comments are not thereby more objective. Neither the lower scores nor richer comments tell us whether this question works.

“A Review of Feedback Models and Theories” summarizes Kluger and DeNisi’s 1996 meta-analysis of 131 studies, selected from roughly 3,000 publications. The reported average effect was an increase of 0.4 standard deviations, while about one-third of studies found a negative effect on performance. This warns against assuming feedback automatically helps. The review concerns varied interventions, largely in learning and performance settings; its fraction is not the chance that asking a coworker for one example will backfire. It also describes how feedback may direct attention toward task details, the task overall, or the self. A question tied to one event keeps the exchange near the work, but no cited study tests that application.

Together, these sources justify asking for a concrete event as a bounded information-gathering move, not promising a better relationship or more accurate verdict. If the coworker names an observable action and effect, the claim becomes easier to examine: the recipient can reflect it back, consider context, and decide whether a behavior is worth practicing. If the account stays broad, detail-seeking has not proved a pattern. The script is evidence-informed because it borrows from specific-feedback guidance and research showing variation and costs; its effectiveness here remains untested.

Sources: A Review of Feedback Models and Theories; How feedback-seeking affects feedback: Evidence from real-time feedback applications; To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature | Annual Review of Organizational Psychology and Organizational Behavior

What if the example is vague, disputed, or incomplete?

Ask once for a recent moment if the coworker stays general. If no example is available, do not treat the label as proof of a repeated pattern; note what remains unclear and decide whether to revisit it. “You can be difficult in meetings” may describe frustration, but it does not identify what happened. One event can be examined; alone, it cannot establish typical behavior.

The Center for Creative Leadership’s feedback guidance recommends describing actions in a particular situation and their impact, while avoiding labels and assumptions about motive. It is written mainly for feedback givers. Adapting it here means asking for detail without putting the coworker on trial: “Could you think of one recent meeting where that happened? What did I do or say?” If no moment comes to mind, say, “I don’t want to guess at what you mean. If a specific example comes to mind, I’m open to hearing it.” Then pause.

A locatable example gives you something concrete to consider. Suppose the coworker recalls that you began responding while they were still explaining a concern. You might reflect: “I started answering before you finished, and it made it harder to get your concern across. Have I understood?” This acknowledges the reported action and effect; it does not require agreement that you always interrupt. CCL supports behavior-and-impact detail. Turning that guidance into a recipient’s question is an editorial inference, not a tested script.

The event may be specific while your memories differ. You may remember starting after a pause; the coworker may have experienced an interruption. Check what each recalls, then add one relevant fact: “I remember waiting for a pause, though I may have misread it. I can see you had not finished.” Keep disagreement attached to the event. Labels about either person’s character do not resolve what happened.

A difference in memory or impact does not establish dishonesty. Nor does hearing an effect settle intent or show a wider pattern. “To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature” describes feedback seeking as shaped by context and possible costs as well as benefits. It does not show that one example is accurate or representative. Asking can gather information; the answer still needs judgment.

If the coworker repeats only a label, keep the uncertainty intact: you heard a concern, but lack an event to evaluate. You can notice one behavior in future meetings, such as leaving room for colleagues to finish. Treat that as a small experiment in your conduct, not proof that the label is correct. Consider an incident’s circumstances before drawing a broader conclusion.

When an example remains disputed, leave the interpretation open: “I understand that the exchange landed that way for you. I remember the timing differently, so I’ll pay attention next time.” If the issue affects shared work, agree on an observable request, such as signaling when the other person has finished. That can guide the next interaction without settling the past one.

If no moment can be named, thank the coworker and leave room to return to it. If accounts differ, separate observations from inferences. If the example reveals a behavior you want to change, choose one action to try. Detail makes feedback discussable; one conversation does not establish a pattern or decide your character.

Sources: How To Give Feedback Most Effectively | Center for Creative Leadership; To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature | Annual Review of Organizational Psychology and Organizational Behavior

When should you pause or choose another channel?

A private follow-up is reasonable only when you can ask and hear the answer without creating a serious risk for yourself or the other person. If the exchange is merely uncomfortable, a short pause and a calmer time may help. If you have a concrete reason to expect retaliation, pressure to disclose confidential information, or interference with an active workplace process, do not treat direct conversation as the required test of emotional skill. Consider an appropriate manager, representative, or established workplace channel instead. Which route fits depends on the facts and the relevant policy, not on a general rule that every difficult exchange must be handled one to one.

Psychological safety is a person’s perception of the consequences of taking an interpersonal risk in a particular context. In “Psychological Safety: The History, Renaissance, and Future of an Interpersonal Construct,” Edmondson and Lei review research connecting that perception with voice, teamwork, and learning at individual, group, and organizational levels. The term helps name why one worker may be willing to ask a colleague for an example in one setting and cautious in another. It does not mean that a workplace is simply friendly, or that a person should ignore a power imbalance because a conversation is described as developmental. A private room and a calm tone cannot by themselves remove a real employment or confidentiality risk.

The limits of the evidence matter here. Edmondson’s “Psychological Safety and Learning Behavior in Work Teams” tested a model in a multimethod field study of 51 teams at one manufacturing company. Team psychological safety was associated with team learning behavior after accounting for team efficacy; learning behavior, in turn, mediated the association between safety and team performance. This is evidence about shared team beliefs and team-level learning in that organization. It does not predict how one coworker will respond to a particular repair request, establish that a specific pair is safe, or tell an individual which channel to choose. The useful implication is narrower: interpersonal risk is relevant to whether people speak and learn, so the circumstances around a conversation deserve attention alongside the wording.

Before reopening the exchange, separate ordinary discomfort from a material reason to be cautious. You may feel embarrassed, anticipate hearing something unwelcome, or wish you had responded differently. Those feelings can make a follow-up difficult without showing that it is unsafe. By contrast, a meaningful status gap, a threat linked to raising concerns, an explicit request to keep information confidential, or an ongoing formal review can change what is prudent. Ask yourself what you know about this situation, rather than trying to diagnose the coworker’s character or label the whole workplace. If a concern is uncertain but consequential, a trusted representative or relevant policy contact may help you understand the available route before you proceed.

When a direct conversation still seems suitable, timing can reduce avoidable strain. Ask for a private moment when neither person is rushing, and make the scope clear: you want to understand one example, not settle every disagreement at once. If the other person is not ready to talk, agree on whether and when to return to it rather than pressing. If the subject involves confidential details, keep the request within the boundaries you are permitted to discuss. Choosing a different channel may also be appropriate when a manager or process needs to be involved; this section cannot determine which internal procedure applies to a particular employer.

A direct request is therefore conditional, not a measure of courage or emotional intelligence. When the setting allows a candid exchange, you can briefly own the defensive reaction and ask for a specific example. When credible risk, confidentiality, or a formal process changes the stakes, pause and choose a suitable route. The research supports taking interpersonal risk and context seriously, while its team-level findings cannot certify the safety of an individual conversation. Use the circumstances you can identify to decide whether to ask now, wait, or seek another channel.

Sources: Psychological Safety: The History, Renaissance, and Future of an Interpersonal Construct; Psychological Safety and Learning Behavior in Work Teams

What is the next step after the conversation?

Choose one next step that matches what the example gave you. If it identified a behavior you can recognize, try one small change in a similar exchange. If the example was that you began answering before a coworker finished, pause until they finish, then notice how you respond. This is a personal experiment, not a promise that the conversation will improve. If a relevant circumstance is missing, clarify that point. If no specific event emerged, keep the conclusion open; a broad label alone does not tell you what to change.

You might note the situation, the action you chose, and what you observed afterward. One later exchange can help you reflect on your response, but cannot establish a wider pattern. The Center for Creative Leadership’s Situation–Behavior–Impact guidance keeps attention on an event, an observable action, and its effect. Using those elements to choose a next step is a practical adaptation, not a tested method for resolving criticism.

The private 32-item Emotional Skills Profile at /assessment offers reflection on recent behavior and authored scenarios. It has no validated norms and cannot verify what happened in this exchange. Use it to choose a habit to notice, while keeping the coworker’s example and unresolved context separate.

Questions readers ask