Answer extracted from the Beyond The Plan podcast — listen to the full episode below.
How does the RoboDebt program exemplify governance failure in public sector delivery?
RoboDebt (2015–2019) failed because no single executive held accountability for decision-making, despite governance structures being in place. Risk registers went unreviewed, frontline staff warnings about incorrect calculations were ignored, and legal concerns were never escalated to senior decision-makers—the machinery of governance existed, but nobody actually used it.
The RoboDebt story reveals a crucial distinction: governance failure is not the same as the absence of governance structures. The Australian government had all the formal frameworks in place—committees, risk registers, audit trails, oversight bodies. What was missing was the will to enforce them.
Multiple agencies and ministers shared responsibility, which meant nobody felt fully accountable. When a steering committee meets but produces zero decisions, as Isabel Gray-Garraway explains in the podcast, the project team fills the void with guesswork and pushes forward unsupervised. That's exactly what happened: the RoboDebt team operated in a decision-making vacuum, making critical choices without proper executive sign-off.
Frontline staff—the people closest to the data and the harm being caused—raised alarms about incorrect numbers and traumatized citizens. These escalations never reached the top. Risk signals were systematically ignored, not because they were hidden, but because nobody with real power was listening.
When governance theatre masks absence of accountability
The RoboDebt failure cost the Australian government close to $2 billion in refunds, repayments, reimbursements, and compensation. A Royal Commission wasn't held until 2023, three years after the program ended. Six years later, the reputational damage persists.
This is the signature of governance failure: the infrastructure looks solid on paper, but nobody is making the hard calls. Legal teams worried about the program's legality, but their concerns weren't escalated. Risk registers existed, but weren't reviewed. Audit processes happened, but findings were deprioritized. The governance machinery ran in neutral.
What made RoboDebt instructive is that it wasn't a technology problem—the systems worked fine technically. It wasn't a data problem; the algorithms did what they were told. As discussed in this episode, the program failed because the people at the top never took ownership of the risk trade-offs, never insisted on evidence before scaling up, and never listened to the voices warning them from the floor.
"Governance is the structure and systems that ensure the right people make the right decisions at the right time about project and delivery risk."
Isabel Gray-Garraway — Director of ICT Corporate Portfolio at Fire and Rescue NSW. With 25 years in project delivery spanning defence, government, and public-private hybrid organisations, she brings deep expertise in accountability, risk management, and enterprise governance. She previously managed a $200 million rolling program at Transport for New South Wales, leading a 100-person team focused on road safety regulation transformation. Her foundation in defence sector governance taught her the inseparable link between risk, accountability, and delivery outcomes.
The RoboDebt Royal Commission found that the governance structures existed but were never actually invoked to manage escalations, challenge assumptions, or halt an obviously broken process—a pattern that repeats across failed public programs when accountability is distributed too widely.
See also
What is the core definition of governance in project delivery, and how does it differ from administration and project management?
Governance is the structure and systems that ensure the right people make the right decisions at the right time about project and delivery risk. It is fundamentally distinct from project management and administration—it's about decision authority and accountability, not task execution.
How should governance frameworks evolve once established to remain fit-for-purpose?
Governance frameworks should be living documents with continuous review and self-reflection. As market conditions change, the economy shifts, and organisational priorities evolve, governance must adapt accordingly to remain effective.
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 on internal teams and ensures objective, uncompromised oversight of critical decisions.