You've asked the team "what are you worried about?" (Level 1)

You've refined those worries into clear risk statements (Level 2).

Now you're staring at 50+ risks on your list. They can't all be equally important.

Welcome to Level 3: Consequences.

How Bad Is It If This Risk Happens?

A Risk consequence is: "How bad of a day is it, if this risk happens?"

Consequences of risks are a first filter to triage whether you should spend much more time worrying about the risk.

"Customer needs replacement stock part" is on the opposite end from "Failed launch ends the company."

NASA's Simple Scale (1-5)

There's no need to get fancy here - NASA uses a simple scale from 1 to 5:

  • 1️⃣ Insignificant – Easy recovery
  • 2️⃣ Minor – Noticeable, needs resources
  • 3️⃣ Moderate – Significant setback
  • 4️⃣ Major – Threatens core goals/timeline
  • 5️⃣ Catastrophic – Project/company ending

Or Simplify to Three Options

You could even reduce it to three options, for a very quick assessment:

  • 🟢 LOW (Insignificant/Minor) – Recoverable with minimal disruption
  • 🟡 MEDIUM (Moderate) – Significant setback, real effort needed
  • 🔴 HIGH (Major/Catastrophic) – Threatens mission success or survival

The Process

Usually it works best to get the ideas written down first, and then go through the list again to rank them by Consequence. Then sort the list and see if it the ordering makes sense to you. These rankings help you and the team put real concerns "on the board."

The Biggest Challenge

The biggest challenge? Everyone has a different standard.

One engineer's "catastrophic" is another's "moderate." Without consistency, your consequence rankings obscure what actually matters.

RiskThing's secure AI agents (built for compliance-conscious teams) help your team consistently rank consequences using your chosen standard—NASA's 5-point scale, your company's custom rubric, or project-specific criteria.