A stakeholder analysis map might be more of a structured way of working with collaboration, rather than a “method” by itself. A way to work can turn out in many ways.
However, the point is to keep track on the stakeholders that concerns you or your project. The output can of course be public to the project, steering group or whoever it concern. But likely the artifact should not be publicity visible outside the project core team.
The point is to get a quicker overview and understanding on what stakeholders have what kind of interest in the subject matter you work on. You can use it to
- Understanding of what key persons that surround your project
- Helps to keep a communication strategy
- Prioritize the right stakeholder based on what being communicated
- Keep less details in memory as a slight drift away can cause damage in communicate wrong thing in wrong context to wrong person.
This represent a table crowded by situation that might make sense to know about stakeholders.
Personally I do also suggest to have columns for when a relationship was started and when it was latest refreshed.
A basic mental model to work from<< Back to list all models