How to Respond When an Employee Gets Defensive

When feedback turns into a defense of the past

A manager says that a handoff arrived after the agreed deadline. The employee interrupts: “The date changed. You keep blaming me for decisions made upstream.” The manager now has two jobs. The handoff may still have affected the project, but the employee has raised a factual objection that could change who was responsible. If the manager answers only, “You’re being defensive,” the conversation shifts from the handoff to the employee’s character. If the manager drops the issue to keep the peace, the work problem remains unexamined.

A more useful response is to slow the exchange, acknowledge the specific concern, and ask which part of the account the employee disputes. Then check the evidence and agree on the next work behavior. That sequence is a practical synthesis, not a tested script. Research does not establish one phrase that reliably calms every employee. It does show why a manager should distinguish disagreement about the event from readiness to act on feedback. The manager can keep accountability in view while allowing the account to be corrected.

The distinction matters because a tense response is information about the conversation, not a verdict about motive. The employee may have misunderstood the standard, remember a different agreement, feel publicly blamed, or be avoiding responsibility. A single interruption cannot tell the manager which explanation is right. The first task is therefore modest: keep the exchange specific enough that both people can examine what happened and what needs to happen next.

There is a practical reason not to begin by naming the reaction. The word can sound like a judgment about whether the employee is emotionally fit for work, even when the manager means only that the conversation has become difficult. Once that label is the subject, the manager may spend the remaining time defending the label and the employee defending their character. A work description is narrower and easier to verify: “You disagree with the date I named,” “You have asked twice how this affects your review,” or “We have not yet answered what should happen when a handoff is at risk.” Each sentence leaves room for a different explanation while keeping the meeting anchored to its purpose. The manager can still address conduct that prevents a conversation, but should do so through clear boundaries and examples.

Before the conversation resumes, the manager can decide what outcome is actually needed. Is the aim to correct a work process, clarify a standard, document a performance concern, or make a formal decision? Mixing those aims creates confusing feedback. A developmental conversation should not imply that a decision has already been made; a formal warning should not be presented as a casual opportunity to brainstorm. Naming the purpose helps the manager choose an appropriate tone and level of documentation, and it gives the employee a fair account of what is at stake.

Sources: The future of feedback: Motivating performance improvement through future-focused feedback

What does “defensive” describe in the room?

“Defensive” is often used as though it names a stable quality in a person. In a feedback conversation, it is more accurate to begin with what can be observed: the employee interrupts, disputes an example, explains constraints, shifts attention to a coworker, asks for evidence, becomes quiet, or leaves. These actions do not all mean the same thing. Asking for the date of an incident can be a reasonable request for accuracy. Repeatedly changing the subject may make it difficult to address the work. The manager should describe the action before assigning a meaning to it.

A 2026 systematic review and meta-analysis in Current Psychology treats feedback processing as several stages: an employee first perceives and interprets a message, then evaluates and may accept it, forms a desire to respond, and may develop an intention to act. The review included 24 empirical studies, 595,950 participants, and 75 effect sizes. Across the supervisory-feedback characteristics examined, the pooled association with processing facets was moderate to strong (average r = .36, 95% confidence interval .30 to .41). Credibility, feedback valence, message quality, support, and charisma had comparatively stronger associations, though estimates varied by facet and characteristic. The result is a synthesis of associations, not evidence that a particular tone causes an employee to change behavior.

This staged view helps a manager ask a better question than “Why are they so defensive?” The employee may understand the words and still doubt their accuracy. They may accept that an event occurred but not know what to do differently. They may intend to change and later lack the time or authority to do it. A visible objection is not a complete measure of any of those later steps.

An observational PLOS ONE study offers a related but distant example. Researchers examined UK hospital staff responses to criticism in an online patient forum and identified public tactics such as redirecting, evading, invalidating concerns, or closing a feedback episode. The setting was public complaint handling, not a manager’s private performance conversation. It supports the narrower idea that defensiveness can be studied as something people do in response to criticism, rather than guessed at as a hidden motive. It does not show that an employee who explains a missed deadline is using one of those tactics.

So the manager can name the immediate exchange without using a label: “I hear that you disagree with the date I gave. Which date do you believe we agreed to?” Or: “We’ve moved to what another person did. I want to understand that, then return to the part of the handoff you owned.” This language keeps the discussion open and makes its boundary visible. Whether the concern is valid remains a question for the evidence.

This distinction also protects the employee from being asked to prove a private feeling. A manager cannot reliably infer shame, anger, anxiety, or contempt from a raised voice or silence. The employee may be frustrated with the manager, surprised by the example, worried about consequences, or simply trying to remember a complicated sequence. Asking what they disagree with is a more answerable question than asking why they are reacting this way. If the employee volunteers an emotional concern, the manager can acknowledge it and ask what would help clarify the work issue. If they do not, there is no need to impose a psychological story on them.

A calm question does not mean allowing every interruption to continue. If the employee repeatedly talks over the manager, set a behavioral limit that applies to the exchange: “I will hear your account, and I need us to take turns so I can follow it.” This is different from demanding that the employee appear calm before their point counts. The manager can maintain a respectful structure while still listening to substantive disagreement.

Sources: Examining the relationship between supervisory feedback characteristics and employee feedback processing: a systematic review and meta-analysis; The complaint handler’s bind: How organisational constraints lead to defensive responses to criticism

Pause the escalation without withdrawing the feedback

When the exchange speeds up, the manager should stop adding new criticisms. More examples, stronger emphasis, and a repeated demand to “own it” can make the conversation harder to follow. A pause is useful when it creates room to identify the disagreement. It need not signal that the original feedback was wrong or that the employee has vetoed it.

A practical pause has three parts. First, reflect the concern without endorsing a disputed explanation: “You’re saying the deadline changed, and that my example leaves out the planning meeting.” Second, ask for the part that needs checking: “Let’s look at when the date changed.” Third, set the scope: “We still need to work out how to flag a risk to the handoff earlier.” The manager can use their own words; the point is to show that the objection was heard and then keep the work issue in view.

The 2026 meta-analysis found that credibility and feedback quality were associated with several processing stages. This makes it reasonable to check whether a message is specific and whether the manager had a sound basis for it. It does not show that supportive delivery alone produces acceptance. A courteous but vague criticism can remain difficult to act on; a direct message can still be inaccurate. The manager should improve the quality of the information, not treat warmth as a substitute for it.

The Chartered Institute of Personnel and Development’s evidence review makes a broad caution: performance feedback may support performance, but it may also be detrimental when delivered poorly. The overview is a professional-body summary, not a study of this particular response. It supports care in the way feedback is given, rather than any fixed technique for de-escalation.

If either person is too angry or upset to listen, agree on a time and place to continue. Make the return concrete: “Let’s pause now and meet at 10 tomorrow with the project timeline.” Avoid a vague “we’ll talk later,” which can leave the employee unsure whether the feedback is still active. If a formal performance, safety, discrimination, or retaliation process is involved, use the organization’s established route rather than trying to settle it through an improvised coaching conversation.

A pause is different from avoidance because it includes a clear return point. The manager should say which subject will resume and what information either person will bring. For example, “Let’s stop here. I’ll check the tracker and you can send the message you remember from planning; we’ll meet tomorrow to settle the date and the handoff plan.” That statement gives the employee a chance to gather context and makes the manager accountable for checking their own claim. If the manager is not ready to resume at the proposed time, they should update the employee rather than leave the matter hanging. A short pause can lower the pressure; an indefinite delay can make feedback feel like an unstated threat.

Avoid using the pause to rehearse a stronger argument. Use it to check the record, regulate your own response, and decide which parts of the conversation are essential. If the employee wants to bring a representative or support person under policy, follow the applicable rules. A manager’s preparation should make the discussion more accurate and fair, not more intimidating.

Sources: Examining the relationship between supervisory feedback characteristics and employee feedback processing: a systematic review and meta-analysis; Performance feedback: an evidence review

Why can arguing about the past make the meeting harder?

People who took part in a feedback discussion can remember the same work differently. The employee knows about obstacles and decisions that the manager may not have seen. The manager may have evidence about the downstream effect that the employee did not witness. Each account can contain useful information, but a conversation about fault can turn quickly into a contest over whose interpretation will stand.

In “The future of feedback: Motivating performance improvement through future-focused feedback,” researchers reported three studies. The first surveyed 419 middle and upper managers enrolled in Executive MBA classes across Chicago, Barcelona, and Singapore; 382 participants remained in the analysis after exclusions. Managers receiving negative feedback judged it less accurate and the source less qualified than managers giving feedback or receiving positive feedback. In the two later studies, managers and executives role-played performance-review conversations. Participants also differed in how they explained past success and failure, and the discussions could widen disagreement about causes rather than settle it.

In the role-play studies, recipients’ perceptions that a conversation focused on future plans were associated with greater acceptance and intention to change. The authors did not show that a manager can cause improvement simply by redirecting every discussion to the future. Nor did they show that facts about the past are unimportant. Their findings suggest a narrower practical point: consensus about every cause may be hard to reach, and a conversation can still identify a future action while some disagreement remains. The studies used recalled incidents and role-play, not long-term observation of ordinary manager–employee relationships.

A 2025 Human Resource Development Quarterly study gives another useful comparison, with limits. In its main experiment, 69 mostly German participants, average age about 25, completed product-knowledge vignettes and received either supervisory negative feedback or coaching. The coaching condition included guidance and learning strategies; the negative-feedback condition included performance information and specific correction. Participants rated their reactions to these scripted materials. The experiment distinguishes message formats and measured reactions, but a short online vignette is not a real feedback relationship or a test of a manager’s response to defensiveness. It cannot establish which approach works best in a live dispute.

The manager can use a forward-looking question without erasing the record: “We may not agree yet about why the file arrived late. What should happen next time if the date changes or the handoff is at risk?” That question is useful only after identifying what is actually disputed. Otherwise it can sound like a way to avoid a valid correction. The sequence is: register the disagreement, check what can be checked, and make a plan for what remains under the employee’s and manager’s control.

The researchers’ future-focus result should not be turned into a slogan that “the past does not matter.” Past evidence determines whether a performance concern is fair, whether the target was known, and whether the employee could reasonably control the event. The more useful distinction is between establishing enough about the past to act responsibly and demanding total agreement about motive. A manager may need to review records, hear another person, or correct a previous account. After doing that work, it may still be impossible to know exactly why someone made a decision. The next work plan can proceed without pretending that uncertainty has disappeared.

Future focus should also leave room for responsibility. A concrete plan is not a way to erase a repeated failure or avoid explaining consequences. If earlier events are relevant to a formal decision, handle them according to the stated process and explain how they inform that decision. Keep that explanation distinct from coaching about the next task. This separation helps the employee understand whether the manager is asking for learning, recording a concern, or communicating an outcome.

Sources: The future of feedback: Motivating performance improvement through future-focused feedback; The effects of supervisory negative feedback and coaching on employees’ responses to feedback: The moderating role of mindset

Was the feedback clear and credible enough to discuss?

Before asking an employee to change, the manager should be able to state the work expectation and the example that fell short. “You need to communicate better” gives the employee little to test. “The client team did not receive the revised file before its review began Tuesday; please send a status note when a handoff is at risk” identifies an event and a possible next behavior. This does not prove the manager’s interpretation is correct, but it makes the claim discussable.

Credibility here means whether the employee has reason to regard the manager as informed and fair about this example. Quality means whether the message gives relevant detail the employee can use. These ideas appear in the 2026 meta-analysis, which found that credibility and feedback quality were associated with several stages of feedback processing. Because studies and measures differed, the pooled pattern cannot tell a manager the exact wording to use or guarantee an employee’s response. It does direct attention to the message and its source, not solely to the recipient’s reaction.

A manager can audit a feedback statement with four plain questions: What was expected? What happened, and when? What evidence supports that account? What consequence for the work followed? If one answer is missing, repair that gap before interpreting the employee’s disagreement as resistance. The point is not to assemble a case against the employee. It is to give both people the same concrete event to discuss.

The CIPD review’s warning that feedback may harm when handled poorly also makes the manager’s delivery part of the conversation. Was the feedback raised in front of colleagues when privacy was possible? Did the employee hear it for the first time in a high-stakes review? Did the manager mix coaching with a decision about pay or promotion? These conditions do not prove the criticism is false. They can affect whether the employee hears a request to learn, a judgment about status, or an explanation of an already-made decision.

The manager should separate those purposes out loud. If the conversation is developmental, say what the employee can practice and what support is available. If it is formal performance management, explain the standard, evidence, process, and next steps accurately. Do not soften a serious concern with reassurance that is not true. Trust can be damaged by either an unfair accusation or a comforting statement that later proves misleading.

Specificity is especially important when the manager gives feedback about an interpersonal effect. “You were dismissive” is difficult to test because it combines an interpretation with an evaluation. “When Priya raised the schedule risk, you said ‘that is not my problem’ and moved to the next agenda item; the team left without an owner for the change” gives the employee a particular moment to confirm or contest. If the wording is remembered imperfectly, say so. The manager can describe the effect on the work without claiming to know the employee’s intention. This is not a technique that guarantees agreement. It simply makes the content more inspectable and gives the employee a fair chance to add missing context.

The employee may also need to know how the manager will judge improvement. “Communicate earlier” is vague unless the manager says what counts as early and whom to inform. A better standard might be: “If a committed date is likely to slip, update the tracker and tell the receiving lead before the daily planning meeting.” The standard can be adapted to the role and workflow. It should be realistic, within the employee’s authority, and consistent with how others are expected to work.

Sources: Examining the relationship between supervisory feedback characteristics and employee feedback processing: a systematic review and meta-analysis; Performance feedback: an evidence review

How should a manager handle a factual disagreement?

Treat a factual objection as a question to investigate. Suppose a manager says a project file missed its agreed handoff date. The employee says the date was moved during a planning meeting. The manager should not decide from the employee’s tone which account is more credible. Ask what date the employee understood, who was present, and where the change was recorded. Then check the project plan or message trail. This is an illustrative example, not a reported case.

If the record confirms the date changed, correct the feedback: “You’re right; the team moved the deadline. I should not have said you missed the original date. The concern I still have is that the receiving team did not know the revised handoff would slip.” If the record does not confirm it, say what remains uncertain rather than overstating certainty: “I don’t see a revised date in the plan. Let’s check with the people who were in the meeting before we close that part.” Both turns preserve a standard while showing that evidence can change the manager’s claim.

A factual check is not the same as giving an employee an endless trial about every performance concern. The manager can define a reasonable scope: one date, one handoff, one source of evidence. If the question requires another person’s account, ask them privately and follow ordinary confidentiality rules. Do not invite a public show of hands or use the employee’s immediate reaction as evidence of guilt.

Research on multisource feedback provides a caution against assuming that a negative rating automatically helps. Brett and Atwater’s 2001 study, available here through its PubMed abstract, examined 360-degree ratings, self–other discrepancies, recipient reactions, perceived accuracy, and usefulness. The abstract reports that less favorable ratings were related to more negative reactions and lower perceived accuracy; those reactions and accuracy judgments were related to lower perceived usefulness. The accessible record does not provide the full methods or detailed estimates. It concerns multisource assessment, not a single manager checking one event, and it does not show causation. Its relevance is limited but clear: unfavorable information does not become useful just because it is delivered.

Taylor and Bright’s 2011 article offers a conceptual model of open-mindedness and defensiveness in multisource-feedback processes. It distinguishes considering others’ views from dismissing them, but the publisher page presents a framework, not an intervention trial or a diagnostic instrument. For a manager, its practical value is a reminder to test whether both parties can consider another account. It cannot sort employees into fixed categories.

After the check, summarize the record in two columns verbally, even if no table is needed: what is established and what remains unresolved. Then ask what behavior can be agreed on despite the unresolved part. For example, both may agree that any date change should be added to the project tracker and sent to the receiving team. That agreement does not decide who caused the first delay. It reduces the chance of the same ambiguity recurring.

The missed-handoff example also shows why records need interpretation. A timestamp can establish when a file was uploaded, but not by itself when the team agreed the file was due. A project tracker can show the current date while missing an oral change. A message can show one person’s understanding without proving everyone received the update. The manager should match evidence to the disputed claim and say what the evidence can and cannot settle. If records conflict, identify that conflict and decide who can clarify it. Treating any available document as final merely because it is written can reproduce an earlier communication failure.

Sometimes the best answer is that the available evidence is not enough. A manager can say, “I cannot establish whether the date changed in that meeting, so I am not going to record that you ignored the original date. We still need a reliable way to confirm changes.” That is a real conclusion, not a failure to manage. It prevents a weak claim from hardening into an official account while identifying a process improvement that both people can use.

Sources: Feedback: Reactions to unfavorable performance appraisals; Open-Mindedness and Defensiveness in Multisource Feedback Processes; The future of feedback: Motivating performance improvement through future-focused feedback

When might the employee’s objection reveal a problem with the manager?

An employee’s pushback may be about the way feedback was delivered rather than only its content. The manager should listen for a concrete complaint: the standard was never shared, a similar mistake by another employee was treated differently, criticism was delivered in public, the manager omitted a relevant constraint, or the employee fears that disagreement will affect their standing. These claims need fair consideration. They should not be accepted or rejected solely because they are uncomfortable.

A study indexed in PubMed examined perceived face threat in relation to abusive supervision and employee feedback seeking. It analyzed 318 paired questionnaires from employees and their direct supervisors collected at multiple time points and from multiple sources. The authors reported that perceived face threat mediated the association between abusive supervision and feedback seeking. “Face threat” means a perceived threat to a person’s social standing or dignity. This study concerns abusive supervision, which is not ordinary corrective feedback. Its questionnaire design and culturally specific context limit what can be inferred about an everyday disagreement. It supports checking for humiliation or power pressure where there is reason to suspect it, not assuming that all employees who disagree feel threatened.

A manager can ask a concrete process question: “Was there anything about how or when I raised this that made it harder to answer?” Then listen without forcing the employee to prove the concern immediately. If the manager gave feedback in front of the team, a private correction may be appropriate. If the expectation was unclear, restate it and allow a fair chance to meet it. If the employee identifies unequal treatment, gather the relevant facts and use the right internal process.

The manager also needs to distinguish an explanation from a complete answer. “I was covering two urgent requests” may explain why the handoff slipped. It does not automatically resolve what the team should do when capacity changes. A useful reply might be: “That workload matters. I should account for it in planning. We still need a signal when both requests compete, so we can reset the date before another team waits.” The constraint changes the manager’s understanding and may change the plan; it does not require pretending the impact did not happen.

If the employee raises possible discrimination, retaliation, a safety issue, or another formal concern, the manager should not turn the moment into an informal debate about motive. Acknowledge the concern, document it according to policy, and seek appropriate guidance. The purpose of this article is conversational practice, not a substitute for an organization’s reporting or investigation procedures.

The employee’s concern may require a change in the manager’s behavior. If a deadline was never written down, the manager can begin confirming dates in the shared plan. If public correction made it harder to respond, the manager can move future feedback to a private setting while still addressing urgent operational issues promptly. If the employee claims that one person receives more favorable treatment, the manager can review comparable cases rather than answer with “I treat everyone the same.” The point is to convert a broad fairness concern into a question that can be checked. The employee need not be right about every detail for the concern to reveal a weak process.

The manager should also notice when their own authority makes disagreement costly. An employee may be weighing not only whether feedback is accurate but how disagreement could affect assignments, evaluations, or access to opportunities. The cited face-threat study does not prove that this is happening in a particular meeting. It does support taking power seriously when the employee names it. The manager can explain how the concern will be handled and avoid promising confidentiality or protection beyond what policy allows.

Sources: Beat People but Not Face: The Role of Perceived Face Threat in the Influence of Abusive Supervision on Employee Feedback Seeking; The complaint handler’s bind: How organisational constraints lead to defensive responses to criticism

How can the manager return to a workable agreement?

Once both people have clarified the disputed point, the manager can make the next step small enough to observe. Avoid “be more accountable,” which can mean different things to each person. Prefer an action with a trigger and a recipient: “If the revised date is at risk, update the project tracker and message the receiving team before the end of the day.” Then ask whether the action is feasible and what obstacle might prevent it.

This is where future focus helps. In the PLOS ONE studies, participants’ perception that the discussion looked ahead to plans was associated with acceptance and intention to change. The findings do not establish that future planning is always sufficient or that a written agreement predicts follow-through. They do support treating the next work behavior as a separate topic from the debate over past intent.

A workable close states three things in ordinary language: what the manager believes is established, what remains under review, and what each person will do next. The manager might say: “The file reached the review team after the deadline we currently have recorded. We still need to check whether the planning meeting changed that date. Until we verify it, please flag any handoff risk in the tracker, and I will confirm the agreed date with the project lead by tomorrow.” This avoids pretending uncertainty is certainty while still giving the work a next step.

The employee should have a chance to correct the summary. “Is that an accurate account of what we agreed?” is more useful than “Do you understand?” The latter can invite a yes without checking whether the plan is shared. If there is no agreement, write down the two accounts neutrally and arrange the next fact-check. A record should capture the issue and commitments, not interpret the employee’s tone as evidence of a personality flaw.

Follow-up should be proportionate. If the manager asked for an updated handoff signal, check the next relevant handoff and discuss whether the signal happened. Do not monitor every unrelated action as proof that the employee has changed. If the behavior improves, say what changed and why it helped. If it does not, return to the standard and consequences described by the organization’s process. The feedback conversation is a work exchange, not a test of whether the employee agrees with the manager’s entire account.

An agreement should not be confused with emotional closure. The employee may remain unhappy with the feedback and still understand the expectation. Conversely, an employee may say “fine” to end a tense meeting without understanding or accepting the plan. Ask for a short summary in the employee’s own words: “What will you do if the receiving team has not confirmed the handoff date?” The manager can then correct misunderstandings and offer support. This is not an oral examination or a request for a promise of perfect performance. It checks whether the action is specific enough for both parties to recognize later.

Set a follow-up date only when there is something meaningful to observe. A next-day check may be appropriate for a time-sensitive handoff; a longer interval may be needed to observe a recurring communication habit. Tell the employee what the manager will review and what support is available. A check-in should assess the agreed behavior, not demand that the employee display gratitude or enthusiasm about having received feedback.

Sources: The future of feedback: Motivating performance improvement through future-focused feedback; Examining the relationship between supervisory feedback characteristics and employee feedback processing: a systematic review and meta-analysis

What if the same exchange keeps repeating?

A repeated pattern deserves a separate conversation about the pattern, but the manager should still use examples rather than a global label. “In our last two feedback meetings, you interrupted before I could finish the example, and we did not agree on a next step” identifies observable behavior. “You’re impossible to give feedback to” turns a work issue into a character judgment and gives the employee little to change.

The manager can invite the employee to help design a workable process: Would a written example before the meeting help? Should the employee have time to review the record? Would it be useful to discuss one issue at a time? These are options to explore, not proven fixes. If the manager changes the format, they should still state the expectation and ask the employee to engage with the specific evidence. A preference for written preparation should not silently replace a necessary conversation.

The Management Center’s practical guide recommends naming the effect of repeated defensiveness, asking what is happening for the employee, and considering whether the manager’s delivery could change. It also cautions that the manager should only offer reassurance that is true. This is practitioner guidance, not controlled evidence. Its useful contribution is to keep both sides in view: the employee’s response may obstruct feedback, and the manager may have something to adjust.

Organizational context can matter too. The PLOS ONE observational study of hospital complaint responses found that staff tactics were shaped by constraints in the organization and the public setting. Because that research is far from ordinary supervisory feedback, it cannot explain a particular employee’s repeated reaction. It does challenge the assumption that every defensive exchange begins and ends with an individual’s disposition. Workload, unclear authority, contradictory priorities, and past consequences can make a response seem safer than open agreement.

If the behavior continues after the facts, expectations, and process are clear, document work-relevant examples and explain the next formal step. Apply the same standard consistently. If the issue is serious, seek HR or other appropriate guidance. Repeating a feedback conversation indefinitely without a clear expectation can create confusion for both people. Equally, escalating because an employee questioned one inaccurate example would punish useful correction.

Keep notes neutral and proportionate. Record the date, the issue discussed, the employee’s material correction, what was checked, and the agreed next step. Avoid recording speculation such as “resistant,” “hostile,” or “lacks self-awareness” when an observable description is available. If the organization has a formal record system, follow its rules for access, retention, and employee notice. Private notes can still affect a person’s work life, so the manager should not collect sensitive personal explanations that are not needed to address the job issue.

If several employees make similar objections about the same expectation, examine the work system before assuming a shared attitude problem. The instructions may conflict, the workload may exceed capacity, or ownership may be unclear. This possibility does not excuse an individual’s conduct where a clear and reasonable expectation was ignored. It does mean that a manager should look for repeated signals in the workflow and adjust the conditions that make the desired behavior difficult.

Sources: Performance feedback: an evidence review; The complaint handler’s bind: How organisational constraints lead to defensive responses to criticism

What can emotional-skill practice change for the manager?

A manager’s emotional skill is visible in what they do under pressure. Awareness may mean noticing, “I’m irritated because I hear this as an excuse.” Regulation may mean pausing long enough not to answer with sarcasm. Understanding emotion may help the manager ask whether the employee’s anger concerns the accusation, the public setting, or the workload. Responding to others may mean acknowledging the concern and setting a limit on interruptions at the same time. These are behaviors to practice; no single exchange proves a stable level of emotional intelligence.

The feedback-processing meta-analysis helps explain why these skills are relevant, but it did not test an EQ assessment or emotional-skills training program. Its synthesis links perceived feedback characteristics with processing outcomes; it cannot show that a manager’s EQ score predicts how well they handle defensiveness. A self-report profile also asks people to reflect on their own behavior and cannot verify how they act in every workplace situation.

A useful practice after a difficult conversation is to review one moment rather than rate yourself as “good” or “bad” at feedback. What did the employee object to? Which part did you check? Did you interrupt or assume motive? What work expectation remained? What will you say or do differently next time? If a trusted colleague observed the exchange, ask for one concrete behavior they noticed. Specific feedback about your own response is more actionable than a global judgment about your emotional intelligence.

EQ Test’s 32-item Emotional Skills Profile can be used privately as an educational reflection tool for noticing recent emotional habits and considering authored scenarios. It has no validated population norms or established ability-test validity, so it cannot rank a manager’s competence or predict how an employee will respond. A reader who wants a structured prompt for personal reflection can explore the profile, then choose one observable behavior to practice in the next conversation.

The manager can practice each part separately before the next hard conversation. For awareness, write down the first interpretation that arose when the employee pushed back. For regulation, choose a brief pause or note-taking action that prevents an immediate retort. For perspective-taking, ask for the strongest version of the employee’s factual concern. For repair, state one thing the manager will check or change. This short reflection is not a clinical exercise and should not become a private diagnosis of either person. Its value is that it translates a broad wish to be more emotionally intelligent into a behavior that can be observed in the next conversation.

A private reflection profile can help organize observations, but any result depends on how a person reports or interprets their own behavior. It cannot tell the manager what an employee experienced, verify the facts of a disagreement, or replace feedback from people who saw the conversation. Use it as a prompt for a question you can test in practice, then revisit the behavior in context rather than treating a report label as the explanation.

Sources: Examining the relationship between supervisory feedback characteristics and employee feedback processing: a systematic review and meta-analysis

One next move after a difficult feedback conversation

Return to the opening handoff example. The manager’s first decision is not whether the employee deserves the label “defensive.” It is whether the employee’s objection changes the account, whether the original feedback was clear and fair, and what work behavior must happen next. Ask one question that tests the disputed fact. If the evidence changes the account, correct it. If a performance concern remains, state it plainly and agree on a specific next step.

The evidence supports this starting point more strongly than treating defensiveness as a flaw to stamp out: respond to the observable exchange, check the quality of the feedback, and move toward a future action without claiming that the past no longer matters. There are real exceptions. If the employee’s conduct is threatening, the concern involves a formal complaint, or the manager cannot be impartial, pause and use the appropriate organizational process. The research cited here combines meta-analysis, role-play, questionnaires, conceptual work, and practitioner guidance; it does not test the full sequence as a single intervention.

One practical action is to write the feedback as a work event plus a next behavior before the next meeting: “On [date], [observable event] affected [work consequence]. Next time, when [trigger], please [specific action].” Bring the evidence, invite correction, and leave room to check what you may have missed. That gives the employee something concrete to answer and gives the manager a fair basis for accountability.

A manager can prepare this in two minutes before the meeting: write the event, the evidence, the work effect, and the next behavior on separate lines. Leave a blank line for what the employee says is missing. That simple layout discourages the manager from mixing facts with conclusions and makes correction easier if new information appears. Afterward, note whether the disagreement was resolved, partly resolved, or still open. Do not mark the conversation successful just because the employee became quieter, or unsuccessful because they remained upset. The relevant result is whether the facts were handled fairly and the next work expectation became clearer.

The question at the center remains simple: can the manager respond in a way that keeps feedback useful when the employee pushes back? Yes, if the manager can separate the employee’s reaction from the claim being made, check that claim fairly, and state what work action follows. The employee does not have to agree with every interpretation for the manager to act responsibly. The manager does have to be willing to correct an account that the evidence does not support.

Sources: Examining the relationship between supervisory feedback characteristics and employee feedback processing: a systematic review and meta-analysis; The future of feedback: Motivating performance improvement through future-focused feedback

Questions readers ask