How to Ask Your Supervisor for One EQ Feedback Example

How can you ask for one example?

You can acknowledge the feedback and ask for a recent moment you can understand and act on: “I want to understand what you mean and identify something I can try. Could you point to one recent interaction where you felt I needed to show more emotional intelligence?”

The phrase “show more emotional intelligence” gives you a broad judgment, but it does not identify an interaction or say what to do differently. Keep the immediate goal narrower: get information about what your supervisor noticed. You do not need to agree that the label defines you, or ask your supervisor to defend a global conclusion, before you can hear an example.

If the conversation is rushed or public, you can say, “I’d like to understand this properly. Could we set aside a few minutes to talk privately?” The wording is a prompt to adapt to your voice and circumstances, not a tested script.

You can make the request sound curious rather than accusatory by naming what you hope to learn: which moment prompted the feedback and what response might have helped. That keeps the conversation focused on information you can use. It also avoids asking your supervisor to produce a full definition of emotional intelligence on the spot.

If the supervisor begins with another general description, bring the request back to a single occasion: “Could we start with one time this came up?” A concrete instance is easier to examine than several labels at once. You can consider the account, ask a follow-up, and decide what small response to try after you know what the concern refers to.

What counts as one specific example?

A useful example gives you an event to locate, an action someone could have seen or heard, and the consequence the supervisor noticed. Center for Creative Leadership’s “SBI Feedback Model & Talent Development Conversations” organizes feedback as Situation, Behavior, and Impact: when the event occurred, what the person did, and what effect followed. Here, you can use that provider-side framework to ask for the missing details from the recipient’s side. That adaptation is a practical way to clarify the account; CCL does not test the employee-side questions proposed here.

For instance, imagine an illustrative meeting exchange in which a supervisor says, “You were dismissive.” The adjective is an interpretation, not yet a description of what happened. You might ask, “Which part of the meeting are you thinking of? What did you see or hear me do, and what effect did you notice?” The questions invite an account tied to a moment rather than a verdict about your character.

A more concrete answer might identify that, during a particular agenda item, you began speaking before a colleague had finished, and that the supervisor thought the colleague’s concern was left unanswered. This is only an illustrative translation, not a report of an actual incident. It separates the event, the observable action, and the supervisor’s reported consequence. It also leaves room for an important distinction: the supervisor can describe what they noticed and how they understood its effect, while your intent remains a separate matter to discuss.

That distinction helps you listen without treating either the label or the first account as the whole story. You could first check that you have the details right: “So you’re referring to the project meeting, when I started speaking before the point was finished, and you felt the concern did not get addressed. Have I understood what you noticed?” The purpose is to make sure you are discussing the same event. It is not a concession that your intention was to dismiss anyone, nor a claim that the reported consequence is the only relevant context.

Once the supervisor has described the moment, listen to the account before offering context. An interruption, for example, could have different significance if it stopped a safety-critical point than if it reflected a meeting norm; that context may change how you understand the action and what response would help. You can ask what effect the supervisor noticed, then explain any relevant detail you believe is missing. Starting with the event and behavior makes that disagreement more precise than debating whether “dismissive” is a fair label.

A specific example does not have to settle every disagreement. Its value is that it gives both people something identifiable to discuss: the same meeting, exchange, or task handoff. Without that anchor, “be more emotionally intelligent” could refer to many different behaviors, from noticing that someone is frustrated to changing how disagreement is voiced. Asking for one instance keeps the feedback at a manageable scale and makes clear what the supervisor actually means in this case.

The reported impact also deserves careful wording. Ask what the supervisor noticed or believed happened, rather than treating an impact statement as independently established fact. “I thought the concern went unanswered” reports the supervisor’s reading of the exchange; “you intended to silence your colleague” adds a motive that the action alone cannot establish. Those are different claims. The first gives you a perspective to understand and check against the surrounding event; the second requires more than an observable interruption to support it.

You may remember the sequence differently. First make sure you have heard the supervisor’s account accurately; then supply relevant context, such as whether the colleague had paused, whether the discussion had moved on, or what the task required at that point. Context is not automatically an excuse, and the supervisor’s reaction does not automatically settle what happened. It helps both of you examine the behavior in the situation where it occurred and decide whether a different response would be useful next time.

Sources: SBI Feedback Model & Talent Development Conversations

Why make your purpose explicit?

A feedback request can carry more than one message. You may mean, “Help me understand what you noticed,” while a supervisor may wonder whether you want guidance, reassurance, evidence for a disagreement, or a chance to make a favorable impression. Saying why you are asking gives the other person a clearer basis for responding. It does not guarantee they will interpret the request as you intend.

That ambiguity appears in a specific setting in the 2024 qualitative study “I Think Many of Them Want to Appear to Have a Growth Mindset”: Exploring Supervisors’ Perceptions of Feedback-Seeking Behavior. Researchers interviewed 17 faculty members at the University of Toronto Temerty Faculty of Medicine. The supervisors described inferring learners’ motives from how a request was framed, when it came, their prior relationship with the learner, and how the learner reacted to feedback. Some participants reported irritation when requests seemed repetitive, poorly timed, or insincere. These are supervisors’ perceptions reported in interviews, not evidence that learners actually held those motives.

The study helps explain why the same words may land differently across relationships. A supervisor who has recently had a productive coaching conversation may hear a follow-up as continued learning. Someone approached during a rushed clinical task, or after repeated requests that seem disconnected from action, may read it differently. Those are plausible applications of the study’s reported factors, not separate findings about particular workplaces. The study does not estimate how often either interpretation occurs beyond its small, single-institution medical-faculty context.

The broader review “To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature” by Ashford, De Stobbeleir, and Nujella (2016) likewise treats feedback seeking as an interpersonal behavior that can involve both learning and impression management. Its review frames context and social interpretation as relevant to the costs and benefits of asking. That supports taking the interaction seriously: a request is not received in a vacuum. The review does not establish the best phrasing for an employee who has just been told to show more emotional intelligence.

For this conversation, make the purpose small and concrete: “I want to understand the expectation and identify one behavior I can try. Could you walk me through one recent example?” The first sentence tells the supervisor what kind of help you are seeking; the question then asks for material you can examine. It does not require you to claim the supervisor is right, promise to change before hearing the example, or present yourself as already knowing the answer. This wording is a practical inference from the qualitative findings, not a script tested by either source.

This distinction also keeps responsibility proportionate. You can make your request easier to interpret by naming the information you want; you are not responsible for predicting and neutralizing every possible reading. The supervisor still has to explain the expectation in a way you can understand, and you can ask a follow-up if the answer remains broad. The study’s recommendation to make purpose explicit informs that conversational choice; it does not assign the learner responsibility for a supervisor’s reaction or establish that clarity will produce a particular response.

Stating a learning aim can also make a real difference between asking for feedback and asking for a verdict. If the supervisor hears only “Was I emotionally intelligent?”, the exchange can become an argument about a broad label or a request for reassurance. Asking to understand an expectation and identify one behavior signals that you are looking for a particular incident and an actionable response. You can still assess the account once you hear it; being open to information does not mean accepting every interpretation as complete.

Even careful wording cannot erase an existing relationship, workload, or institutional expectation. The 2024 study concerns medical learners and clinical supervisors, where hierarchy and the educational setting shape how feedback requests are understood. It cannot tell an employee in another field how their manager will react, or how common any reaction is across workplaces. Its useful implication is narrower: give the supervisor relevant information about what you want from the exchange, then pay attention to the response you actually receive.

Sources: “I Think Many of Them Want to Appear to Have a Growth Mindset”: Exploring Supervisors’ Perceptions of Feedback-Seeking Behavior; To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature

How do you check the example before explaining yourself?

Once the supervisor has described an incident, check whether you have understood the account before supplying your explanation. Reflect the situation, the behavior they say they observed, and the impact they noticed in neutral terms. Then ask if that summary is accurate and leave room for correction. This listening sequence helps both people discuss the same event; it does not establish that the supervisor’s account is the only perspective.

Center for Creative Leadership’s “SBI Feedback Model & Talent Development Conversations” separates feedback into Situation, Behavior, and Impact: when something happened, what the person did, and the effect the feedback giver noticed. CCL presents the framework as a way to make feedback specific and describes inquiry about intent as a route into dialogue. Here, the employee is using that structure to check received feedback. That recipient-side application is practical reasoning based on the provider-side framework; CCL does not test this sequence or claim that it resolves disagreement.

Imagine an illustrative project meeting in which a supervisor says you cut off a colleague and left their concern unanswered. After hearing the account, you might say, “You mean the project meeting, when I started speaking before the point was finished, and you felt the concern did not get addressed. Is that what you noticed?” The question reflects the reported event, action, and effect without adopting the label “dismissive” or adding a motive. It asks whether you have the account right, not whether the supervisor has proved every part of it.

Wait for the correction. The supervisor might say the issue was a different meeting, or that they were concerned about the colleague not being invited back into the discussion. That response changes what you need to understand. If the summary is accurate, you can then ask, “What would you have preferred I do in that situation?” The answer may identify a pause, a question to the colleague, or another response tied to that meeting. It supplies an expectation you can consider, rather than leaving you to guess what “more emotional intelligence” means.

Checking the account first makes a disagreement more precise. You may remember that the colleague had finished speaking, or that the discussion had moved to a time-sensitive decision. After confirming what your supervisor meant, you can say, “I understand that you saw me begin before the point was finished. I remember the transition differently: I thought we had moved to the decision. Can we look at that sequence?” You acknowledge the account you heard while identifying the detail you dispute. There is no need to argue about your character or presumed intent before sorting out the event.

Impact and intention are separate parts of the conversation. A supervisor can accurately report feeling that a concern went unanswered without that report, by itself, establishing why you spoke or everything that happened next. If a material detail is wrong, correct it briefly after checking the summary: “I did speak then; the colleague had paused to hand over, as I understood it.” The point is to make the difference specific enough to discuss, not to invalidate the other person’s experience.

Sources: SBI Feedback Model & Talent Development Conversations

What can the research say about asking?

Research does not show that asking this particular question will improve your emotional skill or job performance. It does give a more useful answer than either “feedback seeking works” or “it does nothing”: people seek feedback in conditions shaped by their work resources, and broader studies find an association with performance, but the evidence does not establish that one request causes either outcome.

“Feedback-Seeking Behavior in Organizations: A Meta-Analysis and Systematical Review of Longitudinal Studies” examined 13 longitudinal studies of employees, with 1,527 participants in total. The authors combined studies of how work resources relate to later feedback seeking and systematically reviewed the outcomes. They reported that job resources predicted later feedback seeking, while calling for more research on reciprocal relationships and performance effects. In other words, the review offers evidence about what may precede seeking over time, but it did not find a settled answer about what seeking subsequently does to performance. Its small, varied set of studies also cannot tell us whether asking one supervisor for one example after an emotional-intelligence comment leads to a better response at work.

A separate synthesis supplies meaningful counterevidence to blanket skepticism. “Does seek feedback improve performance? A meta-analytic review about feedback-seeking behavior and individual performance” combined 62 empirical studies involving 15,141 participants. Across the included studies, feedback-seeking behavior had a positive association with individual performance (r = .329). In the longitudinal paired data, the reported association was smaller (r = .154); the review also found that cultural background and data-collection method moderated results. This pattern is consistent with feedback seeking being related to performance in some settings, while the smaller longitudinal estimate counsels against treating the overall relationship as a predictable result of asking.

The distinction between association and cause matters here. People who seek feedback may also have supportive resources, opportunities to act on what they hear, or other characteristics connected with performance. A meta-analysis can summarize how variables move together across studies; it cannot by itself show that requesting feedback produced the performance difference. The longitudinal review raises the same unresolved issue from another angle: resources predicted later seeking, but the consequences for performance still need research. Taken together, these findings argue against saying feedback seeking is unrelated to work outcomes, and against promising that asking will improve them. The comparison between r = .329 overall and r = .154 in longitudinal paired data is useful because it shows why design matters to the size of the reported relationship. A larger estimate across mixed designs describes a stronger average association in that body of work; the smaller paired-data estimate is closer to asking whether seeking and performance remain linked when they are observed over time. It still does not isolate the effect of the act of asking, and it does not erase the positive finding. The results point to an association whose apparent strength varies with how and where researchers measured it.

Neither review isolates the exchange in this article. Their subject is feedback seeking broadly, using different measures and work settings; neither tests the wording “Could you give me one example?” after a supervisor says an employee needs more emotional intelligence. They therefore cannot show that the request changes a skill, that a supervisor will respond constructively, or that performance will rise. The positive meta-analytic result is still relevant: there is a reason to take feedback seeking seriously as a work behavior. Its breadth supports a general relationship worth investigating, while the weaker longitudinal association and the unresolved causal question limit how much to promise.

For this conversation, the defensible reason to ask is immediate and modest: a concrete example can give you information about an interaction and a response to consider. That information may help you decide what to try or what context to explain. Whether the next behavior improves the exchange depends on what happened, what the work required, and what follows; asking alone is not evidence of growth. The research supports neither a guarantee nor the conclusion that feedback is pointless. It leaves the practical value of the request in obtaining something specific enough to examine. That is a useful threshold for the conversation itself, even while longer-term effects remain uncertain.

Sources: Feedback-Seeking Behavior in Organizations: A Meta-Analysis and Systematical Review of Longitudinal Studies; Does seek feedback improve performance? A meta-analytic review about feedback-seeking behavior and individual performance

When should you ask, and when should you pause?

Ask when you and your supervisor can give the exchange attention, preferably in private. If the comment arrives during a tense discussion or when one of you is rushing, you can keep the conversation open without pressing for an answer immediately: “I want to understand what you meant. Could we set aside a few minutes to talk about one example?” That is a practical way to make space for a specific account, not a timing rule established by research.

Keep the first request to one incident. If no example comes to mind, asking the same question repeatedly in the moment may put pressure on the supervisor to produce an answer before they can identify one. You can instead agree on when to return to the question. The 2016 review “To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature” treats feedback seeking as an interpersonal behavior with possible benefits and costs shaped by context. It does not prescribe a universally safe time or frequency for this request; the choice to pause and revisit is a proportionate application of its broad point about context.

The context also changes if the comment is part of a formal performance conversation. Along with asking for an example, ask which role expectation is involved, what behavior has been documented, and how that expectation will be assessed. You might say, “Could you connect this feedback to the expectation for my role and explain what behavior is being assessed?” If the supervisor refers to a review or written record, ask where the expectation is stated and what next step the process provides. That helps you understand whether the conversation is developmental guidance, documentation, or both, so you can respond to the issue actually being raised. This helps distinguish developmental advice from a formal judgment that may follow a workplace process. It is a practical question for clarifying the conversation, not a claim about what every employer’s process requires.

Power differences and written procedures can constrain when and how directly you ask. Follow the relevant process where one applies, and keep your request factual: what situation, what behavior, and what expectation. The available research does not establish one approach that is safe or effective in every supervisor relationship. Choose a workable moment for a single, clear question, then use the answer you receive to decide whether you need more detail. If the supervisor cannot discuss it then, agree on a specific time or channel for the follow-up rather than leaving the issue open-ended.

Sources: “I Think Many of Them Want to Appear to Have a Growth Mindset”: Exploring Supervisors’ Perceptions of Feedback-Seeking Behavior; To Seek or Not to Seek: Is That the Only Question? Recent Developments in Feedback-Seeking Literature

What will you do if no example comes to mind?

If your supervisor cannot name an interaction, do not fill the silence with guesses about what they might mean. You can leave the question open in a practical way: “No problem if one doesn’t come to mind now. Could you flag the next relevant moment and tell me what response you’d want to see?” This gives them time to notice a concrete occasion and gives you something specific to discuss if one occurs. It also keeps the conversation anchored to what the supervisor actually observed, rather than turning a general comment into a story about an incident neither of you has identified.

A useful follow-up is an agreement about what would count as relevant. You might ask whether they mean a particular kind of recurring work situation, such as receiving a correction, responding to disagreement, or handing off a task. The point is not to propose a list of possible failures for your supervisor to confirm. It is to clarify the setting in which they expect a different response. If they can name that setting, ask what they would want to see or hear from you there. “Be more emotionally intelligent” is still too broad to guide a next move; “let the other person finish explaining the concern before I respond” describes something you can recognize and try. Use that sort of wording only if it reflects the expectation your supervisor actually states.

If the concern is part of a formal review, return to the role expectation and the process rather than trying to reconstruct an unwitnessed event. Ask what observable response the role requires in the recurring situation and how you will know the expectation has been met. That question can make an abstract standard discussable even when no recent example is available. Keep the answer separate from assumptions about your supervisor’s unstated view: record what they said, what future situation they asked you to handle differently, and any agreed follow-up. A missing example does not settle whether the broader feedback is accurate; it means there is not yet an event you can assess. The immediate next step is to invite a later observation or define the expected behavior clearly enough to recognize when the situation arises.

What will you try next?

Before you leave the conversation, put the agreed next action into observable terms: “When a colleague raises a concern in the handoff, I’ll ask one clarifying question before I respond.” Use the action only if it matches the example and expectation your supervisor gave. When a comparable situation comes up, notice whether you tried it and what happened in the exchange; if the situation does not recur, there is nothing to score or force. You can then ask for a brief follow-up about that specific moment, including whether the response addressed the original concern. One later conversation cannot establish lasting change or prove the first interpretation complete. It can tell you whether you understood the requested behavior and give both of you a concrete basis for deciding what to adjust next. If the feedback concerns a recurring expectation rather than one discrete event, ask to review it after the next comparable task, not after an arbitrary stretch of time. Agree on the behavior you will each look for so the follow-up can clarify the expectation instead of becoming a verdict on your character.

For private reflection on your own habits, the Emotional Skills Profile is a 32-item educational profile that separates recent-behavior summaries from judgments on authored scenarios. It cannot decide whether your supervisor’s account was right. [Explore the Emotional Skills Profile](/assessment).

Sources: Emotional Skills Profile

Questions readers ask