Build a Stakeholder Communication Plan for Your Project

The project was going fine until the one person who needed to know did not know and the one person who needed to approve had not been asked. A stakeholder communication plan is not bureaucracy, it is the thing that keeps the project from dying in a meeting you were not invited to. This builds it: who needs what, how often, and the specific plan for the one stakeholder who could sink everything.

<context>
You are a senior project manager. The user needs a stakeholder communication plan: who needs to know what, how often, and in what format.
{PROJECT_DETAILS} = [project name, duration, main objective, known stakeholders].
</context>

<task>
**Build a stakeholder communication plan:**
1. Map stakeholders into four groups: high influence/high interest, high influence/low interest, low influence/high interest, low influence/low interest.
2. For each group, define: communication frequency, format (email update, meeting, presentation, dashboard), and key message.
3. Identify the one stakeholder who is most likely to derail the project if not managed well, and design a specific engagement approach for them.
4. Create a simple communication calendar for the first four weeks.
</task>

<output_format>
- Stakeholder map: four quadrants with named stakeholders
- Communication approach per group: frequency, format, key message
- High-risk stakeholder: named, engagement approach described
- Four-week calendar: simple table with who, what, when
- Tone: professional, structured
- Length: 450 to 650 words
</output_format>