← University
Operational Risk Reporting for Boards and Executives (Faculty of Governance lens)
0 of 4

A mid-sized credit union headquartered in Red Deer, with 37 branches spread across central and northern Alberta, experienced a catastrophic technology failure on March 15, 2024. The incident began shortly after 9:00 AM when branch managers started reporting erratic behaviour in the core banking system, with some transactions processing normally while others were inexplicably rejected. Within 90 minutes, a routine backup procedure triggered an unexpected cascade failure that brought the entire digital infrastructure to a standstill. Members attempting to access accounts through online banking received error messages, debit card transactions at point-of-sale terminals throughout the province declined randomly, and tellers at physical branches found themselves unable to process even the simplest deposits or withdrawals.

The credit union's chief executive officer spent the morning fielding calls from branch managers while the information technology team worked to identify the source of the failure. By early afternoon, the organization had activated its business continuity protocols, but the damage to member confidence and operational capacity was already substantial. The board of directors received its first notification of the incident several hours after the initial reports from branch managers, and the information that reached them was fragmentary and inconsistent with what frontline staff were experiencing.

In the weeks following the incident, the board undertook a review of the circumstances that had led to the failure and the organizational response. That review revealed that warning signs had existed in the weeks and months prior to March 15. System performance metrics had shown gradual degradation, vendor support tickets had accumulated, and information technology staff had expressed concerns about infrastructure capacity in internal communications. None of this information had reached the board in a form that would have enabled meaningful oversight or intervention. The operational risk reports that the board had been receiving focused on a different set of concerns entirely and did not include the indicators that might have signalled the impending failure.

The credit union now faces a series of questions about how operational risk information flows through the organization. The board requires a reporting framework that provides visibility into the threats most likely to disrupt organizational objectives, without overwhelming directors with operational detail that obscures rather than illuminates. Management must determine which metrics and indicators capture meaningful risk exposure and how to present that information in formats that support governance rather than compliance theatre. Most critically, the organization must establish clear thresholds for escalation — criteria that determine which risks warrant board attention and which can be managed at lower levels of the organization without creating liability gaps or governance failures.

Designing Escalation Thresholds That Distinguish Governance From Operations

When the chief information officer of the Red Deer credit union sat down with the board chair three weeks after the March 15 catastrophe, she brought with her a single sheet of paper containing a question that would reshape how the organization thought about risk reporting. The question was deceptively simple: at what point should the accumulating vendor support tickets have moved from an operational concern managed by her team to a governance matter requiring board awareness? The answer, she acknowledged, was not obvious. Her department had been managing those tickets in the ordinary course of business, escalating internally within the technology function, and addressing them according to priority rankings established years earlier. Nothing in the existing escalation framework suggested that the pattern of tickets—their increasing frequency, their concentration in core banking subsystems, their relationship to aging infrastructure—constituted information the board needed to receive. The framework had been designed to keep operational noise away from directors, and it had succeeded in doing precisely that, with consequences that were now painfully apparent.

This question—where does operational management end and governance oversight begin—sits at the heart of organizational accountability in regulated financial institutions. The distinction matters because directors occupy a fundamentally different position than managers in both law and organizational structure. Directors owe fiduciary duties to the credit union itself, duties that include the obligation to act honestly and in good faith with a view to the best interests of the organization, as articulated in the Business Corporations Act and applied through the Credit Union Act. These duties cannot be fulfilled if directors lack access to the information necessary for meaningful oversight. At the same time, directors are not operators. They do not manage daily activities, supervise staff, or make the hundreds of routine decisions that keep a financial institution functioning. The challenge lies in designing systems that deliver the right information to directors without either overwhelming them with operational detail or starving them of material facts.

That’s the free preview

You’ve reached the end of what’s open to read. The rest of this lesson is part of a $79 course — purchasing unlocks it, or sign in if you already have access.