Write a Project Risk Register
Added 2026-11-03
Every risk needs a trigger signal, an impact and an owner.
We just started a project (context below). Write a risk register: 1) list eight risks covering external, resources, technical, people and compliance; 2) rate likelihood and impact high, medium or low; 3) give each an early signal you could see in advance; 4) add a mitigation and an owner; 5) mark the three that must be handled this week. Avoid empty risks like "could cause delays".
Site original
Chinese original
How to use
风险登记表的作用是让「没想到」变成「看到了但没处理」。
Try tweaking it
- Have it state how the hypothesis could be falsified before discussing execution.
- Split the plan into a one-week testable experiment.
What you should get
- A small testable experiment with a failure threshold
- Costs, risks, and what needs outside confirmation
Common mistakes
- Asking for a "full business plan" and getting unverifiable optimistic assumptions.
- No failure threshold, so you never know whether to continue.
How to check the output
- There is a clear failure threshold, testable within a week.
- Costs, assumptions and risks are listed separately.
Where it works
- Good for: turning business assumptions into a small testable experiment with a failure threshold first.
- Watch out: for pricing, contracts and legal points, treat output as a draft needing professional review.