Nov 17, 2017 8:51 AM
Replying to Wade Harshman
...
I like to put this in my risk register. It serves to remind the team of the need to break knowledge silos, and it helps explain any delays the project might have if a team member drives off a cliff.
But what to do after it happens? You'll need your team's input. Maybe someone can gather the project work and documentation and pick up where that person left off. If it's a specialized field, you might need a new team member, potentially even a hire hire. That could cause serious delays to your project, but those are risks your organization has to accept when they hire specialized positions.