What do professional skydivers and successful project managers have in common?
They both identify, assess, and plan for risks.
Skydivers look at the conditions, equipment, and capabilities before, during, and after they jump out of planes. Project managers look at the conditions, equipment, and capabilities before, during, and after projects.
Why do they do that?
How do they do that?
Well, I don’t know how skydivers do it, but to identify, assess, and plan for risks, a good project manager is never far away from a risk register.
But, when I discovered that 81% of organizations feel their risk registers are ineffective at identifying and planning for potential risks, and 30% of projects fail as a direct result, I felt the need to write this Process Street post about how to create one.
So, listen up as we go through the following:
- What is a risk register & what does one contain?
- Why projects won’t survive without a risk register
- The 3 biggest mistakes to avoid when creating a risk register
- How to use Process Street to create a risk register
If you’re in a hurry, grab this free Risk Register Process Checklist now, and catch up with the what, why, and how later.
Got your parachute? Ready, set… Geeeeronimoooooo…