How to Diagnose Workplace Resistance

How to Diagnose Resistance Before Escalating

Diagnose resistance by recording what happened, naming the work impact, separating facts from interpretation, and testing one plausible constraint at a time. The goal is not to discover a person's hidden motive. It is to gather enough evidence to choose clarification, redesign, support, a boundary, or escalation.

Start only after confirming that the issue is ordinary professional friction. Serious conduct, protected complaints, threats, or safety concerns belong in the appropriate formal route.

Write the observation first

"She is difficult" is an interpretation. "The approval request sent Monday has no response, two decision meetings were missed, and the launch cannot proceed without an owner" is an observation with impact.

A short record should contain the request, owner, due date, response history, dependency, and current risk. It should also mark what remains unknown.

flowchart LR
    A["Observable behavior"] --> B["Business impact"]
    B --> C["Unknown constraint"]
    C --> D["Neutral question"]
    D --> E["Evidence"]
    E --> F["Clarify, redesign, support, bound, or escalate"]

Test constraints without diagnosing the person

The table creates hypotheses. It does not authorize questions about health, disability, family, protected status, or private circumstances.

Use questions that reduce defensiveness

Episode 90 recommends moving from confrontation to conversation. A useful opening is specific: "The project is waiting on the data-retention decision. I may be missing a constraint. What makes the current option difficult to approve?"

Avoid telling the person why they are resisting. Dalton's CRM example assumes an experienced salesperson may fear losing mastery of a familiar system. That can happen. It can also be wrong. The workflow may genuinely be worse.

Acas recommends clear language and an open conversation rather than vague conflict labels. The practical value is that both people can discuss a decision instead of defending an identity.

Decide what evidence would be enough

Inquiry cannot continue forever. Before the conversation, define the decision you need, the time available, and the evidence that could alter the plan.

If the issue is value, demonstrate the relevant outcome. If it is workflow cost, observe the current process. If it is capability, provide training and test task completion. If it is authority, move the decision to the right owner.

Organizational-change research connects reactions to participation, job security, anticipated impact, employee-management relationships, and support. One empirical hospital study found several of these factors associated with resistance in its sample. The study does not diagnose another organization.

A later employee-voice study examines relationships among voice, involvement, commitment, and readiness. It supports listening as an evidence source, not a promise that participation removes disagreement.

The response should match the constraint. A higher priority needs a sponsor tradeoff. Missing value needs a better case or a smaller proposal. Limited capacity needs sequencing, support, or reassignment. Prior failure needs a design change or new evidence. Missing authority needs the right decision-maker. A material risk needs mitigation or acceptance by the authorized owner.

Do not keep asking the same person for an explanation when the organization created the problem. If three people believe they own the decision, clarify governance. If a deadline conflicts with another executive commitment, escalate the tradeoff. If the proposed outcome has no measure, define one before demanding adoption.

Timebox the diagnosis

Choose one test, one owner, and one decision date. A short workflow observation, prototype, data review, or bounded trial can be enough.

At the decision date, choose among redesign, added support, an explicit requirement, a changed owner, a deferred initiative, or escalation. State why.

The decision record can be short. It should name the behavior and impact, constraints tested, evidence reviewed, chosen action, owner, date, and conditions for revisiting the choice. Avoid recording speculation about personality or private circumstances.

Acas's 2025 conflict survey found that people used both manager discussions and direct informal discussions. That supports having more than one conversation route. It does not establish which route is correct for a particular workplace.

Know when to stop

Stop the diagnostic approach when the person refuses a required decision after a fair route, repeats a boundary violation, lacks authority, or the delay creates unacceptable risk. Move to the agreed governance process.

Bypass it when the facts involve serious misconduct, harassment, discrimination, retaliation, coercion, fraud, safeguarding, threats, or violence. [[Conversation Boundary or Escalation]] describes that decision.

Investigation is useful because a label closes inquiry too early. It becomes avoidance when the evidence already supports a boundary or formal route.

This page provides general workplace information, not legal or HR advice. It reflects sources reviewed on July 27, 2026. AI assistance was used for research organization, drafting, and validation. Publication remains unauthorized.