Answer extracted from the Beyond The Plan podcast — listen to the full episode below.
Why do staff members stop raising risks and escalating concerns in failing projects?
When risks are raised but ignored repeatedly, teams eventually stop escalating because the absence of sponsor accountability and lack of psychological safety create an environment where team members know their concerns will be dismissed. Fear of challenging public commitments compounds this effect, leaving organizations blind to problems that could be addressed early.
This pattern repeats across failing projects. In cases like RoboDebt and Queensland Health, team members initially flagged serious concerns, but leadership dismissed or ignored them. After repeated cycles of being unheard, staff members rationally conclude that escalation is futile and stop trying altogether.
The root cause lies in governance structure itself. As Isabel Grae Garaway explains in this episode, when there is no clear executive sponsor with real decision-making authority, the chain of accountability breaks. Risk signals flow upward but land nowhere — there's no one empowered to act on them.
Psychological safety amplifies this silence. When team members have witnessed leadership dismiss previous concerns, they face a real cost to speaking up: they may be perceived as disloyal, obstructive, or lacking confidence in the project. Over time, the rational choice becomes silence.
The invisible cost of ignoring early warnings
The tragedy is that teams typically possess the information needed to stop failure before it accelerates. Delivery professionals see scope creep, misaligned stakeholders, and unrealistic timelines. But without a sponsor willing to hear bad news and a governance structure that rewards honesty over optimism, that knowledge stays buried.
The governance framework itself must signal that escalation is safe and valued. This requires explicit sponsor presence, clear decision rights, and a visible commitment to acting on risks raised. A point detailed in the podcast conversation, fit-for-purpose governance isn't about creating bureaucracy — it's about creating the structure that lets the right people make the right decisions at the right time.
"Governance always precedes 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, helping organizations recognize that governance structures either enable or prevent project delivery success before problems become irreversible.
For teams still raising concerns despite this environment, the episode also covers the specific mechanisms that allow some sponsors to break through denial and act on early signals—a distinction that separates recoverable projects from those lost to unaddressed drift.
See also
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 gradually as initial momentum declines.
What is the 'false start' phase in the progression toward governance and delivery failure?
The false start occurs at project beginning when scope documents are not signed off by stakeholders yet work begins anyway, with budgets awaiting approval and authority lines unclear.
What are the pre-project red flags that indicate delivery failure is likely?
Unclear sponsorship with no executive accountability, contested or unclear scope, and a business case that fails to articulate intended benefits are the primary warning signs.
Key takeaways
- Team silence in failing projects results from repeated dismissal of legitimate concerns, not from lack of visibility into problems.
- Absence of clear sponsor accountability removes the decision-maker capable of acting on escalated risks.
- Psychological safety requires visible sponsor presence and demonstrated willingness to address bad news, not just policies that promise it.
- Governance structure signals whether escalation is rewarded or punished, shaping team behavior long before delivery failure becomes obvious.