Objective, horizon, and process are named.
Risk Matrix
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
Prerequisite
What needs to be finished first
Likelihood and impact have observable anchors.
Preparation
What needs to be ready before start
5×5 workspace, risk list, incident history, control evidence, scale anchors, and decision log.
Facilitator, risk owner, likelihood and impact experts, and a person authorised to accept or escalate risk.
Prepare scope, horizon, tolerance, current controls, and reference cases.
45–60 minutes for 8–12 risks; data collection and treatment work are additional.
Label axes 1–5 with concrete anchors and display the extreme-outcome and uncertainty rules.
Core question
The one question this method answers
Which risks exceed our tolerance in the agreed horizon, and which response reduces them credibly?
Flow
Phases with goal, actions, output and pitfall
A Risk Matrix supports comparison when scope, time horizon, and scale anchors are explicit. Ordinal scores are conversation aids rather than precise mathematics; rare catastrophic outcomes and uncertain estimates require separate attention.
Justified risk assessment
Fictional worked example
Connect each scenario to calibrated ratings, controls, and a decision; this is not a quantitative risk model.
| Risk | Risk scenario | Likelihood | Impact | Controls and residual risk | Response |
|---|---|---|---|---|---|
| Checkout loginIdentity-provider outage | If the identity provider is unavailable for more than 30 minutes, customers cannot sign in or purchase. | 3/5: about once per quarter in 12 months of status history. | 5/5: complete login and purchase stop, with revenue and support impact. | Manual fallback exists but is untested; residual risk 3×5=15. | Mitigate: Operations tests by 30 June; switch-over <5 minutes, no data loss; then reassess. |
1. Risk scenario
- Checkout login
- If the identity provider is unavailable for more than 30 minutes, customers cannot sign in or purchase.
2. Likelihood
- Checkout login
- 3/5: about once per quarter in 12 months of status history.
3. Impact
- Checkout login
- 5/5: complete login and purchase stop, with revenue and support impact.
4. Controls and residual risk
- Checkout login
- Manual fallback exists but is untested; residual risk 3×5=15.
5. Response
- Checkout login
- Mitigate: Operations tests by 30 June; switch-over <5 minutes, no data loss; then reassess.
The number is an ordinal sorting aid. Anchors, uncertainty, extreme outcomes, and residual risk remain decision-relevant.
- 1
Calibrate
Anchor scales and thresholds

Goal
Define a scope-specific 5×5 scale with observable anchors and escalation rules.
Inputs for this step
- Decision scope and time horizon
- Risk tolerance or escalation rules
- Historical incidents or reference cases
Actions
- Define each likelihood level as a range or defensible frequency.
- Anchor each impact level with examples for cost, users, operations, and compliance.
- Agree threshold, extreme-outcome rule, and treatment of high uncertainty.
Output
Calibrated scales
5 likelihood anchors · 5 impact anchors · thresholds · extreme-outcome rule
Quality check
Can two people place the same reference case within one level? Does a catastrophic risk remain visible even when likelihood is low?
Pitfall
The group assigns numbers without explaining the real frequency or consequence behind each level. Anchor every level with a range and reference case; mark uncertainty separately where data is missing.
Timing: 10–15 minutes
- 2
Describe
Write precise risk scenarios

Goal
Describe each risk as a possible event with cause, consequence, affected objective, and existing controls.
Inputs for this step
- Risk sources and assumptions
- Process, system, or market knowledge
- Existing controls
Actions
- Write the risk as 'If cause/event, then consequence'.
- Add affected objectives, consequence scope, and current controls.
- Record evidence, data gaps, and assessment date on the item.
Output
Assessable risk list
Event · cause · consequence · objective · control · evidence status
Quality check
Is each item an uncertain event rather than an issue that has already occurred? Is the assessed consequence explicit?
Pitfall
Entries such as 'security' or 'supplier' name a topic but no assessable event or consequence. Rewrite the entry as an if-then statement with an affected objective.
Timing: 10–15 minutes
- 3
Assess
Place inherent and residual risk

Goal
Assess likelihood and impact consistently while preserving disagreement and uncertainty.
Inputs for this step
- Calibrated scales
- Assessable scenarios
- Control effectiveness and case data
Actions
- Assess the risk before additional controls and record the rationale.
- Assess residual risk after existing effective controls separately.
- Capture divergent views as a range or open data question.
Output
Justified matrix
L · I · category · rationale · residual risk · uncertainty
Quality check
Can the cell be traced to scale anchors and evidence? Was the ordinal score kept separate from precise loss probability?
Pitfall
The team multiplies two ordinal numbers and treats the result as objective precision or the only ranking. Review anchors, rationale, uncertainty, and extreme outcomes next to the score; discuss ties substantively.
Timing: 15–20 minutes
- 4
Respond
Set response and monitoring

Goal
Agree a concrete treatment, owner, and review trigger for risks above tolerance.
Inputs for this step
- Justified matrix
- Risk tolerance
- Response options and responsibilities
Actions
- Choose and justify avoid, reduce, transfer, or accept.
- Set action, owner, date, leading indicator, and expected residual risk.
- Agree a review date or trigger for reassessment.
Output
Risk treatment plan
Response · action · owner · date · indicator · residual risk
Quality check
Does every high risk have a decision rather than only a colour? Is it clear when the assessment becomes stale?
Pitfall
The matrix ends with red cells but no decision, owner, indicator, or review date. Add a response and measurable review trigger for every risk above threshold.
Timing: 10–15 minutes
Artifact
What comes out at the end
Sketch: what the artifact looks like
Versioned matrix plus register containing rationale, response, owner, date, and residual risk.
Retain assessment date, scale version, and changed controls for each revision; do not overwrite prior positions.
- Whiteboard with 5×5 grid
- Risk register or spreadsheet
- Decision and action log
risk-matrix-working-template.md
Plan calibration, assessment, and treatment for a bounded risk set.
Risk Matrix: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Full risk review Time: 45–60 minutes
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: 5×5 workspace, risk list, incident history, control evidence, scale anchors, and decision log.
- Roles: Facilitator, risk owner, likelihood and impact experts, and a person authorised to accept or escalate risk.
- Advance information: Prepare scope, horizon, tolerance, current controls, and reference cases.
- Overall time needed: 45–60 minutes for 8–12 risks; data collection and treatment work are additional.
- Setup: Label axes 1–5 with concrete anchors and display the extreme-outcome and uncertainty rules.
Prepare for the work steps
Calibrate: Anchor scales and thresholds
- Decision scope and time horizon
- Risk tolerance or escalation rules
- Historical incidents or reference cases
Describe: Write precise risk scenarios
- Risk sources and assumptions
- Process, system, or market knowledge
- Existing controls
Assess: Place inherent and residual risk
- Calibrated scales
- Assessable scenarios
- Control effectiveness and case data
Respond: Set response and monitoring
- Justified matrix
- Risk tolerance
- Response options and responsibilities
Justified risk assessment
| Risk | If …, then … | L 1–5 + anchor | I 1–5 + anchor | Controls · residual risk | Response · owner · date |
|---|---|---|---|---|---|
| Checkout login |
- Checkout login: Identity-provider outage
For each risk, complete scenario, L/I anchors, controls, residual risk, and response.
Calibrate: Anchor scales and thresholds
Expected artifact: Calibrated scales
5 likelihood anchors · 5 impact anchors · thresholds · extreme-outcome rule
Entry:
...
- Can two people place the same reference case within one level?
- Does a catastrophic risk remain visible even when likelihood is low?
Describe: Write precise risk scenarios
Expected artifact: Assessable risk list
Event · cause · consequence · objective · control · evidence status
Entry:
...
- Is each item an uncertain event rather than an issue that has already occurred?
- Is the assessed consequence explicit?
Assess: Place inherent and residual risk
Expected artifact: Justified matrix
L · I · category · rationale · residual risk · uncertainty
Entry:
...
- Can the cell be traced to scale anchors and evidence?
- Was the ordinal score kept separate from precise loss probability?
Respond: Set response and monitoring
Expected artifact: Risk treatment plan
Response · action · owner · date · indicator · residual risk
Entry:
...
- Does every high risk have a decision rather than only a colour?
- Is it clear when the assessment becomes stale?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/risk-matrix/run-sheet
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
risk-matrix-beispiel.md
Concrete filled scenario, fictional example
Fictional example: checkout depends on an identity provider. Event: provider unavailable for more than 30 minutes. L=3 (about one outage per quarter from status history), I=5 (login and purchase stop, with revenue and support impact). Inherent score 15. The manual fallback is untested, so residual risk remains 15. Decision: mitigate; Operations tests the fallback by 30 June. Success means switch-over under five minutes with no data loss, followed by reassessment.
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Anchor scales and thresholdsThe group assigns numbers without explaining the real frequency or consequence behind each level.View in phase
- Write precise risk scenariosEntries such as 'security' or 'supplier' name a topic but no assessable event or consequence.View in phase
- Place inherent and residual riskThe team multiplies two ordinal numbers and treats the result as objective precision or the only ranking.View in phase
- Set response and monitoringThe matrix ends with red cells but no decision, owner, indicator, or review date.View in phase
Anchor scales and thresholds
The group assigns numbers without explaining the real frequency or consequence behind each level.
Anchor every level with a range and reference case; mark uncertainty separately where data is missing.
Write precise risk scenarios
Entries such as 'security' or 'supplier' name a topic but no assessable event or consequence.
Rewrite the entry as an if-then statement with an affected objective.
Place inherent and residual risk
The team multiplies two ordinal numbers and treats the result as objective precision or the only ranking.
Review anchors, rationale, uncertainty, and extreme outcomes next to the score; discuss ties substantively.
Set response and monitoring
The matrix ends with red cells but no decision, owner, indicator, or review date.
Add a response and measurable review trigger for every risk above threshold.
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

