Mandate, value, stakeholders and tailoring · Lesson 2
Stakeholder analysis and engagement plan
7 min read
Lesson objectives
Turn an authorized project assignment into a concise charter, value map, constraints and traceable decisions.
From a stakeholder list to actionable engagement
Stakeholders are not only those who sign the budget. They include people and groups who can affect the project or are affected by its outputs, inside or outside the organization. In the training network they include learners, reception staff, instructors, support, sponsor, supplier and people with different access needs. Begin with two complementary questions: who can change the work’s direction, and whose work or use of the service will change even without formal influence? Asking only the first may produce a solution supported by management but difficult to use. Do not assume that everyone in an occupation, age group or country has identical needs.
A useful register supports action rather than merely listing names. It can record role, need or concern, degree of impact, decision authority, suitable communication channel, relationship owner and next action. Collect only necessary information and avoid disparaging personal labels. Write “needs evidence that service will not be disrupted” instead of “resists change.” Analysis is provisional and changes with new information. A power-and-interest matrix helps allocate attention; it does not authorize exclusion of people who bear significant effects. Add impact severity or access barriers when useful, because limited influence does not make a user’s experience or the need to listen unimportant.
In our learning application, distinguish three dimensions: power is the ability to change decisions or resources; interest is direct attention to the project; impact is how much work or use will change. Someone able to withhold a resource may have high power despite rarely attending. A low-power user may still experience a complete disruption. Use provisional descriptive categories, not judgments about people’s worth. Base analysis on a role or stated observation and mark uncertainty rather than invent motives.
Role
Assumed power / interest / impact
Action and timing
Owner and evidence
Sponsor
High / high / medium
Review scope options before the trial gate
Project manager; reasoned decision within authority
Reception
Limited financial power / high / high
Trial cancellation before requirements are fixed
Requirements analyst; seat-update observation and recorded response
Trial users
Low / needs verification / high
Test confirmation in an accessible format before acceptance
Trial coordinator; observed task result, not assumed satisfaction
Operations owner
High acceptance authority / high / high
Review support and handover before launch
Project manager; acceptance or explicit acceptance conditions
Revisit the engagement plan as work moves from design to trials and handover, because the relevant people and questions change. Observe useful results such as resolving a critical concern, an operational owner understanding responsibilities, or a user checking an acceptance scenario. Do not turn such observations into a causal claim that one meeting produced every improvement. Where interests conflict, explain the criteria, alternatives, decision and authority, and provide an appropriate objection channel. When applying the method at work, use role labels rather than personal names in the exercise. The resulting tool transfers across small organizations, public services and community initiatives without assuming one national or organizational culture.
Lesson summary
Stakeholder analysis connects roles and needs with power, interest and impact, then turns them into purposeful engagement. The register and plan change with evidence; message volume does not prove needs are met, and consultation confers neither financial authority nor automatic acceptance.