Case Study 2
The Bad News Doesn't Reach the CEO
The Situation
An expanding mission-led entity has scaled rapidly during the last several years. It currently manages diverse initiatives across various sites, requiring additional staff, expanded management tiers, and more intricate oversight protocols.
Technically, the oversight framework appears robust. The Board maintains a consistent meeting schedule. The leadership team convenes once a week. Every division provides monthly updates. A formal risk register is maintained, alongside standard internal audit and regulatory compliance functions.
The leadership team assumes they possess a clear view of operational realities. The CEO publicly invites staff to surface obstacles but maintains a strict focus on executive accountability. She often remarks: “Bring me solutions, not just problems.” This culture is intended to foster agency. There is no explicit directive to hide unfavorable data.
The Signals
One of the entity’s primary initiatives begins to falter. The issues are subtle rather than catastrophic, yet different departments observe isolated red flags. Human Resources identifies a spike in staff departures, with exit feedback citing excessive workloads and concerns regarding the initiative’s viability.
Operations notes a delay in critical milestones. Finance observes expenditures exceeding the budget. The hiring process is stalling. A key stakeholder expresses concern over delivery standards. Seasoned staff voice private doubts regarding the project’s strategic trajectory.
Every individual concern has a rationalization and an assigned lead. A recent Internal Audit summary mentions 'localized process gaps' but fails to identify the resulting threat to revenue stability. Risk registers document technical failures but ignore the cultural dynamics causing departments to bypass protocols.
What Moves Upward
The initiative lead recognizes the friction but characterizes the project in monthly summaries as: “Progressing with manageable hurdles.” These notes mention hiring lag and slight timeline shifts, stating a mitigation strategy is active. No formal grievances are filed and no contracts have yet been breached.
In a leadership briefing, the VP asks if the matter requires senior escalation. The lead responds: “We have it under control. Escalation isn't necessary at this stage.” The VP accepts this assessment.
This filtered data flows upward. The VP reports on staffing strategies. The CFO highlights general cost pressures across the portfolio. HR shares high-level turnover metrics without isolating the specific program as a high-risk cluster. Compliance finds no policy breaches. The executive summary flags the initiative as: YELLOW. NOT RED.
The enterprise risk register covers workforce and delivery but fails to link operational friction to the erosion of external stakeholder trust. The Board views the same sterilized data. No specific report is inaccurate. No one is intentionally dishonest. No formal reporting policy has been ignored.
Then the CEO Gets a Call
Weeks later, a high-ranking official from the entity's primary donor contacts the CEO. The donor is alarmed. Delivery failures are persisting. Key dates are being missed. Talent is leaving. Consequently, the donor's trust in the entity’s execution capability is fading.
The donor bluntly asks: “What is your plan to fix this?”
The CEO is blindsided. She was aware of minor staffing issues and project adjustments, but she lacked the context that multiple warning signs were converging, threatening the organization's most vital relationship.
When she confronts her directors, she asks: “Why is this the first I am hearing of this?”
Yet, the data was already present. The organization possessed the knowledge. Warnings were voiced. Reports were filed. Every piece of data was technically true. The entity itself knew the truth; its CEO simply did not.
The Governance Stress Test
The external call bypassed the internal filters, but that call was an anomaly, not a design of the system. Had it not occurred, would the existing reporting structures have eventually identified the systemic risk? Or would the fragmented issues have been managed in silos until the damage became irreparable?
The Central Question
How does vital risk data flow through a hierarchy and lose its urgency before reaching the decision-makers who need to see the full picture?
Questions for Practitioners
- At what stage did the data flow experience friction? Is this a failure of a specific individual or a systemic failure of the architecture? What indicators would you analyze to determine if this represents a localized mishap or a fundamental governance flaw? How should an organization be restructured to identify emerging patterns without overwhelming the CEO with every minor operational issue?
About the Governance Under Pressure Observatory™
The Governance Under Pressure Observatory™ is a flagship initiative of Ngong Governance Advisory, designed to unite industry experts in investigating how internal and external stressors impact corporate decision-making and transparency. By analyzing realistic case studies, hosting recurring practitioner roundtables, and publishing detailed learning reports, the Observatory provides a platform to explore the mechanics of oversight when stakes are high. Our mission is to uncover how institutional frameworks respond to strain, helping leaders fortify their systems before small failures evolve into systemic crises. Join us as we observe local realities, learn through collaboration, and aim to govern with greater wisdom and foresight.
Read Scenario 02 Insights
This page presents a concise version of Scenario 02 for quick reference. For the full practitioner synthesis, including detailed observations, disagreements, and questions for boards, executives, and assurance leaders, read the complete insights report.