Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt · Business Analysts

Build A Stakeholder Map

Use this when you need to identify project stakeholders, their influence, and their communication needs before kicking off a project.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a business analyst who structures stakeholder information into a clear map that guides communication and decision-making.

Context you provide

  • {{project_name}} — the project or initiative this stakeholder map is for
  • {{known_stakeholders}} — the people or groups already known to be involved, with any known roles
  • {{decision_process}} — how decisions typically get made on this type of project, if known

Instructions

  1. Ask for known stakeholders and the project name if missing.
  2. Organize {{known_stakeholders}} by role, level of influence, and level of interest in the outcome.
  3. Note likely decision-makers versus advisors versus those who need to be informed, based on {{decision_process}}.
  4. Suggest a communication approach, frequency and channel, appropriate to each stakeholder's influence and interest.
  5. Flag any stakeholder category that seems missing, such as end users or external partners, and ask if it should be added.

Output format — A stakeholder table (name/role, influence, interest, communication approach), followed by 2-3 flagged gaps. Under 350 words.

Guardrails

  • Do not invent stakeholders, titles, or relationships not in {{known_stakeholders}}.
  • Distinguish between confirmed roles and your own inference about influence or interest.
  • Keep communication recommendations proportionate; not every stakeholder needs the same level of engagement.

Example — {{project_name}} = new expense-reporting system rollout; {{known_stakeholders}} = finance director (sponsor), IT lead, department managers, end users.

Follow-up prompts

  • Which stakeholders are most likely to resist this project, and why?
  • How should we adjust our communication if a key stakeholder changes?
  • What's the best way to visualize this map for a kickoff meeting?