PMP Assessing Readiness and Resistance to Change

Readiness and resistance matter because low adoption is often treated as a late surprise when it is really an early signal. PMP questions here usually test whether the project manager diagnoses why people are not ready instead of assuming resistance is just stubbornness.

Readiness and Resistance Are Different but Linked

Readiness is the organization’s ability and willingness to absorb the change. Resistance is the pushback, hesitation, or nonadoption that appears when readiness is weak or the change is poorly supported.

Typical readiness dimensions include:

• awareness
• skills and confidence
• local management support
• capacity to change
• trust in the change rationale

Resistance can come from fear, overload, incentive mismatch, unclear ownership, or poor communication.

    flowchart TD
	    A["Assess audience"] --> B["Readiness level"]
	    A --> C["Resistance source"]
	    B --> D["Choose targeted intervention"]
	    C --> D
	    D --> E["Reassess engagement and acceptance"]

Diagnose the Source Before Choosing the Intervention

The strongest response depends on why resistance exists. Examples:

• low awareness may need clearer communication
• low skill may need training and support
• low trust may need sponsor visibility and listening
• low capacity may require pacing changes or workload relief

PMP questions usually reward diagnosis first. Generic motivation or pressure is weaker than a targeted intervention tied to the real barrier.

Plan Interventions That Improve Acceptance

A good intervention plan names:

• the affected group
• the barrier
• the intervention
• the owner
• the indicator that shows improvement

That turns “manage resistance” into a practical adoption plan.

Example

A team says it supports the project but keeps avoiding training registration. A weak interpretation is “they resist change.” A stronger interpretation may be that training conflicts with peak workload and managers are not protecting time for attendance. The intervention should address capacity and manager support, not just resend reminders.

Common Pitfalls

• Labeling all concern as resistance.
• Using the same intervention for every group.
• Assuming communication solves skill or workload problems.
• Measuring attendance instead of actual readiness or acceptance.

Check Your Understanding

Sample Exam Question

Scenario: A project will introduce a new control workflow. The affected operations team says it supports the change, but training attendance is low and managers keep postponing preparation activities. One stakeholder says the team is simply resistant and should be told to comply.

Question: What is the strongest next step?

• A. Assess whether the problem is capacity, skill confidence, manager support, or motivation, then target interventions accordingly
• B. Escalate immediately on the assumption that resistance is the only explanation
• C. Send another generic reminder and assume the issue is solved
• D. Drop readiness analysis because the team verbally supports the change

Best answer: A

Explanation: A is strongest because the observed behavior may come from several barriers, not just attitude. The project manager should diagnose the actual cause and then choose targeted support, such as workload protection, training, manager reinforcement, or clearer communication. That is stronger than labeling the team resistant without evidence.

Why the other options are weaker:

• B: Escalation without diagnosis may target the wrong problem.
• C: Generic reminders do not solve readiness gaps by themselves.
• D: Verbal support does not prove practical readiness.

Key Terms

• Readiness: The degree to which a group is able and willing to absorb a change.
• Resistance source: The underlying reason people are pushing back or not engaging.
• Targeted intervention: A change-support action matched to a specific barrier.