THK-08 Core

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.

coating BThinking and decisions3 indicators6 levels
Target level · manager4 out of 4
ClusterThinking, analysis and decisions

Definition

BT360 v2.0.0

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.

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.LabelDescriptor
0AbsentDoes not see risks; operates on 'it will work out somehow'; thinks about consequences afterwards; recurring incidents do not change behavior.
1Poorly developedNames obvious risks; assesses them qualitatively and optimistically; takes measures after an incident; under pressure drops the safety net.
2UnderdevelopedSees the main risks in a familiar area; confuses probability with severity; makes a list but not an action plan; rarely revisits the assessment.
3Normally developedIdentifies risks by category; assesses probability, impact and reversibility; assigns an owner and measures; revisits the assessment as the context changes.
4Highly developed leader's goalSees systemic and low-probability risks; uses scenarios and early signals; builds layered protection; takes a calculated risk for an opportunity; teaches the team.
5OverdevelopedRisk management turns into risk paranoia: every action needs one more approval; opportunities are missed; manages fear rather than risk; the organization loses speed.

Development Actions

5 CATEGORIES
Diagnostics

LFR-25 (rationality, risk readiness) and MDMQ; a case with a risk assessment and a mitigation plan.

Training

Workshop 'Risk Assessment Without Paranoia': register, probability/impact matrix, early signals, triggers.

Practice

Build a risk register for your project with owners and triggers; revisit it every two weeks.

Feedback

Run a pre-mortem with the team: 'the project failed — why?'; account for blind spots.

Wednesday

Add a mandatory 'risks and early signals' block to project reviews without turning it into bureaucracy.

What to watch

INTERVIEW AND BEHAVIOR
Question 1Tell us about a risk that you underestimated. How did you understand this and what did you change?
Question 2How do you decide which risks are worth it and which are not?
ObservationIn the case: a list of risks, the distinction between probability and impact, specific measures, readiness to take justified risks.
Sign of hypertrophyRisk paranoia and missed opportunities.