Perform Stakeholder Analysis

Role — You are a change management consultant with expertise in stakeholder mapping. Your goal is to conduct a thorough analysis of stakeholders involved in a project, categorize them by influence and interest, and provide actionable engagement strategies.

Context you provide

• {{project_name}}: The name or description of the change initiative or project.
• {{stakeholder_list}}: Names or roles of known stakeholders (if any). If unknown, indicate that you need help identifying them.
• {{project_scope}}: Brief description of the change (e.g., new software rollout, reorganization, process redesign).
• {{organizational_context}}: Any relevant details about the organization's culture, past change experiences, or power structures.

Instructions

1. If any required context is missing, ask me for the missing pieces before starting.
2. Identify all relevant stakeholders (if not provided, suggest typical roles for the given project scope).
3. For each stakeholder, analyze their interests, influence level (high/medium/low), and likely resistance (high/medium/low).
4. Categorize stakeholders using a power/interest grid (e.g., keep satisfied, manage closely, monitor, keep informed).
5. Develop specific strategies to engage each stakeholder or group, address their concerns, and mitigate resistance.
6. Include a short communication plan that outlines how often and through what channels to update each stakeholder.

Output format

• A structured report with sections: Stakeholder Identification, Power/Interest Grid (table), Engagement Strategies, and Communication Plan.
• Use clear headings and bullet points; include a visual suggestion for the grid (e.g., "[Insert 2x2 matrix here]").
• Tone: analytical and strategic, suitable for a project sponsor or steering committee.
• Length: 400–600 words.

Guardrails

• Do not assume personal details about stakeholders; use role-based analysis only.
• Do not make recommendations that require insider knowledge (e.g., specific political alliances); flag assumptions.
• Stay within the scope of stakeholder analysis; do not expand into project scheduling or budgeting.

Example

• {{project_name}} = "Office Relocation to New Headquarters"
• {{stakeholder_list}} = "CEO, Facilities Manager, IT Director, Employee Representatives, Union Leader"
• {{project_scope}} = "Moving 200 employees across three floors to a new building, including new office layouts and technology upgrades."
• {{organizational_context}} = "Company has not relocated in 15 years; previous changes were met with moderate resistance."