Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Not really, it is a team effort and you should distribute it to the concerned who are responsible for managing stakeholders but you have to be cautious about how you share it and whom to share it with as it contains sensitive information. Saving Changes...
Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
You can create two versions - one for your eyes only, and one for public consumption. My private version might contain notes such as "Stakeholder A is insecure, incompetent and vindictive". This helps me plan how to work around that stakeholder to get the results I want. For example, I'd take pains to avoid pointing out this particular stakeholder's mistakes in a public setting, as doing so could cause me considerable headaches. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Typically stakeholder analysis is not a project deliverable and is done in order for the PM/BA to better navigate issues around communication and risk management. It is not something I have ever shared outside the project team and even then not to all team members. Erics two version approach is something I've used before but it does add a bit of extra work since they need to be kept in synch. I have also seen somebody share the wrong version by mistake. Not good so be careful. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
You have to share it with everyone. But sometimes the organizational culture do not allow that. For example, and depending the type of clasification you use, if you will publish that some stkaholder that could be interested in the initiative (perhpas as a assumption because its position in the organizational pyramid) is not then it could be taken in the incorrect way. Is a matter of culture and organizational maturity. Remember: the stakeholder analysis data is taken from stakeholders performing elicitation activities. Is not what you think is what your stakehodlers said you. Saving Changes...
LORI WILSONRETIRED - Technical Project Manager| RETIRED - LifePoint HealthClarkston, Wa, United States
Hello Richard: I agree with Anton, I create a stakeholder analysis but I do not share it with others. I definitely share stakeholder information with others who need to know some of the information, but some of the information is just private for my use/understanding as project manager. Saving Changes...
You don't have to share a stakeholder analysis with anyone. It's your tool to evaluate the power, influence, and interest of your stakeholders. You use this information to create strategies for 1) engaging stakeholders, 2) using them to generate support for the project, and 3) improving their interest in/support for the project. Some of these activities will go into the communication plan and/or project schedule; share these documents. Feel free to share your stakeholder register (name, contact info, role or relevance on the project...). Be careful about whom you share your stakeholder analysis with. Their power and influence could come back to haunt you. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
As Anton points out, stakeholder analysis is a process, not a deliverable. While there may be a lot of different feedback and comments gathered, I only share the results: the stakeholder registry.
By default, conversations should be confidential. That's the only way you can build the trust necessary to get openess and transparency from your stakeholders. Saving Changes...
Community Champion
