See what each risk leads to before it happens
List the risks to a project, follow each one through its consequences, and plan how to prevent, spot and respond to the ones that matter.
Start from a template
A risk assessment template you can clone. Describe your launch in the root and work through each risk category in its own branch.
How it works
Describe the project, its timeline and what failure would cost. Each risk gets its own branch, and what it leads to sits underneath it.
-
List risks by category. Ask for the risks to your project grouped by category, such as regulatory, operational, market, financial and technical. Add a branch per category.
-
Follow the consequences. Under a risk, ask “What happens if this goes wrong?” and ask again under the answer. A supply delay leads to late orders, then lost customers, then a revenue shortfall, each one a level deeper.
-
Check how risks combine. A branch only sees the nodes above it. To ask how two risks make each other worse, ask under the category overview, where the model can see both, or ask Milo, the assistant built into the map, which reads the whole map. Milo is on the Promptmaps and Lifetime plans.
-
Plan the response. Under each risk you decide to act on, ask how to prevent it, how to spot it early and what to do if it happens. Add a note with the owner and the trigger that starts the response.
Following a risk past the first step
A risk register gives each risk one line and a red, yellow or green rating. “Regulatory risk” on one line is easy to skip in a review. Followed three levels down, it reads as a fine, a suspended service and three lost European deals.
Example
Say you run a hardware startup about to place your first production order. Under supply chain, a branch on a part with only one supplier leads to a six-week lead time for an alternative, then a three-month delay, then a missed holiday season. With the chain in front of you, you qualify a second supplier before you place the order.