Answer extracted from the Beyond The Plan podcast — listen to the full episode below.
How should governance frameworks stay fit-for-purpose as conditions change?
Governance frameworks must be living documents with continuous review and adjustment, not static structures. As market conditions shift, organizational context evolves, and risks emerge, frameworks require consistent monitoring and deep dives into problems early—before issues cascade into catastrophic failures like those in RoboDebt and Queensland Health.
The Governance Framework as an Active, Evolving System
Fit-for-purpose governance is not a set-and-forget model. Frameworks must reflect the actual risk environment and operational reality of the organization, adapting as circumstances change. When Isabel Grae Garaway discusses governance in this episode, she emphasizes that governance should enable decision-making at the right time—and that enablement must evolve as the organization and its challenges evolve.
The core principle is simple: governance should scale proportionally to risk, not remain static regardless of changing conditions. A framework designed for stable conditions may become ineffective when markets shift or organizational complexity increases. Equally, governance that was adequate five years ago may no longer suit the organization's current operating environment.
Early Detection and Intervention: The Cost of Delay
One of the starkest lessons from governance failures is that early intervention saves catastrophe. When risks are raised within a framework, they should trigger investigation and response immediately, not be deferred or ignored. The absence of this mechanism—where risks surface but no action follows—creates the conditions for collapse.
As explored in the Beyond The Plan episode, deep dives should be commissioned as soon as concerning signals appear, preventing the slow escalation that turns manageable problems into organizational crises. The failures seen in programs like RoboDebt and Queensland Health were not sudden; they were the result of risks ignored across months or years, compounded by governance structures that failed to demand action.
"Governance always precede delivery failure. You can tell a project that's going to fail before it's even started."
Isabel Grae Garaway — Governance Expert. Garaway began her career in defence, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She specializes in fit-for-purpose governance structures that enable organizations to detect and prevent project delivery failures before they occur.
The governance review process itself must be continuous and reflexive, not an annual checkbox. As a point explored in detail in the podcast, organizations that treat governance as an active conversation—challenging processes, asking what could improve, and adjusting without fear—create resilience. Those that treat it as a static rulebook risk being blindsided by changing circumstances.
Key takeaways
- Governance frameworks must adapt as market conditions, organizational context, and risk profiles change—static frameworks become unfit over time.
- Risk-based scaling means governance intensity should match actual risk exposure, not remain constant regardless of circumstances.
- Early intervention on emerging risks prevents escalation into catastrophic failures; frameworks must demand investigation and response when signals appear.
- Continuous review and self-reflection enable governance to remain fit-for-purpose; governance should be actively challenged and refined, not treated as static rules.
See also
What role does independent challenge play in effective governance frameworks?
Independent challenge by external experts, rather than internal assurance, prevents the 'fox watching the henhouse' dynamic. This removes tension and ensures objective oversight of governance and delivery.
Why do staff members stop raising risks and escalating concerns in failing projects?
When risks are raised but ignored repeatedly, as happened in RoboDebt and Queensland Health, teams eventually stop escalating. The absence of sponsor accountability and responsiveness breaks the feedback loop.
How does the 'early drift' phase differ from the false start in project failure patterns?
In early drift, sponsors become progressively absent, delegations increase with misaligned views, project teams reduce detailed updates, and scope creep occurs silently—creating a gradual descent rather than an immediate crisis.