The prompt
Score 10 of 10, Excellent
Use it when You need who cares about the project, what each needs to hear, and how often.
- {{project_summary}}
- {{timeline}}
- {{channels}}
- {{stakeholders}}
Full prompt and why it works
Prompt
Project: {{project_summary}} Timeline and key moments: {{timeline}} Channels available to us: {{channels}} Stakeholders, with what I know about each (role, interest, how they feel about the project): """ {{stakeholders}} """ Task: Map the stakeholders above and plan the project's communications with them, so that each group hears what it needs, from the right person, at the right time, and nobody learns about a change that affects them second-hand. Format: 1. Stakeholder map: a table with the columns Stakeholder (group or role), What they care about, Influence on the project (high, medium, low), How much it affects them (high, medium, low), Current view (supportive, neutral, concerned or unknown), Approach. For the approach, use: work closely with (high influence and high effect), keep satisfied (high influence, lower effect), keep informed (lower influence, high effect), or check in occasionally (both lower). 2. Key messages: three, in plain words, to be used consistently everywhere. 3. Communication plan: a table with the columns Audience, What they need to hear, Channel, How often or when, Sender, How they can respond. 4. Calendar: communications tied to the key moments in the timeline. 5. Watch list: stakeholders likely to resist or be surprised, and how to involve them early. Requirements: - Under 700 words plus the tables. - Use roles and groups, not personal judgments about individuals, and write it so it could be shared with the people in it without embarrassment, since documents like this get forwarded. - Use only what I have told you. Where I have not said how a stakeholder views the project, write "unknown" and add an action to find out; do not guess. - The sender should be the person whose word carries weight with that audience: usually the sponsor for why the change matters, and people's own managers for what it means for them. - Every strongly affected group should hear about changes before they happen, with a way to ask questions. If a group seems to be missing, for example the people who will support the result after the project ends, suggest it at the end rather than adding it to the map.
Variables
- {{project_summary}}
- What the project is and what it will change, in two or three sentences.
- {{timeline}}
- Key dates such as approval, pilot and go-live.
- {{channels}}
- For example team meetings, email, the intranet, all-hands meetings, chat channels.
- {{stakeholders}}
- Each group or role, with what you know about their interest and how they feel about the project.
Why it works
- Format. A map of influence and effect, with a plain rule for how to approach each group, turns a list of names into a plan for who needs the most attention.
- What to avoid. It sticks to roles and keeps personal judgments out, because stakeholder plans get forwarded and should survive being read by the people in them.
- If unsure. Where you have not said how a group views the project, it writes "unknown" and adds an action to find out, instead of guessing.