Can an EQ Test Explain Defensive Reactions to Feedback?

Start with the exchange, not the score

Suppose a colleague says, “The handoff left out the risk notes,” and the reply is, “You had the same information. Why is this suddenly my fault?” The useful evidence is the wording, the timing, the missing notes, and what happens next. Calling the person low in emotional intelligence adds a cause that the exchange has not established.

An EQ test can still make the moment easier to examine. It may point toward a question about noticing threat, slowing down, taking another person’s perspective, or asking for evidence before explaining. That question becomes useful only when it is checked against more than one observed exchange.

Find out what “EQ” means on this test

“EQ test” is not one measurement. O’Connor and colleagues’ critical review distinguishes ability measures, which ask people to solve emotion-related problems, from trait measures, which use self-report to describe typical emotional functioning or perceived capacity. Mixed measures may combine traits, social skills, competencies, and observer ratings. A systematic review likewise finds substantial variation among instruments, so the label alone cannot tell you what a result means.

That difference matters in the feedback example. A self-report item might resemble “I usually pause before responding to criticism.” The resulting score is partly about the person’s self-view and may reflect confidence or self-knowledge. An ability score concerns performance on the tasks included in that instrument. It may say something about understanding emotion while saying less about what the person usually does when a manager challenges their work.

A 360-degree report adds observations from colleagues, supervisors, or direct reports. That can bring behavior into view, but the raters’ access to the person and their relationships with one another become part of the evidence. A single total score hides these differences.

The same caution applies to a short online self-reflection. It can help someone name a development area, especially when its prompts and scoring logic are clear, but it is not an ability test or a representative comparison with a workforce. Treat its result as a private prompt for reflection. A manager should not convert that prompt into an employee label or ask colleagues to infer a score from one tense conversation.

Before interpreting the result, note the model, method, facets, comparison group if one is supplied, and intended use. If the publisher cannot explain those basics, the score is a poor basis for explaining a specific workplace reaction.

Use the result to form one testable question

A result is most useful when it narrows the next observation. A regulation result might lead to: “Do I answer before the first surge of threat has passed?” A perspective-taking result might lead to: “Can I restate the concern accurately before defending the work?” A self-awareness result might lead to: “Do I notice my short answers or interrupting early enough to change course?”

Try one question in several relevant conversations. Record the exact feedback, the first feeling or impulse you noticed, the response you chose, and whether the conversation moved toward evidence or argument. This is a behavioral check, not a new score. It can show whether the proposed practice is visible in the situation that matters.

Keep the wording provisional. “I need to ask for an example before I explain” can guide practice. “My EQ is low, so I am defensive” turns a tentative interpretation into a fixed story.

Inspect the feedback before judging the recipient

The feedback environment is evidence too. Research on supervisor feedback environments treats source credibility, message quality, delivery, availability, and support for seeking feedback as relevant to how people receive a message. In practice, ask whether the comment was specific, whether the speaker knew the work, whether it was delivered privately, and whether the recipient could question the evidence without being punished for doing so. A reaction can be unhelpful while the message or setting is also poorly designed.

This check protects against a common management error: treating the recipient as the only variable when the process is producing the same problem repeatedly. Clear ownership, a dated example, time to respond, and a route for repair can make feedback easier to use. They also give the recipient a fairer test of the practice the EQ result suggested.

Compare the pattern across situations

A PLOS One analysis of criticism responses in healthcare complaint handling describes defensiveness as socially situated behavior shaped by organizational constraints as well as individual responses. Its setting was specialized, so it cannot be transferred directly to every office. It does, however, provide a useful test for interpretation: does the behavior appear with every feedback giver, or mainly where ownership is unclear, criticism is public, or the consequences feel unsafe?

Compare the trigger, first response, recovery, and repair attempt across more than one exchange. If several people become guarded in the same meeting, the meeting may need attention. If one person becomes guarded across otherwise different settings, an individual practice may deserve more weight. Neither pattern turns an EQ score into a cause, but the comparison makes the next action less speculative.

The comparison should include successful moments, not only failures. A person who accepts precise feedback from a trusted colleague but argues when feedback arrives without an example may need a request-for-evidence habit. A person who can ask questions in private but shuts down in front of senior leaders may be responding to the setting’s power and risk. Those are different development conversations, even if both are described casually as defensiveness.

Make the next conversation the evidence

Choose one practice that fits the work: ask for a concrete example, summarize the concern before replying, pause before explaining, or return with a specific next action. Review it after two or three relevant conversations. Did the person notice the reaction earlier? Did the question produce better evidence? Did the exchange end with a repair or a clear commitment? The answers show whether the practice is useful, not whether the test proved a cause.

Keep an individual result private by default. In a team rollout, a lead can discuss shared behaviors such as how feedback is requested, how examples are documented, and how people repair a sharp exchange without asking employees to disclose scores. That is the appropriate development use for [EQ Test’s team program](/teams), rather than hiring, ranking, promotion, performance scoring, or deciding who belongs on a team.

A useful conversation can be modest. The feedback giver names one observable event; the recipient checks what they heard; both agree on the next handoff or follow-up. If the exchange still fails, the team has new information about the process, the evidence, or the practice. That is more actionable than arguing over whether a total score is high or low.

The stopping rule is simple: keep the result in the process only while it produces a concrete observation or practice. Once it becomes a label for a person, return to the exchange, the evidence, and the conditions that shaped it.

Questions readers ask