
Stakeholder Resistant to Change: Awareness With Opposition
PMBOK v8 Definition
A stakeholder who is aware of the project and its potential impacts but resistant to any changes that may occur as a result of the work or outcomes of the project is classified at the Resistant level in the Stakeholder Engagement Assessment Matrix. This stakeholder understands the project exists and knows what effects it may produce, yet actively opposes the work or its outcomes. The resistance stems from unwillingness to accept changes, not from lack of knowledge or awareness.
Why It Matters for the Exam
The Resistant engagement level is frequently tested because it represents a critical midpoint between unawareness and active opposition. PMI exam questions commonly present scenarios where a stakeholder knows about the project but blocks progress, requiring the project manager to select the correct engagement classification and determine appropriate strategies to move this stakeholder toward Supportive or Leading levels. This concept appears in situational questions about stakeholder analysis, engagement planning, and communication management.
Key Points to Remember (for the exam)
-
Exact Definition: The stakeholder is aware of the project and potential impacts but resistant to any changes that may occur as a result of the work or outcomes of the project. These stakeholders will be unsupportive of the work or outcomes.
-
Five Engagement Levels (C to D): The Stakeholder Engagement Assessment Matrix uses five levels: Unaware, Resistant, Neutral, Supportive, and Leading. Current engagement is marked as C, desired engagement as D.
-
Key Distinction from Unaware: An Unaware stakeholder does not know about the project or its impacts. A Resistant stakeholder knows but opposes changes. This is the most common confusion on the exam.
-
Desired State: The project team assesses the desired (D) engagement level essential to ensure project success. For resistant stakeholders, the target is typically Supportive or Leading.
-
Not a Fixed State: Engagement levels change throughout the project. A stakeholder may move from Resistant to Neutral through effective engagement strategies.
-
Knowledge vs. Support: The resistant stakeholder possesses knowledge (they are aware) but withholds support. This differs from the Knowledge benefit category where specialist knowledge aids project delivery.
-
Risk Implication: Resistant stakeholders represent a source of overall project risk and may contribute to individual threats if their opposition creates uncertainty or blocks critical decisions.
Typical PMI Exam Example
A project to implement a new inventory management system is underway. The warehouse manager is fully aware that the system will change daily workflows and reduce manual data entry. However, the manager actively opposes the implementation, telling staff the system will fail and refusing to provide required input data. According to the Stakeholder Engagement Assessment Matrix, this stakeholder is at the Resistant level. The project manager should document current engagement as C = Resistant and desired engagement as D = Supportive or Leading.
PMI Exam Traps
-
Trap: Confusing Resistant with Unaware
-
Reality: Unaware means no knowledge of the project. Resistant means awareness exists but opposition to change is present. A stakeholder cannot be resistant if they do not know about the project.
-
Trap: Assuming Resistant means the stakeholder will never change
-
Reality: The Stakeholder Engagement Assessment Matrix tracks current (C) and desired (D) levels. The project team actively works to move resistant stakeholders toward supportive or leading positions through engagement strategies.
-
Trap: Treating all resistant stakeholders identically
-
Reality: Resistance may stem from different sources (fear of job loss, loss of power, lack of trust). The exam tests whether you recognize that awareness exists but the engagement strategy must address the specific cause of resistance.
-
Trap: Conflicting Resistant with the Contribution benefit category
-
Reality: Contribution involves providing resources or advocacy. A resistant stakeholder may still contribute funds or resources while opposing changes, but their advocacy is absent or negative.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Stakeholder Engagement Assessment Matrix | Direct container | The matrix shows C (current) and D (desired) for each stakeholder across five levels. Resistant is one of five levels. |
| Overall Project Risk | Effect relationship | Resistant stakeholders increase overall project risk by creating uncertainty and potential blockages. Responses to overall risk may include engaging resistant stakeholders. |
| Project Charter | Input source | Stakeholders identified in the project charter may include resistant individuals. The charter authorizes the project despite known resistance. |
| Decision-Making Techniques | Mitigation strategy | When resistant stakeholders have power, the project team may use convergent decision-making after individual input to prevent undue influence from charismatic or senior resistant stakeholders. |
Quick Review Questions
-
A stakeholder knows the project will automate their department's reporting process. They express concern and actively refuse to cooperate with data requests. What is their current engagement level in the Stakeholder Engagement Assessment Matrix?
-
What is the key difference between an Unaware stakeholder and a Resistant stakeholder in terms of project knowledge and support?
-
A project manager documents a stakeholder's current engagement as "C" and desired engagement as "D." What do "C" and "D" represent in the Stakeholder Engagement Assessment Matrix?
-
If a resistant stakeholder holds specialist knowledge that could benefit the project, which benefit category does this represent, and how should the project manager approach this situation?
-
A resistant stakeholder is also a senior executive with significant organizational influence. According to the PMBOK v8 context, what approach should the project team use when generating decision alternatives involving this stakeholder?
PMBOK v8 Reference
Section 5.2.2.1 - Stakeholder Engagement Assessment Matrix (Figure 5-23)