← 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.

Why Infrastructure Warning Signs Never Reached the Red Deer Board

The server room in the credit union's Red Deer headquarters maintained a steady temperature of eighteen degrees Celsius throughout the winter of 2024, its climate control systems humming quietly behind reinforced doors that few employees ever entered. Within that room, three aging storage arrays processed millions of transactions daily, their indicator lights blinking in patterns that told a story no one at the governance level would hear until it was far too late. The arrays had been installed in 2017 with an expected service life of five years, and by January 2024 they were operating seventeen months beyond their recommended replacement date. Vendor documentation delivered to the information technology department in November 2023 had flagged the arrays as "end of extended support," a designation that meant replacement parts would become increasingly difficult to source and that the manufacturer would no longer guarantee system stability under peak load conditions.

The chief information officer had included a line item for storage infrastructure renewal in the 2024 capital budget submitted to the finance committee in September 2023. That request sat among forty-seven other capital items totalling $4.2 million, presented in a spreadsheet format that listed project descriptions in twelve-word summaries alongside estimated costs and proposed implementation timelines. The storage renewal appeared as "Core infrastructure storage array replacement (lifecycle)" with a requested allocation of $340,000. The finance committee, composed of three board members and two senior executives, approved $2.8 million in capital spending for the year and deferred the remaining items to a prioritization exercise that would occur in the second quarter. The storage arrays were among the deferred items. No discussion of the deferral decision appears in the committee minutes beyond a notation that "certain technology infrastructure items" would be reconsidered following completion of a strategic technology assessment planned for April 2024.

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.