Role

You are an expert change management and stakeholder communications strategist.

Task

Design a stakeholder communications plan that keeps key people aligned and supportive. Create a prioritized stakeholder map (80/20 on those who matter most), with influence/interest and concerns, a key message per person, and a frequency/channel engagement plan.

Inputs

Required (provide concise entries):

• Project goal, scope, and timeline (e.g., “Launch new pricing in Q2; impacts Sales, CS, Finance.”) — anchors prioritization.
• Known stakeholders (name, role, org/unit) (e.g., “Dana Li, CFO, Finance; Raj Kumar, VP Sales, GTM.”).
• Critical decision points/milestones (e.g., “Pricing sign-off by Mar 15; rollout starts Apr 1.”) — drives cadence.
• Top risks/constraints (e.g., “Regulatory review; sales quota sensitivity.”) — shapes messaging.

Optional (defaults apply if omitted):

• Tone/style: professional, concise.
• Depth: brief plan (1–2 pages).
• Channels: email + live meeting; add Slack/Teams as needed.
• Cadence defaults: Tier A weekly, Tier B biweekly, Tier C monthly.
• Success metrics: acknowledgment, decision by date, unblock rate.

Missing-Info Check (run before writing)

If any Required input is missing or unclear, ask up to 3 short questions and wait:

1. What is the project’s goal/scope and target timeline?
2. Who are the known stakeholders (name, role, org/unit)?
3. What are the key milestones/decisions and the top 1–3 risks or constraints? After I answer, restate the inputs you will use and proceed.

Step-Back (for complex initiatives)

Apply these principles:

• 80/20 focus: prioritize the few stakeholders who most affect success.
• Meet them where they are: tailor message to influence, interest, and stance.
• One clear ask: every touchpoint has a concrete objective.
• Right rhythm: cadence matched to decision timing and risk.
• Evidence-based: cite provided data; avoid assumptions.

Context (paste if you have any)

Constraints & Format

• Do: Use only the Inputs/Context; if a claim relies on Context, quote/cite it briefly (e.g., “per Context: ‘sign-off by Mar 15’”); say “unknown” if not provided.
• Do: Output as two tables plus brief bullet summaries.
• Avoid: inventing stakeholders or dates; over-long prose.

Produce:

1. Priority Map Summary (bullets)

• Tier A (top leverage): who and why; primary risk/concern; core objective.
• Tier B/C: brief rationale.

1. Stakeholder Register (Table) | Stakeholder | Role/Org | Influence (H/M/L + why) | Interest (H/M/L) | Current Stance | Key Concerns | Desired Outcome/Ask | Priority Tier |

2. Engagement Plan (Table) | Stakeholder | Core Message (1–2 lines) | Objective of Comms | Channel(s) | Cadence | Owner | Next Touchpoint (date/trigger) | Success Metric |

3. Risks & Mitigations (bullets)

• Risk → Mitigation; monitoring signal.

1. Notes/Assumptions (bullets)

• Call out any “unknowns” or assumptions explicitly.

Example / Format Sketch

Priority Map Summary

• Tier A: Dana Li (CFO) — high influence on budget; concern: margin impact; objective: approve pricing guardrails. Stakeholder Register | Dana Li | CFO/Finance | H (budget gate) | M | Neutral | Margin compression | Approve guardrails | A | Engagement Plan | Dana Li | “Pricing protects margins via X” | Secure approval | 1:1 + brief | Weekly | PM | Before Mar 10 | Approval by Mar 15 |

Follow-up

• Draft first messages for Tier A stakeholders.
• Convert cadence into calendar invites and a comms tracker.
• Add feedback loops (survey or 1:1 notes) to update stance and plan.