Risk Block
Document individual architectural risks with impact, likelihood, mitigation strategies, and ownership. Track risks through their lifecycle from identification to resolution.
Risks are potential events that could negatively impact the system or project. The Risk block captures individual risks with structured fields for impact assessment, mitigation planning, and ownership tracking. Risks are visualised with a colour-coded header based on their severity.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Title | Yes | Short name for the risk |
| Description | Yes | Detailed explanation of the risk and its context |
| Impact | Yes | Severity if the risk occurs: Low, Medium, or High |
| Likelihood | Yes | Probability of occurrence: Low, Medium, or High |
| Category | No | Type of risk: architectural, operational, security, performance, compliance, or delivery |
| Status | No | Current state: identified, mitigated, accepted, monitored, or retired |
| Response Type | No | Strategy: mitigate, accept, avoid, or transfer |
| Mitigation | No | Strategy to reduce or eliminate the risk |
| Residual Risk | No | Risk remaining after mitigation measures |
| Detection Signals | No | How to detect if the risk materialises (array of signals) |
| Owner | No | Who is responsible for managing this risk |
| Review Date | No | When to re-evaluate the risk |
| Notes | No | Additional context or observations |
Impact and Likelihood Values
Category Values
Response Type Values
Example: High-Impact Architectural Risk
A significant architectural risk that requires active mitigation.
Example: Security Risk
A security risk with transfer response strategy.
Example: Accepted Risk
A risk that has been consciously accepted with documented reasoning.
Example: Delivery Risk
A project delivery risk that could affect timelines.