During the evolution of a project, people come and go on the project team. This is an unavoidable aspect of successful project completion. So what is the best way to handle this seemingly open-door policy? In a post for PM Hut, Kiron D. Bondale elaborates on what to do when a person leave the project team.
When the project initially starts, the core team is developed, but as the project gains momentum more people are added to the team in order to create the best end results. After the project is completed, these add-ons inevitably leave to work on other priorities. Bondale suggests three things that should be done when these team members make their departure:
- Recognize them in a public forum.
- Ask them for feedback.
- Encourage knowledge transfer.
Although a good manager will likely have acknowledged accomplishments along the way, before a person officially leaves the team they should be recognized and thanked publicly for their specific contributions. This not only allows for the person to leave on a positive note, but it encourages the rest of the team to accomplish more. A small token of appreciation, like a gift card, goes a long way.
Before a person officially leaves, ask them for their feedback on their overall experience. Feedback may prove more useful during the course of the project because then action can be taken immediately, but end feedback is valuable too. This information can help to improve the entire team’s experience.
Do not wait until the person is actually gone before you accrue their knowledge. Have a plan in place to make this transition easier, while ensuring that their valuable knowledge is not lost forever. The closing phase of a project will likely address this.
You can read the original post here: http://www.pmhut.com/three-things-you-should-do-whenever-someone-leaves-your-project