← ClaudeAtlas

stakeholder-maplisted

Maps stakeholders onto an influence/interest grid, captures each one's stance, motivations, and decision power, and derives a per-person engagement plan with a RACI overlay. Use when you say "who do I need to get on board," "map my stakeholders," "build a power/interest grid," "figure out who's blocking this," "who decides vs. who's just informed," or "I keep getting surprised by the same exec."
Sidsaladi9/persona-os · ★ 0 · AI & Automation · score 78
Install: claude install-skill Sidsaladi9/persona-os
# Stakeholder Map A stakeholder map built on the influence/interest (power/interest) grid plus a RACI overlay: place each person by how much power they hold and how much they care, mark their current stance, then assign decision roles so you know exactly who to win, who to manage, and who to keep warm. **Grounded in:** *Mendelow's power-interest grid* — Aubrey Mendelow: map influence × interest and tailor engagement per quadrant. **Go deeper (The Product Channel):** [9 Ways to Influence Without Authority](https://sidsaladi.substack.com/p/week-12-9-ways-to-influence-people) ## When to use this - Kicking off an initiative that needs sign-off or resources from people outside your direct team. - A decision keeps stalling and you can't tell who actually has veto power. - You're repeatedly blindsided by an exec or function that "should have been looped in." - A launch, migration, or reorg touches multiple teams with conflicting incentives. - You're new to a role or org and need to map the political terrain before you push anything. ## Before you start (gather these) - **The initiative**: one sentence on what you're trying to ship, change, or get approved. - **The decision at stake**: what specifically needs a yes (budget, headcount, scope, go/no-go). - **The cast**: names + roles of everyone who could approve, block, influence, or be affected. - **What you know per person**: their stance (supporter → blocker), what they care about, their formal power over this decision. If you