Part 3: Changing How Organisations Respond to Failure

For his final article in the three-part series, Stephen O’ Grady, a trusted colleague, project expert, and IT management veteran from the UK, explores why projects break down, how those risks surface, and how to address them before they compound. To navigate to his previous articles in this series, click below:

• Part 1: Why Projects Fail – The Structural, Cultural, and Cognitive Drivers
• Part 2: Why Organisations Pursue Failing Projects: The Psychology and Politics of Escalation
• Part 3: Changing How Organisations Respond to Failure

Failure Does Not Mean Defeat

Most organisations know how to start projects. Far fewer know how to stop them, reshape them, or challenge the assumptions that underpin them.

Changing attitudes toward failure is not about motivational slogans or new reporting templates. It requires incentives, leadership behaviours, and cultural norms that reward truth over optimism and learning over blame.

In many organisations that deliver change well, candour is safe, evidence matters, and course correction is treated as a sign of maturity rather than defeat. This article explores how to build that environment.

1. Redesign Governance to Reward Truth, Not Optimism

Governance is often the first barrier to cultural change. Many organisations still rely on models that emphasise compliance, documentation, and activity tracking. These systems often unintentionally reward teams for appearing on track rather than being on track.

To shift attitudes, governance must evolve to:

Prioritise outcomes over activity: Milestones should measure value delivered, not artefacts produced.

Create regular decision points: Structured stop, go, or reshape reviews make course correction routine rather than exceptional.

Expose uncertainty early: Governance should encourage teams to surface risks before they become crises.

Reward evidence-based reporting: Teams that provide honest assessments should be recognised, not penalised.

When governance signals that truth is valued more than optimism, behaviour changes quickly.

2. Build Safety Around Candour and Escalation

People do not hide problems because they are irresponsible. They hide them because they fear the consequences of being honest.

Psychological safety, meaning the ability to speak up without fear of embarrassment or punishment, is the foundation of high-performing project cultures.

Organisations can strengthen that safety by:

• Normalising early escalation as a responsible act.
• Responding constructively when teams raise concerns.
• Separating performance evaluation from risk reporting.
• Encouraging leaders to model openness by admitting uncertainty or past mistakes.

When people feel safe to speak the truth, issues surface early enough to be addressed.

3. Institutionalise Structured Pause Points and Exit Strategies

Most organisations design projects to start, not to stop. As a result, continuation becomes the default, even when evidence suggests a different path.

To counter this, organisations should:

Define clear exit criteria: Projects should have explicit conditions under which they will be paused, reshaped, or stopped.

Schedule formal pause points: These should be built into the lifecycle, not triggered only when problems arise.

Use independent challenge: External reviewers or cross-functional peers can provide objective assessment.

Frame cancellation as a success: Stopping a project that no longer makes sense is a sign of strategic discipline, not failure.

When exit strategies are designed into the system, teams no longer feel trapped in failing trajectories.

4.  Model Leadership Behaviours That Encourage Realism

Culture follows leadership. If leaders reward optimism, they will get optimism; if they reward candour, they will get candour. Effective leaders ask for evidence rather than reassurance and treat course correction as something worth recognising, not something to hide. They are willing to admit when assumptions were wrong and avoid punishing teams for raising uncomfortable truths. When problems surface, they respond with curiosity instead of blame. In that environment, realism and humility become the norm, and teams feel safe to operate the same way.

5. Turn Lessons Learned Into Lessons Applied

Many organisations conduct “lessons learned” exercises, but few integrate those lessons into future work. The result is ritualistic reflection without meaningful change.

To break this cycle, organisations should:

Capture insights continuously, not only at the end: Real-time learning is more accurate and more actionable.

Translate lessons into standards: If a lesson is important, it should become a requirement, not a memory.

Make learning visible: Share insights across teams, functions, and business units.

Hold leaders accountable: If the same mistakes recur, it is a leadership issue, not a project issue.

Learning cultures do not avoid failure entirely, but they do avoid repeating it.

Final Thoughts

Changing attitudes toward project failure is not about eliminating risk or demanding perfection. It is about creating environments where truth is valued, evidence guides decisions, and course correction is seen as a strength. Organisations that work this way deliver more reliably, adapt more effectively, and waste fewer resources on initiatives that no longer make sense.

Often, putting this into practice is where many teams struggle. It requires more than intent, but structured governance, clear decision frameworks, and consistent leadership behaviours applied over time. Ferroque Systems supports organisations in building these capabilities, helping teams move from theory to execution and creating project environments where better decisions happen earlier and outcomes improve as a result. If you would like to learn more about these services, connect with our experts.