People — Stakeholders, communication & influence
A module for scenarios where the challenge is not technical but human: absent sponsor, resistant user, competing interests, poor communication, or blocked decision.
Estimated time : 85 min
Learning objectives
- Map stakeholder power, interest, and attitude.
- Adapt channel, level of detail, and communication frequency.
- Choose between collaboration, negotiation, facilitation, and escalation.
- Turn resistance into actionable feedback.
Key concepts
- Stakeholder register
- Artifact capturing identity, role, expectations, influence, attitude, and engagement strategy.
- PMBOK 8 — Stakeholders Performance Domain
- Power / interest grid
- Simple tool to tailor communication and engagement effort.
- Stakeholder analysis
- Pull communication
- Information available when the recipient needs it, useful for repositories, dashboards, and knowledge bases.
- PMBOK communications
- Escalation
- Moving a decision to the authorized level when the PM or team cannot resolve it within limits.
- PMBOK 8 — Governance
1. Identify what each actor really wants
On the exam, an unhappy stakeholder rarely signals simple bad mood. It often reveals an uncaptured expectation, underestimated operational impact, or poorly tailored communication.
| Profile | Need | PM action |
|---|---|---|
| High-power / low-availability sponsor | Short decisions and clear options | Prepare recommendations with impacts. |
| Resistant frontline user | Be heard and reduce change impact | Run listening, prototype, or pilot. |
| Influential technical expert | Technical risk acknowledged | Clarify assumptions and decision criteria. |
PMI reflex
Engaging does not mean satisfying every request. It means understanding, analyzing impact, prioritizing, and communicating transparently.
Stakeholder Engagement Assessment Matrix (current C vs desired D)
| Level | Description | Current / desired example |
|---|---|---|
| Unaware | Unaware of the project and its potential impacts. | Build awareness to move toward Neutral or higher. |
| Resistant | Aware but opposed to the change or its effects. | Frequent target: move C → D toward Supportive. |
| Neutral | Aware, neither supportive nor opposed. | Keep informed and seek buy-in. |
| Supportive | Aware and supportive of the project and the change. | Often the desired level D for most stakeholders. |
| Leading | Aware and actively engaged in ensuring success. | Desired level for key stakeholders and champions. |
Reading the matrix: C and D
Mark C (current) for the current engagement level and D (desired) for the target level. A gap where C ≠ D triggers a targeted engagement action, for example moving an actor from Resistant to Supportive.
Artifact → decision → PMI action map
Artifact
Stakeholder register + engagement plan
Decision
Which expectation, influence, or resistance must be addressed?
PMI action
Adapt message, channel, frequency, and involvement in the decision.
Avoid: Sending more reporting without addressing the real concern.
Recommendations
- Update stakeholder analysis whenever behavior changes.
- Look for the need behind the request.
- Compare current (C) and desired (D) engagement to target your actions.
Tips
- Resistance = information to use before escalation.
- The PM facilitates decisions; they do not impose them without authority.
Chapter quiz
1.A key user rejects a new feature during review. What is the best first action?
2.In the engagement matrix, a key actor is marked Resistant (current) while the project needs them Supportive (desired). Which action is most PMI-aligned?
2. Design useful communication
Effective communication is not message volume. It answers four questions: who needs to know what, why, when, and in what form.
- Segment audiences: sponsor, team, customer, users, vendors.
- Tailor the level: decision, risk, action, information.
- Choose the channel: meeting, board, report, direct conversation.
- Confirm understanding when stakes are critical.
Exam trap
Sending one report to everyone is rarely the best answer. The right reflex is to tailor the message to the stakeholder.
Canaux = n(n − 1) / 2Number of potential communication channels for n stakeholders.
Communication channels calculation
A project team has 6 stakeholders. The sponsor adds a 7th person. How many potential communication channels exist before and after?
- With n = 6: 6 × (6 − 1) / 2 = 6 × 5 / 2 = 30 / 2 = 15 channels.
- With n = 7: 7 × (7 − 1) / 2 = 7 × 6 / 2 = 42 / 2 = 21 channels.
- Adding a single person raises channels from 15 to 21, that is 6 more.
15 channels for 6 stakeholders, 21 for 7: each new actor sharply increases communication complexity.
Why this formula matters
Growth is non-linear: doubling the team does not double channels, it nearly quadruples them. This is the argument for structuring communication rather than broadcasting everything to everyone.
Artifact → decision → PMI action map
Artifact
Stakeholder register + engagement plan
Decision
Which expectation, influence, or resistance must be addressed?
PMI action
Adapt message, channel, frequency, and involvement in the decision.
Avoid: Sending more reporting without addressing the real concern.
Recommendations
- Tie each communication to an expected decision or behavior.
- During uncertainty, increase transparency without overwhelming people.
Tips
- Push for urgency; pull for reference; interactive for ambiguity.
- A complex conflict is better handled in conversation than email.
Chapter quiz
1.The sponsor wants only decisions and major risks. Which format fits best?
2.A team of 5 grows to 8. By how much do potential communication channels increase?
3. Influence without forcing, escalate without escaping
The best PMP answer often seeks resolution at the lowest competent level. Escalation becomes correct when authority, budget, priority, or risk threshold exceeds the PM's mandate.
| Situation | Expected response |
|---|---|
| Misunderstanding or interpersonal tension | Private discussion, active listening, root cause search. |
| Decision outside PM authority | Prepare options, impacts, recommendation, and escalate. |
| Blockage between two departments | Facilitate a decision workshop with shared criteria. |
The five conflict-handling modes (Thomas-Kilmann)
The five Thomas-Kilmann modes and when to use them
| Mode | Posture | When to use |
|---|---|---|
| Collaborate / problem-solve (PMI preferred) | Win-win: seek a solution that satisfies all parties. | Stakes high for everyone, time available, lasting buy-in needed. |
| Compromise | Each side gives up something: a partial, quick solution. | Parties of equal power, tight deadline, temporary agreement acceptable. |
| Smooth / accommodate | Emphasize points of agreement, yield on the rest. | Preserving the relationship outweighs the issue, or you are wrong. |
| Force / direct | Impose one's view: win-lose. | Critical emergency, safety, or an essential unpopular decision. |
| Avoid / withdraw | Postpone or withdraw from the conflict. | Trivial issue, need to cool down, or more information required. |
PMI reflex on conflict
PMI favors collaborate / problem-solve because it addresses the cause and preserves the relationship. Force and avoid are rarely the right answer, except in an emergency or for a trivial issue.
Artifact → decision → PMI action map
Artifact
Stakeholder register + engagement plan
Decision
Which expectation, influence, or resistance must be addressed?
PMI action
Adapt message, channel, frequency, and involvement in the decision.
Avoid: Sending more reporting without addressing the real concern.
Recommendations
- Escalate with options, not with a raw problem.
- Keep a record of decisions and owners.
- Favor collaborate / problem-solve when stakes and time allow.
Tips
- First action: understand. Second: collaborate. Escalate only if needed.
- Well-prepared escalation accelerates; premature escalation damages trust.
Chapter quiz
1.A decision exceeds the PM's authority. What should be sent to the committee?
2.Two experts disagree on a critical architecture decision; the timeline allows it and buy-in from both is needed. Which conflict-handling mode does PMI favor?
Decision toolkit
PMP decision trees & running case
Use this when two answers look right: qualify the context, choose the artifact, then act.
Team conflict
Two people or groups block a decision or blame each other.
1. The conflict is new or moderate.
Decision: Address it early, privately, with the involved parties.
Action: Facilitate a fact-based discussion and seek the root cause.
2. The conflict involves roles or responsibilities.
Decision: Clarify work governance.
Action: Update the RACI, team charter, or communication plan.
3. The conflict persists after facilitation.
Decision: Escalate only with evidence and options.
Action: Present impacts, alternatives, and a recommendation to the sponsor/manager.
Trap: Forcing a solution or escalating immediately is rarely the first PMI action.
Responsible escalation
The project manager can no longer resolve a blocker alone.
1. The PM has not yet spoken with the parties involved.
Decision: Do not escalate too early.
Action: Meet the parties, clarify facts, impacts, and options.
2. The blocker exceeds the PM's authority.
Decision: Escalate with a recommendation.
Action: Present context, options, impact, and the decision needed.
3. There is an ethical or compliance violation.
Decision: Use the appropriate formal channel.
Action: Document without accusation and follow organizational policy.
Trap: Escalating without analysis or options transfers the problem instead of managing it.
Resistant stakeholder
A key user rejects the solution, slows approvals, or blocks adoption.
1. Resistance comes from lack of understanding.
Decision: Adapt communication.
Action: Connect the change to their benefits, impacts, and expectations.
2. Resistance comes from a real business risk.
Decision: Do not treat it as personal opposition.
Action: Analyze the concern, update risks/requirements, and co-create the response.
3. Adoption remains low.
Decision: Strengthen the change management plan.
Action: Add training, champions, feedback loops, and adoption metrics.
Trap: Ignoring a resistant stakeholder often turns adoption risk into benefits failure.
AI & sustainability project: energy optimization
Charter
Objective: reduce energy consumption by 12% with a responsible AI model.
Backlog / WBS
Hypotheses, experiment backlog, model card, ethical thresholds, controlled pilots.
Stakeholders
- ESG sponsor, data science, operations, IT, AI compliance, field users.
- Success measured by savings, adoption, explainability, and no negative HSE impact.
Risks
- Data bias, non-explainable model, operator rejection.
- Energy optimization that degrades quality or safety.
Change
Request: automate a critical decision. Response: assess risk, human control, compliance, and acceptability.
EVM
Connect model/deployment cost to measured benefits; include AI operating costs.
Closure
Model monitoring, operations handover, carbon/energy benefits tracking, responsible audit.
Practical examples
Silent sponsor
Scenario : The sponsor misses three steering meetings and scope decisions stall.
Project manager's action : Clarify the decision need, propose short options, and agree on an arbitration mechanism.
Influential resistant user
Scenario : A frontline manager blocks adoption because the target process adds duplicate entry.
Project manager's action : Listen, measure operational impact, and adjust the solution or adoption plan.
Exam strategy
- Before escalating, look for direct discussion and root cause.
- A resistant stakeholder is not an enemy: often it is a source of risk or hidden requirement.
- Do not communicate more; communicate better, at the right level and time.
Module assessment
1.What is the best indicator of poorly tailored communication?
2.When is escalation most justified?