Build a delivery risk register with accountable owners

A risk register should change behavior. A list of generic concerns without triggers or owners becomes stale reporting and gives no one authority to act.

Build the decision artifact

Write each risk as a condition and consequence. Score likelihood and impact using defined scales, then record preventive control, contingency, early trigger, accountable owner and review date. Track dependency risks separately from current issues. Re-rank after controls rather than assuming a mitigation removed the risk.

The commercial leadership lab makes the artifact inspectable with authored inputs:

from leadership_cases import risk_register_case

result = risk_register_case()
assert result["scores"] == [20, 15, 8]
assert result["unowned"] == []
assert result["risks"][0]["owner"] == "data owner"
assert result["fictional"] is True

The fictional register ranks permission delay at 20, slice regression at 15 and support overload at 8. Every row has an owner and observable trigger. The scores establish review order; they are not universal probabilities.

Protect the decision from weak evidence

Do not make the FDE owner of risks controlled by a client data owner, security team or sponsor. Escalate ownership gaps. High scores deserve decisions and tests, while low-likelihood catastrophic risks can still require hard controls.

Keep these artifacts for review:

• defined scoring scale
• condition/consequence risk statements
• control, contingency, trigger and owner
• review history and residual score

This practice aligns with the discovery, productisation, client enablement, technical leadership and capstone sequence in the FDE for Professionals course. The course link describes the pathway; the local scenario is fictional and does not claim a client engagement, investment result, hiring decision or certificate.

Practice task

Write five risks for one integration. Replace every phrase like data issue or model risk with an observable condition and consequence.

Continue learning

This article is part of the Commercial judgement and delivery leadership sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Explain a failed pilot without hiding the original assumptions.
• Continue with Create an executive demo around a business decision.

Reference: GOV.UK agile governance principles.