I love George Mack's framing: "kill your todo list, play video games instead" (read his full essay here—it's point 9 of his brilliant piece on agency).
Applied to Risk Intelligence, the first 5 levels of the game look like this:
- Risk ideas (what are you most worried about?)
- Risk Titles & Descriptions
- Consequences
- Likelihood
- Severity
Yesterday, I discussed asking "what are you worried about right now?" to generate your first draft risk list.
But Charles Kettering's quote applies here: "A problem well-stated is a problem half-solved."
Where Most Risk Lists Fail
Level 2 is where most risk lists fail—vague titles and jargon-heavy descriptions that nobody reads, and fewer like to write.
Effective Risk Statements Have Two Parts
The Title (short enough for an email subject line)
- Captures the core risk clearly
- Avoids hedging like "could" or "may"
- Example: "Battery thermal runaway during Mars transit"
The Description (2-5 sentences)
- Explains what happens, why, and the primary impact
- Technical for engineers, clear for executives
- Describes the risk—not solutions
Bad: "There might be thermal concerns."
Good: "Lithium-ion batteries may exceed 60°C during peak solar exposure, triggering thermal runaway. Current design assumes 45°C max. Failure risks loss of primary power."
The Standard
There are various formats for writing risks—this is one proven approach.
The standard: Risk statements should be clear enough for anyone on your team to read and understand—from interns to board members.
Getting started is the hard part. RiskThing's secure AI assistants (built for compliance-conscious teams) help you iterate to achieve clear risk titles and descriptions—so you can move through the levels without getting stuck.