Organisational resilience is often associated with governance frameworks, policies, and documented controls.

These remain essential.

However, resilience is rarely determined by documentation alone.

In this RiskMasters: The Download, Frédéric Gielen explains why organisational resilience depends on organisational design, decision-making, and behaviours that continue to operate effectively under pressure.

Drawing on decades of experience advising regulators and financial institutions across Europe, he argues that resilience rarely disappears through a single failure. Instead, it gradually weakens through rational trade-offs that appear reasonable when viewed individually but collectively reduce organisational control.

The discussion also explores the difference between documented capability and operational capability. Many organisations develop comprehensive governance frameworks, recovery plans, and resilience documentation. Under stress, however, those same organisations often discover that decision-making, escalation, and accountability do not operate as expected.

Another key insight is that resilience should be viewed as a design choice rather than a technical exercise. Governance frameworks provide structure, but organisational resilience depends on transparency, redundancy, accountability, and the ability of the organisation to adapt when disruption occurs.

The extract covers:

• Organisational resilience and governance
• Risk frameworks and governance frameworks
• Organisational design and resilience
• Documented versus operational capability
• Decision-making under stress
• Rational trade-offs and organisational fragility

This extract is taken from the full RiskMasters conversation with Frédéric Gielen discussing organisational resilience, governance, leadership, and the structural choices that determine how organisations perform under pressure. This episode will be released on August 1st 2026.

Compliance is often defined through rules, regulation, and control frameworks.

The challenge is not the absence of rules. It is how those rules are interpreted and applied in practice.

In this RiskMasters bonus episode, Jennifer Geary and Natalie McManus explore the difference between rules-based compliance and principles-based compliance, and why starting with harm leads to better decisions.

The discussion focuses on a shift in sequence.

Compliance processes typically begin with the question: what does the rule require.

In practice, decisions are shaped earlier, when potential outcomes and risks are considered.

Starting with harm changes how compliance operates.

It requires organisations to consider impact before interpretation, and to apply rules in context rather than in isolation.

This creates a shift in how compliance decisions are made:

• decisions are anchored in potential harm rather than rule interpretation
• rules are applied in context rather than followed mechanically
• judgement is exercised earlier in the decision process
• supervision is balanced with trust and capability
• compliance supports outcomes as well as adherence

The extract also highlights the role of supervision.

Organisations can increase control through oversight, automation, and monitoring.

This reduces the risk of error. It also increases cost and can reduce flexibility.

Alternatively, organisations can invest in judgement, enabling individuals to act as their own control.

The balance between supervision and autonomy becomes a risk decision.

For organisations, this changes how compliance supports governance and risk management.

Compliance is not only about meeting regulatory requirements. It is about how those requirements are interpreted, prioritised, and embedded in decision-making.

This includes how harm is identified, how rules are applied in context, and how judgement is developed across the organisation.

Strengthening these capabilities improves how organisations manage compliance risk, support decision-making, and align outcomes with regulatory intent.

This extract is taken from the RiskMasters episode with Jennifer Geary and Natalie McManus, discussing principles-based compliance, decision-making, and the role of the Chief Compliance Officer.

Compliance frameworks typically include risk assessment, monitoring, reporting, governance, and policy.

The challenge is not the absence of these components. It is how they connect in practice.

In this RiskMasters bonus episode, Natalie McManus explains the IMPACT Wheel and how it reframes compliance as a continuous system aligned to the risk management lifecycle.

The discussion focuses on how compliance moves from periodic activity to real-time decision support.

Risk assessment is often treated as an annual or cyclical exercise. In practice, it occurs continuously, whenever new information, regulatory change, or operational risk emerges.

The IMPACT Wheel connects risk identification, measurement, action, monitoring, and correction into a single integrated process.

This creates a shift in how compliance operates:

• risk assessment becomes continuous and real-time
• monitoring reflects current conditions, not predefined plans
• actions are taken based on live information
• issues are surfaced through multiple channels
• insight feeds back into decision-making

The model is designed to be flexible and organisation-agnostic.

It allows compliance, audit, and control functions to operate as a connected system rather than separate activities.

Simplicity is a core principle. Clear models are easier to apply, easier to scale, and more likely to influence behaviour.

For organisations, this changes how compliance supports governance and risk management.

It shifts compliance from a structured framework to an integrated capability embedded in decision-making.

This includes how risk is assessed in context, how monitoring adapts to change, and how information flows across the organisation.

This extract is taken from the RiskMasters episode with Jennifer Geary and Natalie McManus, discussing the IMPACT Wheel, compliance frameworks, and the integration of compliance into the risk management lifecycle.