High power · High interest
Manage closely. Involve in key decisions, resolve concerns quickly, and build a durable working relationship.
A stakeholder can affect, be affected by, or perceive being affected by a project. Management is not “sending updates”; it is continuously understanding interests, influence, expectations, and the relationships needed to create value.
Manage closely. Involve in key decisions, resolve concerns quickly, and build a durable working relationship.
Keep satisfied. Give concise, relevant assurance; avoid flooding them with detail.
Keep informed. Invite feedback and use them as informed advocates or domain experts.
Monitor. Use lightweight communication and reassess if power or interest changes.
Power/influence, impact/influence, and the stakeholder cube add dimensions. A salience model considers power, legitimacy, and urgency.
Upward to sponsor/governance; downward to team; outward to customers/vendors/public; sideways to peers and other managers.
Classification guides effort, not respect. A low-power user may hold critical knowledge or gain influence later.
An engagement assessment matrix compares today’s stance with the stance needed for success.
Does not know the project or its likely impact. First create awareness in relevant language.
Aware and opposed. Listen for legitimate loss, risk, incentives, or trust problems before persuading.
Aware but neither supportive nor resistant. Clarify relevance and invite useful participation.
Understands and supports change. Maintain trust and give meaningful roles.
Actively champions success. Equip them with evidence, authority, and feedback channels.
Who needs what information, why, when, in what format/channel, from whom, and how feedback will be captured?
Interactive for ambiguity; push for known recipients; pull for large information repositories.
Ask, paraphrase, confirm, surface emotion, and distinguish positions (“what”) from interests (“why”).
Collaborate/problem-solve for durable agreement; compromise when time matters; avoid or accommodate only when context justifies it.
Monitor relationships through observation, feedback, issue logs, sentiment, participation, decision latency, and adoption signals. A delivered message is not proof of shared understanding.
Explain impacts, limits, assumptions, and decision criteria honestly.
Seek voices that are easy to miss, especially those affected without formal authority.
Protect sensitive stakeholder assessments; separate observations from unsupported judgments.
Assign owners and dates to commitments; close the feedback loop.