Risk Registers as a Tool, Not a Tax
Most risk registers are a tax, not a tool. Two changes — write the trigger before the risk, write the mitigation owner in the same line — flip the register into something teams actually use.
Most risk registers are a tax, not a tool
The risk register is the single most over-built and under-used artefact in project management. Teams spend a quarter populating it, then update it on a quarterly review cadence that's slower than the project's actual risk surface. The result is a binder of dead risks and a project surprised by the risk that wasn't on the list.
Two changes flip the register from tax to tool. First, write the trigger before the risk — the observable signal that says "this is happening now." A risk without a trigger isn't a risk; it's a worry. Second, write the mitigation owner in the same line; an unowned mitigation isn't a plan, it's a wish.
| Field | Bad register | Tool register |
|---|---|---|
| Description | Vendor delay | Vendor X delivers > 2 weeks late on milestone M3 |
| Trigger | — | Weekly status from vendor X reports < 60% complete by Apr 12 |
| Owner | Project manager | Sasha (PM, escalation: Maria, VP Eng) |
| Mitigation | Monitor weekly | Pre-negotiated alternate vendor Y queued; redirect on trigger |
| Last reviewed | Quarterly | Weekly during execution; daily during M3 |