5.2Stakeholder engagement & expectation management

Stakeholder analysis is not a one-time exercise—engagement levels shift as a project progresses. It is not unusual for a stakeholder who was initially "neutral" to turn to resistance as dissatisfaction accumulates from unaddressed requirements or a lack of information. This section covers the judgment needed to spot early signs of resistance and re-select an engagement strategy appropriate to power and interest, as well as agreement-building techniques that prevent expectation gaps from arising in the first place.

5.2.1Signs of resistance and choosing an engagement strategy by quadrant

• Signs of resistance commonly appear as changes in behavior: increasing absence or unresponsiveness in meetings, a sudden drop in questions or comments (or, conversely, a sudden surge of objections to fine details), approval or agreement processes stalling without clear reason, or complaints reaching the PM secondhand through informal channels. Because these signals are hard to quantify, the PM must actively and continuously watch for them in day-to-day interactions.
• Once a sign of resistance is detected, the PM first re-confirms that stakeholder's power/interest quadrant and re-selects an engagement strategy accordingly. For example, resistance from a "low power, high interest" stakeholder is often caused by insufficient information, so the response is to switch to more frequent, two-way dialogue. Resistance from a "high power, high interest" stakeholder is often caused by insufficient involvement in the decision-making process, and the highest-priority response is to hold an individual conversation, directly hear their concerns, and involve them in building agreement. Simply increasing generic briefing sessions without pinpointing the cause of resistance (insufficient information, insufficient involvement, or dissatisfaction that requirements were not reflected) often fails to address the root cause.

5.2.2Visualizing expectations and building agreement

• A gap in expectations among stakeholders often arises because each person implicitly pictures a different image of success. To prevent this, rather than relying solely on verbal exchange, it is effective to put requirements and expectations into a written document, such as a scope statement or acceptance criteria, and have stakeholders explicitly confirm and agree to it. A documented agreement substantially reduces later "he-said-she-said" disputes and misalignment at the acceptance stage.
• Expectation management does not end with a single agreement; it must be operated as an iterative process in which, whenever circumstances change as the project progresses (a scope change, a delay, a cost overrun, etc.), the PM explains the impact to the relevant stakeholders, and if necessary, realigns expectations and secures renewed agreement.

Suppose that on a core-system renewal project, a procurement department director—initially at a "supportive" engagement level and positioned as "high power, high interest" on the power/interest grid—began, midway through the project, to frequently miss regular meetings and stopped raising questions about materials sent in advance. The PM interprets this as a sign of resistance and first re-confirms this director's quadrant, finding that their influence over decisions and interest both remain high. Resistance from a high-power, high-interest stakeholder is most often caused by insufficient involvement in the decision-making process, so rather than adding more generic briefings at the full group meeting, the PM instead sets up a one-on-one conversation with the director to directly hear their concerns. The conversation reveals that, in fact, a scope change several months earlier had proceeded to agreement without fully explaining its impact on procurement (consistency with the existing ordering workflow), and the dissatisfaction that "my concern was not reflected in the decision" had been showing up as absences. The PM puts this concern through the formal change-control process for re-evaluation, produces a revised scope statement reflecting procurement's requirements, and explicitly re-secures agreement with the director. Had the PM instead assumed at this stage that "the increased absences are probably just because they're busy" and responded only by adding more briefings for everyone without digging into the cause, the root cause—dissatisfaction from insufficient involvement—would have gone unaddressed, risking the resistance deepening further and escalating into strong opposition at the final acceptance stage. As this shows, when a sign of resistance is detected, the judgment this section calls for is to separate the stakeholder's power/interest quadrant from the root cause of the resistance (insufficient information vs. insufficient involvement) before choosing a response, rather than reacting to surface behavior alone.

5.2.3Section summary

• Actively watch for signs of resistance (increased absence, sudden unresponsiveness, stalling, informal complaints), and re-confirm the quadrant upon detection
• Resistance from high power/high interest is often caused by insufficient involvement—prioritize individual dialogue; resistance from low power/high interest is often caused by insufficient information—increase dialogue frequency
• Do not rely on verbal exchange for expectations—document them and explicitly agree, and iteratively realign and re-agree whenever circumstances change