One of my key stakeholders of my project has left the organization and replaced with another person. I have added the new stakeholder into my stakeholder register and completed the stakeholder insights. Can I remove the "already left" key stakeholder from the stakeholder register? Saving Changes...
So long as you don't lose the information related to that departed stakeholder, that should be fine. For example, if the register is captured in an Excel workbook, you could have a separate worksheet where you move departed stakeholders.
This will be important for enabling future use of the register (post-project) as a source of knowledge for other projects.
Kiron
...
2 replies by KLAO BELL-LEWIS and Rajesh Vasukuttan Nair
Nov 15, 2024 1:43 PM
Rajesh Vasukuttan Nair
...
Thanks Kiron for sharing your experience.. it helps
Nov 15, 2024 3:04 PM
KLAO BELL-LEWIS
...
Also...include a copy of the departure notice in your records. E.g, a non-confidential email sent to you and/or the group.
So long as you don't lose the information related to that departed stakeholder, that should be fine. For example, if the register is captured in an Excel workbook, you could have a separate worksheet where you move departed stakeholders.
This will be important for enabling future use of the register (post-project) as a source of knowledge for other projects.
Kiron
Thanks Kiron for sharing your experience.. it helps Saving Changes...
So long as you don't lose the information related to that departed stakeholder, that should be fine. For example, if the register is captured in an Excel workbook, you could have a separate worksheet where you move departed stakeholders.
This will be important for enabling future use of the register (post-project) as a source of knowledge for other projects.
Kiron
Also...include a copy of the departure notice in your records. E.g, a non-confidential email sent to you and/or the group. Saving Changes...
Depending on how you have things organized, I would normally just create a note in the register entry for the new stakeholder, e.g. "Replaced John Doe D/M/Y". Putting things in too many places can sometimes create more places for things to get lost, but different methods work for different situations. Saving Changes...
Product Operations Program ManagerBarcelona, Cataluña, Spain
Agree with previous comments. It can be done as simple as capturing the change in an additional field named e.g. "Comments" or "Notes", or in a separate sheet withing the same workbook, as pointed out by Rami Kaibni. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
If a stakeholder with a defined role in the project is replaced in this role by somebody else, he still is a stakeholder. He might even be beneficial if he retains his network and influence on others still on the project and may no longer be bound by loyalty or confidentiality. An update on stakeholder analysis is needed, though. Stakeholders are humans. I experienced it when my client hired my team members.
Consultant| Canarys Automation LtdBangalore, Karnataka, India
I am in agreement with the responses others have made.
While it’s fine to remove the former stakeholder from the register, ensure that any critical knowledge or context they provided has been documented or passed on to their replacement. This helps avoid gaps in understanding that could impact the project. Additionally, communicate the change to your project team and other stakeholders to keep everyone aligned.
Saving Changes...
Keith MelvinSumaria Systems, LLCDayton, OH, United States
Rajesh,
I have a column in my stakeholder register called "Used to be". Here we put the name of the person who "used to be" in that role when a new person comes on board. Saving Changes...
Community Champion
