Business
Project Risk Generator
Used by developers, writers, and creators worldwide.
A project risk generator hands you the common risks that derail projects, so you can name them in planning before they become fires. Choose how many you want and it returns a shuffled set — scope creep, key-person dependency, a dependency team that slips, underestimated complexity, testing time squeezed at the end. Project managers and teams use it to run a pre-mortem, build a risk register, or stress-test a plan by asking what could go wrong while there is still time to act. Each risk is a recognisable failure mode rather than a vague worry. Pick the ones relevant to your project, rate each by likelihood and impact, and decide a mitigation or owner for the serious ones. Naming a risk out loud is most of the battle: the dangers that sink projects are usually the ones no one wanted to mention until it was too late.
Read the complete guide — 4 min read
Loading usage…
Free forever — no account required
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 use a risk list
Pick the relevant ones, rate each by likelihood and impact, and assign a mitigation or owner to the serious ones. Naming the risk is most of the battle.
what is a pre-mortem
Imagine the project has failed and ask why. Listing the ways it could go wrong while there is still time to act surfaces risks a normal plan tends to gloss over.
which risks matter most
Focus on high-likelihood, high-impact ones, and watch for the quiet killers — scope creep and key-person dependency — that teams often avoid mentioning until too late.
You might also like
Popular tools from other categories that share themes with this one.