Most projects have a risk register. It is created in the kickoff, contains forty lines, and is opened again when one of the risks has already happened.
A register is useful only when it changes what the team does this week.
Cause, event, effect
Write every risk as one sentence with three parts:
“Because the drive supplier has a backlog, the drive units may arrive four weeks late, so the build starts late and the end date moves.”
The cause shows where to act. The event is what may happen. The effect shows why it matters. A line like “supplier risk” contains none of this and leads to no action.
An issue is different: it is a risk that has already happened. Issues go into the action list with an owner and a date, not into the register.
Score with one scale
Probability and impact each get a score from 1 to 5, and the product is the risk score. The scale must be defined, otherwise every person scores differently:
| Score | Probability | Impact |
|---|---|---|
| 1 | below 10 percent | less than a week or EUR 10,000 |
| 2 | 10 to 30 percent | one to two weeks or up to EUR 50,000 |
| 3 | 30 to 50 percent | a milestone moves, the end date holds |
| 4 | 50 to 70 percent | the end date moves up to four weeks |
| 5 | above 70 percent | more than four weeks, or customer or safety affected |
A score of 12 or more is high. In the assembly cell example, the late drive units score 3 × 5 = 15, interface changes after week 12 score 4 × 3 = 12.
Four responses
- Avoid: change the plan so the risk cannot occur, for example a proven drive type instead of a new one.
- Reduce: lower probability or impact, for example a prototype test of the gripper in week 12.
- Transfer: move the impact to a party better able to carry it, for example a penalty clause with the supplier.
- Accept: live with it, with contingency and a trigger that tells you when to act.
Every response has an owner and a date. A response without an owner is a hope.
The weekly five
Each week the core team looks at the five highest scores only. Three questions per risk: what changed, is the response working, is a new one needed? This takes ten minutes.
The full register is reviewed at every gate. New risks come from the weekly meeting, from the design reviews and from the people closest to the work, who usually see them first.
A short register that drives five actions a week is worth more than a complete one that nobody reads.