Risk Management

This involves identifying potential problems, technical hurdles, or delays that could impact the work. It also includes preparing alternative plans and responses to address these issues if they actually occur.

RAID Log (Risks, Assumptions, Issues, Dependencies)

This involves maintaining a centralised, live tracking document that captures four critical variables influencing a project’s success or failure. By categorising factors into future threats (Risks), foundational presuppositions (Assumptions), current roadblocks (Issues), and critical external links (Dependencies), this framework provides a comprehensive health record for the project. It ensures that the team proactively monitors vulnerabilities, assigns clear ownership for mitigation, and maintains cross-functional alignment on factors outside their direct control.

Risk Register/Log

This involves maintaining a structured, living repository that documents all identified vulnerabilities, technical hurdles, and potential disruptions that could impact a project’s timeline, budget, or quality. Each entry includes a description of the threat, its root cause, and a quantitative or qualitative assessment of its probability and impact. This framework ensures that potential problems are systematically logged, assigned to specific owners, paired with proactive mitigation or contingency plans, and regularly reviewed to keep the project resilient against uncertainty.

Risk Statements

This involves using a standardised, cause-and-effect linguistic framework to clearly define and communicate potential project disruptions. Typically structured using an “If [Event] occurs, then [Consequence], resulting in [Impact]” format, this approach removes ambiguity from risk descriptions by explicitly linking a specific vulnerability to its operational fallout. This framework enables team members and stakeholders to objectively evaluate the severity of a threat, separating vague anxieties from concrete risks to drive precise mitigation planning.

Risk Matrix

This involves using a two-dimensional grid to visually evaluate and prioritise project risks based on two primary variables: the likelihood of the event occurring and the operational impact if it does. By intersecting these two values, the matrix maps individual threats into defined priority zones—typically low, medium, and high risk. This framework provides teams with an immediate, scannable prioritisation mechanism, ensuring that leadership focus and mitigation resources are automatically directed toward the most critical threats first.

Mind-mapping risks

This involves using a non-linear, visual brainstorming framework to uncover, explore, and connect potential project threats and vulnerabilities. Starting with the core project or objective at the center, team members branch out into major risk categories—such as technical, financial, operational, or legal—and continue radiating outward into increasingly granular root causes and sub-risks. This associative framework helps teams break out of linear thinking, map complex interdependencies between different risk factors, and identify hidden single points of failure that standard sequential lists might miss.

SWOT (Strengths, Weaknesses, Opportunities, Threats) risk analysis

This involves adapting a classic strategic planning framework to identify and evaluate project risks from both internal and external perspectives. By assessing internal capabilities (Strengths and Weaknesses) alongside external market or environmental dynamics (Opportunities and Threats), this approach uncovers vulnerabilities that standard risk logs might miss. This framework helps teams leverage their existing organizational advantages to mitigate potential downsides, while turning external uncertainties into actionable advantages.

Bow-tie risk analysis

This involves using a structured, visual diagram to analyze a single major risk event by mapping out its entire path from cause to consequence. The approach places the central hazard in the middle, branching out to the left to show potential root causes and the preventive steps designed to stop it, and to the right to map out the potential fallout alongside recovery plans designed to minimise damage. This framework provides teams with a clear, dual-focused view, ensuring they have robust defences to both prevent a crisis and effectively handle its aftermath if it does occur.

Risk Mitigation/Contingency Plan

This involves creating a structured blueprint that outlines specific, actionable steps the team will take to reduce the likelihood and impact of known project threats. Instead of just identifying problems, this document assigns clear ownership for each risk, defines early warning triggers, and outlines pre-planned backup strategies to deploy if a crisis hits. By deciding exactly how to respond before an issue actually occurs, the team removes panic and guesswork from the equation. It serves as a vital playbook that keeps the project on track and resilient when unexpected challenges arise.

Project Pre-Mortem

This strategy involves gathering the team before a project launches and asking everyone to pretend that the work has already completely failed. Working backward from this imaginary disaster, team members brainstorm every possible reason things went wrong, from missed deadlines to technical glitches. By actively hunting for weaknesses while you still have time to change course, you bypass the usual optimism that can hide early warnings. It serves as a powerful exercise for identifying hidden risks and building defences into your plan from day one.