Business
Project Risk Generator
The project risk generator draws from a pool of 14 recognisable failure modes and returns a shuffled subset. The single input — how many — controls batch size from 1 to 10. Risks cover scope creep, key-person dependency, unclear requirements, third-party reliability, stakeholder disagreement, testing time squeeze, budget loss, late compliance discovery, and poor handover. Project managers and teams use it to run a pre-mortem before work begins, build a risk register, or stress-test a plan while there is still time to act. Generate a set, filter for what is relevant to your project, rate each by likelihood and impact, and assign a mitigation owner to the serious ones. The risks that sink projects are usually the ones everyone saw but nobody wanted to name.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose how many risks you want.
- Generate a set relevant to your project.
- Rate each by likelihood and impact.
- Assign a mitigation or owner to the serious ones.
Use Cases
- •Running a project pre-mortem
- •Building a risk register
- •Stress-testing a project plan
- •Surfacing risks in a review
- •Preparing a status update honestly
Tips
- →Run it as a pre-mortem before you start.
- →Rate risks by likelihood and impact.
- →Give every serious risk an owner.
- →Name the quiet killers others avoid.
FAQ
How do I turn a generated risk list into a risk register?
Filter for the risks relevant to your project, then rate each by likelihood and impact on a simple two-axis scale. Assign a mitigation action and an owner to every high-rated risk, and review the register at each project checkpoint.
What is a pre-mortem and how does this tool help?
A pre-mortem imagines the project has already failed and asks why. Generate a batch of risks, read them aloud with the team, and identify which ones your current plan does not address. It surfaces problems while you still have time to act.
Which risks should I prioritise?
Focus on high-likelihood, high-impact ones first. Also watch for the quiet killers — scope creep and key-person dependency — that teams often avoid naming until they have already done damage.
Are these risks specific to software projects?
Most apply across project types — unclear requirements, budget loss, and stakeholder disagreement happen in any domain. A few (legacy system integration, testing time) skew toward technical projects, so filter those out when running a non-technical pre-mortem.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.