The journal

Team Performance · 2 April 2026 · 6 min read

Leading a Team After a Failure Without Blame or Denial

Leading a team after a failure means containing harm, establishing facts and setting fair accountability while making practical changes to prevent repetition.

Written by Sarah Murray

Leading a Team After a Failure Without Blame or Denial

Photograph: Immersive Leaders programme photography — all rights reserved by Immersive Leaders by ISSET

Something has gone wrong, people are asking who knew what, and your team is watching how you respond. Moving straight to blame can destroy useful information; moving straight to reassurance can look like denial. The immediate task is to contain the consequences, establish what is known and show that fairness and accountability will both survive the discussion.

Stabilise the situation before interpreting it

Check whether harm is continuing and who has authority to act. That may mean pausing work, supporting affected people, notifying the appropriate functions or following established incident procedures. Preserve relevant information through the correct channels. Do not let an urgent desire to explain the failure interfere with the practical work needed to contain it.

Be clear about your own limits. Legal, regulatory, safety or employment issues may require specialist involvement and formal processes. An informal team review should not compromise those responsibilities. Explain what happens next, who is coordinating the response and how updates will be shared. Where the position is uncertain, say so. A provisional account delivered as settled fact can become another problem to correct once better information emerges.

Acknowledge impact without assigning a premature verdict

People affected by the failure need an honest acknowledgement of what has happened. Avoid language that minimises the consequence simply because the team worked hard or meant well. Intent matters when understanding behaviour, but it does not erase impact. Equally, do not imply misconduct before there is a fair basis for that conclusion.

Tell the team what is known, what remains unverified and which questions are being investigated. Explain when they can expect another update, while recognising that confidentiality may limit what can be shared. Managers sometimes fill silence with comforting certainty because uncertainty feels weak. It is better to be precise about the gap than to create a story that colleagues immediately recognise as incomplete or self-protective.

  • What consequences still need active management or specialist support?
  • Which facts are verified, and which are currently assumptions?
  • Who needs an update, and who is responsible for providing it?

Reconstruct the work from the information available then

When it is appropriate to review the event, build an account of what happened without assuming the outcome was obvious in advance. Ask what people could see, which expectations they were working under and what made their actions appear reasonable or necessary at the time. This is not an exercise in excusing every choice. It is a way to understand the actual conditions in which decisions were made.

Use records and different perspectives rather than relying on the most confident account. Look for unclear responsibilities, conflicting priorities, missed signals and controls that were difficult to use. Notice workarounds that had become normal. A process can appear sound on paper while depending on people routinely bypassing it to complete ordinary tasks. That gap deserves investigation before another reminder to follow the process is issued.

Separate fair accountability from public blame

Accountability means examining responsibilities, decisions and consequences through a fair process. It does not mean identifying someone whose name will make the report feel complete. Consider whether expectations were clear, resources were adequate and people had appropriate authority and support. Where conduct concerns exist, use the relevant procedures rather than turning a learning discussion into an improvised disciplinary hearing.

Make the purpose of each conversation explicit. People should know whether they are contributing to operational learning, providing evidence to a formal investigation or discussing their own performance. These processes may inform one another, but they are not interchangeable. Promising a completely consequence-free conversation when you cannot honour that promise undermines trust. So does claiming to seek learning while quietly treating every contribution as a confession.

Change a condition that helped the failure happen

Translate findings into actions that address how work is organised. Clarify a decision boundary, redesign a handover, remove a conflicting target or make an escalation route usable. Training may be appropriate where knowledge or skill is genuinely missing, but it is not a universal response to inconvenient evidence about system design.

Assign an owner who has authority to implement the change and define how its effectiveness will be checked. Closing an action because a document has been updated says little about whether the risk has changed. Ask someone close to the work to test whether the proposed adjustment is practical.

  • Identify the condition each action is intended to change.
  • Check that the action owner can make the required decision.
  • Look for evidence that the change works during ordinary operations.

Rebuild confidence through consistent follow-through

After a failure, teams may become hesitant, defensive or overly dependent on approval. Restore clarity about what they can decide and where support is available. Check workload as well as morale, particularly if people are managing the original consequence alongside their normal responsibilities. Encouragement without a manageable plan can sound like a request to absorb the damage quietly.

Keep reporting on agreed changes without repeatedly reopening personal blame. Recognise useful candour and sound decisions, including decisions that expose uncomfortable information. Confidence returns through evidence that the organisation can face a problem and improve its response. The aim is not to make everyone feel that nothing serious happened. It is to make it possible to work responsibly again, with a more accurate understanding of the risks and a clearer way to address them.

Bring this to your team

We run NASA-style simulations, astronaut keynotes and leadership expeditions for organisations that need their leaders to make good calls under pressure.

Book a Call