Skip to content

6 min read

American Corners

Impact × likelihood in practice

From a worried list to a plan

It is easy to end up with a long list of things that could go wrong and no idea where to start. Everything feels a little urgent, so nothing gets fixed. The point of measuring risk is to break that stall: to turn a vague pile of worries into an ordered plan.

The tool for that is the small formula introduced in Threats, vulnerabilities and risk:

Priority = Impact × Likelihood

As a reminder, impact is how bad it would be if the thing happened and likelihood is how probable it is. Multiplying them puts very different problems onto one comparable scale. This lesson is about actually using that score to decide what to fix first.

Score it simply

You do not need precise numbers. A rough scale of 1 to 5 for each is plenty:

  • Impact 1 is a minor annoyance; impact 5 would be a serious loss (money, data, safety, reputation).
  • Likelihood 1 is very unlikely; likelihood 5 is almost expected.

Multiply the two and you get a priority score between 1 and 25. The exact figure is not the goal. The ranking it produces is.

A worked example

Take a short, everyday list, the kind of thing anyone might jot down about their own digital life:

ConcernImpactLikelihoodPriority
Main email has no multi-factor authentication (MFA) and a reused password5420
No backup of family photos on the laptop5315
Phone software several updates behind3412
Weak PIN on a rarely used loyalty app133

Now the list sorts itself. The unprotected main email scores highest, because losing it is severe and, with a reused password and no MFA, it is very much exposed. That is where you start. The missing backup is next: just as painful if it happens, but a little less likely on any given day. The outdated phone follows, and the weak PIN on a throwaway app sits at the bottom, worth doing eventually but not first.

Using the ranking

The value of the formula is that it settles arguments with yourself. Instead of fixing whatever you noticed last, or whatever feels scariest in the moment, you work down from the highest score.

Two habits make it work in practice:

  • Deal with the top item before the rest. A high score means high impact and high likelihood together, which is exactly what you want to remove first.
  • Do not chase the bottom of the list while the top is unaddressed. A rare, low-impact problem can wait; a likely, costly one cannot.

The same method scales from a personal list to a whole organisation's. The numbers get more detailed, but the move is identical: score by impact times likelihood, then fix from the top down.

Try it yourself

Place each scenario on the grid and watch its priority appear as Impact × Likelihood; the highest scores rise to the top, exactly as they should on your real list.

Risk matrix

Priority = Impact × Likelihood

Drag each scenario onto the grid, or Tab to a chip, press Enter to pick it up, move with the arrow keys and Enter to drop.

Impact
High
Med
Low
Low
Med
High
Likelihood

Scenarios to place

Priority ranking

  1. Place a scenario to see its priority.

Where this lesson comes from

Built from

  • Workshop 1: Cybersecurity Essentials (participant guide V3.0): prioritising risk

alphaPlan courses are built from taught programmes rather than invented for the web. Where a claim rests on an outside standard or a reported case, it is named above so you can check it rather than take our word for it.

shënim: ky material u krijua në kuadër të projektit 'U.S. Cybersecurity Leadership in AI for Albania', financuar nga departamenti i shtetit i shteteve të bashkuara. mendimet, gjetjet dhe përfundimet e paraqitura këtu janë të autorit(ëve) dhe nuk pasqyrojnë domosdoshmërisht ato të departamentit të shtetit të shteteve të bashkuara.

Disclaimer: This material was created on behalf of the 'U.S. Cybersecurity Leadership in AI for Albania' project, funded by the United States Department of State. The opinions, findings, and conclusions stated herein are those of the author(s) and do not necessarily reflect those of the United States Department of State.

Disclaimer

Found something unclear, outdated or improvable? Suggest an improvement