A risk is something that could go wrong. It names a problem that hasn't happened yet, what it would hurt, and the condition that would bring it about.
For example, the progress bar is driving more new cardholders to redeem rewards. Finance notices that if adoption keeps growing faster than spending, the cost of redemptions could go over budget. That is a risk.
Why it matters
Teams tend to talk about risks in hallways and then move on. Nobody writes them down, so nobody owns them, and when the problem arrives it feels like a surprise even though someone saw it coming.
Writing risks down turns worry into something the team can manage. It says what could happen, how bad it would be, and what would cause it. That lets leaders decide which risks to accept, which to watch, and which call for a change of plan, and it sends the right questions back into research.
Name each risk plainly, judge its likelihood and impact, give it an owner, and decide what you'll do about it.
How we write one
Every risk is written as one sentence that names the risk, its impact and the condition that would cause it:
A risk could have an impact if a condition holds.
Redemption costs could exceed budget if adoption grows faster than spend.
Writing it this way makes the cause explicit, so the team knows what to watch and can tell quickly whether the risk is getting closer.
How it differs from similar ideas
-
A watch item tracks one metric against a threshold. A risk describes what could go wrong; it often gets a watch item to track it.
-
A constraint is a fixed limit that already applies. A risk is something that may or may not happen.
-
An assumption is something treated as true without checking. If an assumption turns out wrong, that can become a risk.
-
A business outcome is a change that already happened. A risk is a possible change that hasn't happened yet.
A good risk
-
Names a specific problem, not a general worry
-
Says what it would hurt
-
Names the condition that would cause it
-
Is judged for likelihood and impact
-
Has an owner
-
Has a response: accept, watch, reduce or avoid
What happens to it
-
Raised. Someone spots it in results, or attaches it to a concept, bet or decision.
-
Assessed. The owner judges its likelihood and impact.
-
Managed. A response is chosen: accept it, watch it, reduce it or avoid it.
-
Occurred or passed. The risk either happens and becomes an issue to act on, or the condition goes away.
-
Looped back. What was learned returns to Define and Collecting, so the next round of research accounts for it.
For Ray
This part tells Ray how to find a risk in an input, such as a results review, a finance forecast, a risk register, a legal review, a retro or a steering committee note, and how to store it.
How to find one
-
Mark statements about what could go wrong. Read the input and mark every statement about a possible problem, downside or exposure.
-
Find the risk. Pull out the specific problem in plain words.
-
Find the impact. Identify what it would hurt, such as budget, customers, brand or compliance.
-
Find the condition. Look for what would cause it. If none is given, leave it blank.
-
Find what it attaches to. Note the result, concept, bet or decision it relates to.
-
Judge the stakes. Score likelihood and impact using the scale below. If the source doesn't support a score, leave it blank.
-
Write the sentence. Use the format: [Risk] could [impact] if [condition].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Caution language: "the danger is", "we could end up", "I'm worried that", "if this keeps up"
-
Risk registers, legal reviews and finance forecasts
-
Results that beat or miss targets in a way that strains another part of the business
-
Conditional warnings: "if adoption outpaces spend, costs will..."
What doesn't count
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>If the statement...</p></th><th colspan="1" rowspan="1"><p>Store it as</p></th></tr><tr><td colspan="1" rowspan="1"><p>Sets a fixed limit that already applies</p></td><td colspan="1" rowspan="1"><p>Constraint</p></td></tr><tr><td colspan="1" rowspan="1"><p>Names a metric and a threshold to monitor</p></td><td colspan="1" rowspan="1"><p>Watch item, linked to the risk if one exists</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes something that already went wrong</p></td><td colspan="1" rowspan="1"><p>Business Outcome or Result, and raise a new risk only if it could recur</p></td></tr><tr><td colspan="1" rowspan="1"><p>Treats a belief as true without checking</p></td><td colspan="1" rowspan="1"><p>Assumption</p></td></tr><tr><td colspan="1" rowspan="1"><p>Is a general worry with no specific problem</p></td><td colspan="1" rowspan="1"><p>Leave it out, or store at low confidence for review</p></td></tr></tbody></table>
The record
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What to fill in</p></th><th colspan="1" rowspan="1"><p>Values</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>The one-sentence risk</p></td><td colspan="1" rowspan="1"><p>[Risk] could [impact] if [condition].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Risk</p></td><td colspan="1" rowspan="1"><p>The specific problem</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Impact</p></td><td colspan="1" rowspan="1"><p>What it would hurt</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Condition</p></td><td colspan="1" rowspan="1"><p>What would cause it</p></td><td colspan="1" rowspan="1"><p>Short text, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Attached to</p></td><td colspan="1" rowspan="1"><p>What it relates to</p></td><td colspan="1" rowspan="1"><p>Link to Result, Concept, Bet or Decision</p></td></tr><tr><td colspan="1" rowspan="1"><p>Likelihood</p></td><td colspan="1" rowspan="1"><p>How likely it is</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr><tr><td colspan="1" rowspan="1"><p>Impact level</p></td><td colspan="1" rowspan="1"><p>How bad it would be</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr><tr><td colspan="1" rowspan="1"><p>Response</p></td><td colspan="1" rowspan="1"><p>What the team will do</p></td><td colspan="1" rowspan="1"><p>Accept, Watch, Reduce, Avoid</p></td></tr><tr><td colspan="1" rowspan="1"><p>Owner</p></td><td colspan="1" rowspan="1"><p>The person responsible for it</p></td><td colspan="1" rowspan="1"><p>Name or role</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>The input and exact passage</p></td><td colspan="1" rowspan="1"><p>Link to Input</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Where it stands</p></td><td colspan="1" rowspan="1"><p>Raised, Assessed, Managed, Occurred, Passed</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How clearly it was stated</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
New risks start as Raised. A risk can't move to Managed until it has a response and an owner.
Scoring confidence
Confidence measures how clearly the risk was stated and grounded in evidence, not how serious it is. Seriousness is judged separately below.
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Level</p></th><th colspan="1" rowspan="1"><p>When to use it</p></th></tr><tr><td colspan="1" rowspan="1"><p>High</p></td><td colspan="1" rowspan="1"><p>Stated in writing with a specific problem, an impact and a condition, backed by data</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>The problem is clear, but the impact, condition or supporting data is missing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>A general worry or a passing remark with no specific problem or cause</p></td></tr></tbody></table>
If any part of the record can't be filled from the source, leave it blank and lower confidence by one level.
Judging the stakes
Ray scores each risk on likelihood and impact. The higher of the two sets the stakes, which decides how fast the risk reaches a leader.
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Level</p></th><th colspan="1" rowspan="1"><p>When to use it</p></th></tr><tr><td colspan="1" rowspan="1"><p>High</p></td><td colspan="1" rowspan="1"><p>Likely to happen soon, or would hurt a business goal, budget, customers or compliance in a serious way</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Could happen within the current timeframe, with a noticeable but recoverable impact</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Unlikely, or would have a small, contained impact</p></td></tr></tbody></table>
High-stakes risks always go to the review digest, whatever their confidence.
Linking
-
Check for duplicates first. If an existing risk names the same problem and condition, add the new source to it instead of creating another.
-
Link to the result that raised it, or to the concept, bet or decision it attaches to, and its source input.
-
Link to any watch item set up to track it, or prompt the owner to create one.
-
Link back to Define and Collecting, so the risk shapes the next round of inputs and assumptions.
-
Note conflicts. If a risk contradicts an active bet or business intent, link them as conflicting.
When to store and when to ask
-
Store automatically when confidence is high and stakes are low or medium.
-
Add to the review digest when confidence is medium or low, when stakes are high, when it has no owner, or when it threatens an active bet.
When to flag
-
A high-stakes risk has no owner or response
-
A risk's condition appears to be coming true
-
A bet is Live with a high-stakes risk attached and no watch item
-
A risk has stayed Raised for more than 30 days without being assessed
-
A risk has occurred
Worked example
Input: notes from the Q2 results review with Finance.
"Card spend is up 8.5%, which is short of the 10% target. Redemptions are growing faster than spend. If that continues, redemption costs will blow through the rewards budget by Q3. Finance lead to own this."
What Ray finds:
-
"Card spend is up 8.5%" is the result the risk is raised from.
-
"Redemption costs will blow through the rewards budget" is the risk and its impact.
-
"If redemptions keep growing faster than spend" is the condition.
-
The Finance lead is the owner, and the trend data supports high likelihood.
Stored record:
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>Redemption costs could exceed budget if adoption grows faster than spend.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Risk</p></td><td colspan="1" rowspan="1"><p>Redemption costs exceed the rewards budget</p></td></tr><tr><td colspan="1" rowspan="1"><p>Impact</p></td><td colspan="1" rowspan="1"><p>Rewards budget overrun by Q3</p></td></tr><tr><td colspan="1" rowspan="1"><p>Condition</p></td><td colspan="1" rowspan="1"><p>Redemptions keep growing faster than card spend</p></td></tr><tr><td colspan="1" rowspan="1"><p>Attached to</p></td><td colspan="1" rowspan="1"><p>Result: Grow sales: card spend rose 8.5% against a 10% target in Q2; Bet: progress bar</p></td></tr><tr><td colspan="1" rowspan="1"><p>Likelihood</p></td><td colspan="1" rowspan="1"><p>High</p></td></tr><tr><td colspan="1" rowspan="1"><p>Impact level</p></td><td colspan="1" rowspan="1"><p>Medium</p></td></tr><tr><td colspan="1" rowspan="1"><p>Response</p></td><td colspan="1" rowspan="1"><p>Blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Owner</p></td><td colspan="1" rowspan="1"><p>Finance lead</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Q2 results review notes</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Raised</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: specific problem, impact and condition, backed by trend data</p></td></tr></tbody></table>
Flag raised: high-stakes risk with no response, sent to the review digest with a prompt to the Finance lead to choose one and set a watch item on redemption costs.
Edge cases
-
Vague worry. "This could backfire" has no problem or cause. Store it at low confidence and ask the speaker what specifically could go wrong.
-
Risk already happened. If the budget is already over, record it as an outcome and mark the risk Occurred.
-
Several risks in one. "Costs could rise and Legal may object" is two risks. Split them, each with its own owner.
-
Stakes change. Don't overwrite the old score. Record the new likelihood or impact, the reason, and keep the old score in history.