stakeholder-maplisted
Install: claude install-skill teodstr/workbench
# Stakeholder map
Projects rarely fail because of a missing task; they fail because someone important learned about them too late. This skill lists the people around the project, ranks them, and plans who hears what, when.
## When to use
- After `project-charter`, as soon as more than two people are involved.
- Before a change that will surprise someone: a reorganization, works in a shared building, a new tool for a team.
- Not to split the work itself: use `responsibility-matrix`.
## Inputs
1. The project charter, or the project in a few sentences.
2. Everyone the person running the project can think of who is affected, who decides, who pays, who can delay or block.
## Method
1. **List the stakeholders widely**, then group them: decision makers, people doing the work, people affected, people with a veto (authorities, landlords, legal, unions, co-owners), people who simply need to know.
2. **Place them on an influence and interest grid**: manage closely (high influence, high interest), keep satisfied (high influence, low interest), keep informed (low influence, high interest), monitor (low, low).
3. **For each key stakeholder**, write what they need, what they fear, what they could do if surprised, and their current position (supports, neutral, against).
4. **Plan the communication**: message, channel, frequency and messenger for each group. Bad news travels best early and in person.
5. **Prepare the hard conversations**: the two or three people likely to object, with