Presentation Tips for Risk Managers: Uncertainty in Numbers
By Daniel Harper · Career & Business
How should a risk manager present risks to leadership? Present a short list of the risks that matter, each with its likely impact in money or customers, its likelihood as a number or a range, and what is being done. Express uncertainty in numbers rather than vague words: numeric uncertainty costs little trust, while "medium likelihood" means something different to everyone in the room.
Risk managers present things that have not happened, may never happen, and are uncertain by definition, to leaders who have to make decisions now with limited time. The temptation is either to overstate risks to get attention or to hide uncertainty behind colours and labels. Both make the presentation less useful.
Words mean different things to different people
Most risk registers describe likelihood and impact in words: low, medium, high, unlikely, possible, almost certain. They are quick to read, and they hide disagreement. "Possible" might mean a one-in-ten chance to the risk owner and a one-in-two chance to the finance director. A room can agree a risk is "medium" while meaning quite different things.
Numbers, or ranges, solve that, and they cost less trust than people fear. In five experiments with nearly 5,800 people, including one on the BBC News website, van der Bles and colleagues found that communicating uncertainty about facts and numbers lowered trust only slightly, and mainly when the uncertainty was expressed in words rather than numbers.1
So where you can, put a number on it: "We estimate roughly a one-in-five chance of this in the next year, with a loss between $2 million and $5 million if it happens." Say how you got there. A rough, explained estimate is more useful than a precise-looking label.
Show only the risks that matter
A board shown a register of sixty risks cannot act on any of them. Present the five to ten that matter most at this level, each with:
- What could happen, in business terms.
- Likelihood, as a number or range.
- Impact, in money, customers, regulation or reputation.
- What is being done, and how far along it is.
- Whether the remaining risk is within appetite, and if not, what decision is needed.
Show movement, not just the snapshot
Risks change. Show which have grown, which have shrunk and why, since the last presentation. A risk that has quietly grown for three quarters is exactly what a board needs to see, and a static register hides it.
Make the biggest risk concrete
For the top risk, walk through a concrete scenario: what would happen in the first day, the first week, the first month. Concrete scenarios make abstract risks feel real enough to fund, in a way that a heat map does not.
When a risk materialises
When something on the register happens, present it promptly: what happened, its effect, how the response is going, and what it teaches about the register itself. Avoid the temptation to point out that it was on the list; the board will remember.
The hardest question
The question risk managers dread is "So what should we do?", asked after a carefully balanced presentation that recommended nothing. Always arrive with a recommendation for each risk that needs a decision: accept it, reduce it, transfer it, or stop the activity. Leaders can disagree with a recommendation; they cannot act on a list.
Presenting to the business
Risk presentations to business teams work best as conversations: ask them what keeps them up at night, show them how their risks connect to the company's, and agree what they will do. A risk framework the business helped shape is one it will use.
For the interview questions on this work, see behavioral interview questions for risk managers, and for presenting uncertain dates and estimates in another setting, presentation tips for software development managers.
References
- van der Bles, A. M., van der Linden, S., Freeman, A. L. J., & Spiegelhalter, D. J. (2020). The effects of communicating uncertainty on public trust in facts and numbers. Proceedings of the National Academy of Sciences, 117(14), 7672–7683. https://doi.org/10.1073/pnas.1913678117