Why Failure Sharing Matters for Team Innovation

Most organisations have learned how to celebrate success. Promotions, award ceremonies, LinkedIn shoutouts, and these are all ways we reinforce performance and progress.

But what happens when things go wrong?

When projects fall flat or decisions miss the mark?

In most environments, failure becomes something to hide or downplay. But in reality, failure is one of the most consistent, yet underutilised, tools for learning and for innovation. If we want our teams to think creatively, take healthy risks, and learn continuously, we need to create space to talk about what didn't work, and more importantly, why.

This is where failure sharing comes in.

Not as a post-mortem or finger-pointing session, but as a cultural shift, one that values growth over perfectionism, and collective learning over individual avoidance. The Failure Sharing workshop is built around exactly thisidea. Creating the psychological safety and practical tools to make honest reflection not only possible, but powerful.

Table of Contents

• What is failure sharing?

• Failure sharing vs post-mortems: what is the difference?

• Does your team need a failure sharing practice?

• How to introduce failure sharing in 6 steps

• Measuring the impact of failure sharing

• Can smaller teams benefit from failure sharing?

• How to implement failure sharing successfully

• Summary

Executive Summary

Failure sharing is the intentional practice of creating facilitated space, within teams and organisations, to speak openly about what didn't work, understand why, and extract learning that drives future improvement.

It is not about dwelling on failure or assigning blame.

It is a cultural shift that values growth over perfectionism and collective learning over individual avoidance.

This workshop focuses on building the psychological safety that makes honest reflection possible, and provides a practical framework for teams to discuss failure productively, reframe it constructively, and turn it into fuel for innovation.

What Is Failure Sharing?

Failure sharing is the practice of deliberately creating opportunities for teams to discuss setbacks, mistakes, and things that didn't go to plan, in a structured, facilitated, psychologically safe environment that turns those experiences into collective learning.

The goal is to understand the failure, reframe it, and share it in a way that others can learn from. You want to explore three steps that make this possible:

• How to establish safety and trust before failure sharing begins

• How to discuss failures without moving immediately into solutions or blame

• How to reconstruct and reframe failures into future-ready insight

One simple but powerful practice is the 10-minute failure-sharing session.

Just like a stand-up meeting, it gives people space to reflect on what didn't work, and why. It allows teams to identify recurring issues, surface patterns, and prevent repeated mistakes. But perhaps more importantly, it models that failure is safe to talk about.

Failure Sharing vs Post-Mortems, They Are Not the Same

Both failure sharing and post-mortem practices involve reflecting on what went wrong, but they operate very differently, and the distinction matters for how teams experience them.

A post-mortem is typically a formal, retrospective process triggered by a significant failure or project completion. It tends to be structured around what happened, why it happened, and what should change.

While valuable, post-mortems can feel high-stakes and blame-adjacent, particularly if they are only used when something goes significantly wrong.

Failure sharing is different in both tone and cadence. It is a regular, lightweight cultural practice, more like a habit than a process. It does not wait for a significant failure; it creates ongoing space to surface smaller setbacks, misalignments, and learning opportunities before they become larger problems.

Where post-mortems look back, failure sharing looks forward. Where post-mortems are reactive, failure sharing is a proactive investment in learning culture.

The two can coexist, but failure sharing fills the gap that post-mortems leave: the everyday moments of honest reflection that most teams never have.

Does Your Team Need a Failure Sharing Practice?

If people in your team play it safe, stop experimenting, or rarely ask for help...fear is probably present.

One of the biggest blockers to innovation isn't capability. It's fear.

When people are afraid of blame or embarrassment, they stop taking risks, stop sharing ideas that might not work, and stop flagging problems early. And that puts a ceiling on what's possible.

In one Failure Sharing workshop everyone was quiet, everyone was cautious. They all had something to say, to add, but they were fearful of the consequences of raising their hand. It takes courage, and one woman who cautiously raised her hand said what they were all thinking, "What if I speak up about failure, and it goes on my record and I am never called on again for new projects?", my response was "What if you all spoke up, and for, each other?"

The question is not whether failure happens in your team, it does, in every team. The question is whether your team has a healthy relationship with it.

• Do people feel safe admitting mistakes?

• Are setbacks treated as learning opportunities or as evidence of incompetence?

• Is the culture one of curiosity or one of avoidance?

Failure sharing encourages teams to let go of perfectionism, embrace change, and increase gratitude for the effort behind every attempt, successful or not. It reinforces the mindset that growth is ongoing, and that reflection matters just as much as execution.

How to Introduce Failure Sharing in 6 Steps

These steps are grounded in the practical approach used in the Failure Sharing workshop, and can be adapted for teams at any stage of their psychological safety journey.

1. Build psychological safety first. Before any failure sharing can happen, the environment must feel genuinely safe. That means establishing clear norms: no blame, no judgement, no immediate pivoting to solutions. Safety is not assumed, it is built, deliberately and over time.

2. Leaders go first. Vulnerability from the top signals that it is safe for others to follow. When a leader shares a real setback, i.e. what happened, what they learned, and what they would do differently, it shifts the culture more powerfully than any policy can.

3. Set clear ground rules for sharing. The session is not about solutions or accountability, it is about honest reflection. What happened? What did we learn? What would we do differently? Keep the focus on understanding, not fixing.

4. Use a simple, consistent structure. The 10-minute failure-sharing session works well as a regular ritual, brief, structured, and recurring. Consistency is what makes it safe, because people know what to expect and how it works.

5. Separate reflection from action. One of the most common mistakes is moving too quickly from "what went wrong" to "what we need to do about it." Give the reflection its own space. Action steps can (and will!) follow, but not before the learning has been properly heard.

6. Celebrate the sharing, not just the outcome. Acknowledge the courage it takes to share a setback openly. Recognise the contribution of honest reflection to the team's growth. This is what makes failure sharing a cultural norm rather than a one-off exercise.

Measuring the Impact of Failure Sharing

The impact of failure sharing is often felt before it is formally measured. Key signs that it is working include:

Team members start sharing their learnings with one another as a matter of habit, simply ensuring no one repeats their mistake again. Teams that reach this inflection point report increased feelings of collaboration and trust.  

Here are some indicators that your approach is working:

• Increased willingness to experiment and take healthy risks, people know that setbacks will be met with curiosity, not blame.

• Fewer repeated mistakes, recurring issues get surfaced and addressed rather than quietly repeated.

• Faster feedback loops and more open communication across the team.

• Greater psychological safety in team surveys and informal feedback.

• More honest, productive 1:1 conversations between managers and team members.

• New ideas and approaches emerging directly from what "didn't work" previouslyYou feel less reactive and more in control of your day and your emotions.

The result is teams that are more adaptive, more innovative, and more connected. Leaders who model vulnerability invite trust. And organisations that learn from every outcome, good or bad, position themselves to thrive in times of change.

Can Smaller Teams Benefit from Failure Sharing?

Failure sharing is arguably most powerful in smaller teams, where every mistake is visible and every lesson is immediately applicable. In a small team, there is nowhere for failure to hide, which can make the fear of it more acute, but it also means that when the team builds a healthy relationship with failure, the benefits are felt immediately and by everyone.

Small teams can also move faster from insight to action. When a failure-sharing session surfaces a recurring problem, a small team can address it the same week. That speed of learning is a genuine competitive advantage.

Psychological safety is also somewhat easier to build in smaller groups with consistent membership, because trust develops through repeated, positive interactions over time. The workshop is equally effective for small teams and provides a framework that scales naturally as teams grow.

How to Implement Failure Sharing Successfully

It is easy to say that failure is part of innovation. But unless that belief shows up in practice, in team rituals, in leadership language, and in performance conversations, it remains theoretical.

The Failure Sharing workshop is based on the belief that failure is not the opposite of success. It is a key ingredient.

To implement effectively:

• Start with a leader sharing their own failure. This single act does more to build psychological safety than any framework or policy. Choose something real, reflect on it honestly, and model the kind of sharing you want to see.

• Introduce the 10-minute session as a regular ritual. Keep it short, structured, and consistent. Over time, it becomes a habit rather than an event.

• Use the five-step framework consistently. Deconstruct, Assess, Reconstruct. Reframe. Boundaries. Establish safety, discuss without blame or solutions, then reconstruct the failure into future-ready insight. The structure to failure sharing is what makes the conversation productive.

• Separate failure sharing from performance management. If people fear that what they share will be used against them, they will not share. The session must be a learning space, not an accountability space.

• Celebrate the courage to share. Acknowledge openly when someone brings a real setback to the table. The culture of failure sharing is built one honest conversation at a time.

Summary

Teams that learn from failure are more adaptive, more innovative, and more connected. Leaders who model vulnerability invite trust. And organisations that learn from every outcome, good or bad, position themselves to thrive in times of change.

The tools and framework from the Failure Sharing workshop, psychological safety foundations, the five-step sharing structure, and the 10-minute session ritual, are practical, accessible, and immediately applicable.

They do not require a culture overhaul; they create one, one honest conversation at a time.

Failure isn't the opposite of success. It is a key ingredient.

And the teams that know how to use it are the ones that keep getting better.

---

References:

• TinyBox UG. (2021). Failure Sharing & Team Dynamics for teams

• Amy Edmondson. (2019). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth.

• McKinsey & Company. (2023). The Power of Learning from Unsuccessful Projects.