Try this exercise with your team to identify, overcome and avoid potential project “gotchas”:
Get the team to write a project obituary — ask them to imagine the project is nearly over and has failed, and their job for the next 45 minutes is to describe all the things that went wrong contributing to its eventual demise. Often times, people who are difficult to engage in “regular vision” exercises relish the opportunity to list all the things that could go wrong. Perhaps given a slightly pessimistic slant on life, they can generate an exhaustive list of possible — albeit gloomy — outcomes for the project. These might include communication failures that lead to mismatched expectations, vendor delays, team morale issues… anything that could negatively impact the project.
Run the session as you would a brainstorming session with someone in a facilitator role recording the ailments on a white board (or via sticky pad notes) and prompting submitters for more detail to clarify understanding where required. If you used sticky notes, group related problems under broad categories. Review the lists with the group and then ask people to quietly think through potential solutions to these problems and take a break for 15 minutes.
Then after the break, solicit solutions (vaccines) to each of the problems (ailments) from the team.
The only thing I’d add to this is the encouragement to do so regularly throughout the project lifecycle. It’s not called Continuous Risk Management for nothing.
Latest posts by Martin Burns (see all)
- Colocated Teams, Distributed Organisations - January 20, 2018
- Christmas Reading: 6 Books That Will Change Your Thinking - December 22, 2017
- Now Is Not The Time for #NoProjects - December 14, 2017