Build a Risk Statement That Can Be Tested
Convert a vague concern into a testable risk statement.
In the risk log, "AI compliance" has sat untouched for three weeks. It is too vague to assign, too broad to score, and too scary to ignore. The teach is the ISO 31000 logic in miniature: risk is uncertainty affecting objectives, so the statement must show the uncertainty and the objective. A testable statement lets the team gather evidence. It contains condition, trigger or event, consequence, objective, and horizon. The mechanism is compression without losing decision value. A risk statement should be short enough to read in a meeting but specific enough to tell you what evidence to collect. It…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in