Map project stakeholders by influence and interest

Business automationKINDA1 method

KINDA — AI can help, with a person in the loop.

1 method on the page: 1 prompt.

Use cases

Methods

Paste into a general LLM and map project stakeholders by influence and interest.

prompt

LLMPrompt

Prompt

Copied 0

You are a senior healthcare project management consultant. I need you to perform a comprehensive Stakeholder X-Ray analysis for my project.

**Project Context:** [DESCRIBE YOUR PROJECT — e.g., EHR migration, new clinic build-out, telehealth expansion, revenue cycle overhaul]

For every stakeholder group you identify, provide:

1. **Stakeholder Name/Role** (be specific — not just "leadership" but "CMO," "Nurse Manager — Med/Surg," "Revenue Cycle Director")
2. **Influence Level** (High / Medium / Low) — their power to accelerate or kill the project
3. **Interest Level** (High / Medium / Low) — how much they care about the outcome
4. **Stance** (Champion / Supportive / Neutral / Resistant / Hostile)
5. **What They Care About Most** (1 sentence — their real motivation)
6. **Hidden Risk** (what could go wrong if you ignore them)
7. **Engagement Strategy** (1-2 sentences — how to win them over or neutralize resistance)

Organize into a table. Then provide:
- A **Power/Interest Grid** summary (who goes in each quadrant)
- **Top 3 Stakeholders to Engage First** with rationale
- **The One Stakeholder Everyone Forgets** (and why they matter)

Be specific to healthcare. Think about clinical staff, IT, compliance, finance, patients, unions, and vendors.

Add a method

How you would do this use case, in plain words. Anyone can post.

The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.

All use cases:GET /api/jobs
This use case:GET /api/jobs/stakeholder-influence-interest-map
Schema:GET /api/jobs/schema
Add a method: POST /api/jobs/method — same fields as the form. No API key yet.

A bad request returns JSON like {"error":"Method description is required"} with status 400.

Field	What it is
`jobId`	This use case. Review queue uses `useCaseTitle` + `email` instead.
`summary`	Method description. Shown on the card. Also accepts `title`.
`products`	Optional. Array of `{ name, url }`. Legacy: `tools`.
`prompts`	Optional. Array of prompt strings. Legacy: one `prompt` string.
`skills`	Optional. Array of `{ text, url }`. Legacy: `skill` + `skillUrl`.
`authorName`	Author name. Legacy live field: `postedBy`.
`author`	Optional 𝕏 handle. Legacy live field: `creditHandle`.
`parts`	Optional. Inferred from products, prompts, and skills if omitted.`standalone-product`, `ai-agent`, `ai-tool`, `skill`, `prompt`. Do not send a prompt/product/agent/skill radio.

{
  "jobId": "stakeholder-influence-interest-map",
  "summary": "Turns a Zoom recording into notes and action items with owners",
  "products": [
    {
      "name": "Claude",
      "url": "https://claude.ai"
    }
  ],
  "prompts": [
    "Turn this transcript into notes and action items with owners."
  ],
  "skills": [
    {
      "text": "Watch a folder. When a transcript lands, write notes with owners.",
      "url": "https://example.com/zoom-notes.md"
    }
  ],
  "authorName": "Alex Rivera",
  "author": "@handle"
}