Risk assessment
The ability to see what can go wrong, estimate the probability and cost of consequences, and define mitigation measures in advance without turning caution into refusal to act.
Definition
BT360 v2.0.0The ability to see what can go wrong, estimate the probability and cost of consequences, and define mitigation measures in advance without turning caution into refusal to act.
What is it made up of?
3 INDICATORS- 01Identifying risks and their sources
- 02Estimating probability and cost of consequences
- 03Planning mitigation measures
Behavior levels 0–5
MANAGER'S GOAL - 4| Lv. | Label | Descriptor |
|---|---|---|
| 0 | Absent | Does not see risks; operates on 'it will work out somehow'; thinks about consequences afterwards; recurring incidents do not change behavior. |
| 1 | Poorly developed | Names obvious risks; assesses them qualitatively and optimistically; takes measures after an incident; under pressure drops the safety net. |
| 2 | Underdeveloped | Sees the main risks in a familiar area; confuses probability with severity; makes a list but not an action plan; rarely revisits the assessment. |
| 3 | Normally developed | Identifies risks by category; assesses probability, impact and reversibility; assigns an owner and measures; revisits the assessment as the context changes. |
| 4 | Highly developed leader's goal | Sees systemic and low-probability risks; uses scenarios and early signals; builds layered protection; takes a calculated risk for an opportunity; teaches the team. |
| 5 | Overdeveloped | Risk management turns into risk paranoia: every action needs one more approval; opportunities are missed; manages fear rather than risk; the organization loses speed. |
How is it measured?
coating BLFR-25 measures rationality and risk-taking, MDMQ measures vigilance in decisions. Tests show disposition, not the quality of a particular risk analysis.
Development Actions
5 CATEGORIESLFR-25 (rationality, risk readiness) and MDMQ; a case with a risk assessment and a mitigation plan.
Workshop 'Risk Assessment Without Paranoia': register, probability/impact matrix, early signals, triggers.
Build a risk register for your project with owners and triggers; revisit it every two weeks.
Run a pre-mortem with the team: 'the project failed — why?'; account for blind spots.
Add a mandatory 'risks and early signals' block to project reviews without turning it into bureaucracy.