Accountability and Resilience: Turning Mountains Into Speed Humps

Accountability and resilience belong together because accountability is how you turn a potential mountain into a speed hump. This is the simplest way to understand accountability and resilience when work goes wrong. Accountability should not be punishment, it should be how reality becomes usable again.

For many of us, the word accountability does not conjure up learning, ownership or mature adult functioning. It conjures up childhood: “Who drew on the wall?”, “Who put that in the microwave?”, or “Why is there mud all over the sofa?”

Our responses were a masterclass in early crisis communications. “I don’t know.” “It wasn’t me.” And, if you had a sibling, the classic act of betrayal they never saw coming: “It was my brother. I would never do such a thing.” Delivered with the moral conviction of a tiny courtroom barrister covered in chocolate.

The excuses almost never worked. What followed was usually a consequence, or the kind of parental disappointment that could turn a room into a small domestic courtroom. The lesson was clear: if something goes wrong, accountability is where you are exposed, blamed and punished.

That is where the problem starts. Accountability and resilience cannot work when accountability is treated as threat. The mistake may still have happened. The consequence may still be real. The relationship may still need repair. But the moment someone can say, “This happened, this part is mine, this part is systemic, and this is what needs to happen next,” the issue becomes movable.

Without that, the issue grows. It attracts fear, silence, defensiveness, meetings, speculation and the organisational admin of finding the guilty party before anyone fixes the actual problem. Low-accountability cultures do not have fewer mistakes. They have fewer visible mistakes.

Accountability is not blame

Adults do not stop avoiding accountability, we just upgrade the vocabulary. “It wasn’t me” becomes “There were dependencies.” “My brother did it” becomes “Another department owned that part of the process.” And “I don’t know” becomes “There appears to have been some misalignment around expectations.”

At work, accountability and resilience often get misunderstood. We think taking ownership means volunteering to be blamed, shamed or marched into a meeting with sixteen senior people and a subject line that says “Quick alignment discussion.”

But accountability is not self-flagellation. It is the ability to separate what happened, what belongs to you, what belongs to the system, and what needs to move next. Defensiveness makes sense. It just does not scale. What protects your ego in the moment can damage the system over time.

Blame asks, “Who can we pin this on?” Accountability asks, “What is true, what is ours, and what needs to move now?” Blame creates fear. Accountability creates movement.

If people believe accountability means punishment, they will hide mistakes until the mistake has invited friends, hired subcontractors and become a structural problem wearing a hard hat. If people believe accountability means reality can be named without immediate public sacrifice, they will surface issues earlier, correct faster and learn faster.

This does not mean soft standards. Accountability without safety becomes blame. Safety without standards becomes avoidance. A resilient culture is not soft. It has high standards and enough safety for people to tell the truth. That is why accountability and resilience need both truth and standards.

The tangible value of accountability and resilience

This is not just a useful principle. The evidence for accountability and resilience shows the same pattern.

Amy C. Edmondson is a Harvard Business School professor whose work focuses on leadership, team learning and psychological safety. Her early research into medical teams found something counterintuitive: better-performing teams appeared to report more errors than weaker teams, not because they were necessarily making more mistakes, but because they were more willing to make those mistakes visible.

The same pattern shows up in aviation, where accountability and resilience are not branding language but safety requirements. The Aviation Safety Reporting System lets pilots, air traffic controllers, mechanics and others voluntarily report incidents, close calls and safety risks so the system can learn earlier. The FAA’s guidance says the programme depends on the “free, unrestricted flow of information” from people inside the system. If you want accountability and resilience in a safety-critical environment, you need the truth to move.

Business performance points in the same direction. Gallup’s large-scale Q12 meta-analysis covered 456 studies, 276 organisations, 54 industries, 96 countries, 112,312 work units and 2.7 million employees, with top-quartile teams outperforming bottom-quartile teams across outcomes including absenteeism, safety incidents, quality defects, productivity and profitability.

Structured debriefs and after-action reviews follow the same logic. Teams improve faster when they ask what they intended, what actually happened, what caused the gap and what needs to change.

So the value of accountability and resilience is not fewer mistakes. It is fewer hidden mistakes. Faster reporting. Faster correction. Less defensive drag. Better learning. And a system that can see itself clearly enough to adapt before the failure becomes catastrophic.

This is where accountability and resilience become personal. I learned it the awkward way, copied into an email with half the senior leadership population of the known universe.

The mistake that became useful

A couple of years ago, I was working with an African telecommunications company. The work was fast-paced and arriving at a volume I had never dealt with before, like trying to put fire-hydrant pressure through a drinking straw.

There were multiple projects, senior stakeholders, constant urgency and the kind of inbox that starts to feel less like communication and more like being attacked by an office printer with unresolved childhood issues. Then something slipped through. Not because I did not care. It slipped because the system was overloaded and I was trying to keep too many plates spinning while someone kept cheerfully adding plates.

Then the email arrived.

The first feeling was shock. Not because there was a problem. Problems happen. What shocked me was how they chose to handle it. There were a dozen better ways to approach it: a direct message, a call, a smaller email, or a simple, “Murray, this has fallen through. What is going on?” Instead, they went straight to email with all the most senior people included.

It felt totally unnecessary. Then came the irritation. The client knew the pressure, the volume and the strain. Instead of creating clarity, the escalation created heat.

That is the moment your primal child-brain wakes up. You look at the email and, somewhere inside you, a six-year-old version of yourself starts weighing up the old options. Wasn’t me. Was that department. I was never told. There were unclear dependencies. My brother did it.

The adult version sounds more sophisticated, but the mechanism is the same. It is defence. It is distance. It is ego trying to avoid impact. Part of me wanted to explain the context and prove the pressure. That would have been satisfying for about twelve seconds. It also would have made everything heavier.

Once that game starts, the original problem multiplies. Now there is theatre, blame, defensiveness, escalation and the enormous organisational admin of proving who should be symbolically fed to the corporate punishment badger.

At the time, I had been working deliberately with my Feel, Think, Act process. Notice the emotional reaction first. Make sense of it second. Only then choose the action. The shock and irritation were real, but they did not need to drive the response.

So I replied with something along the lines of:

“I am sorry, and I will comfortably take accountability for this falling through. Unfortunately, we do not have the time or capacity to focus on this right now. I am happy to deal with any consequences, but I would ask that we keep moving on project X, Y and Z before anything else falls through the cracks.”

That was accountability and resilience in practice. Not dramatic. Not heroic. Just ownership, context and movement.

I owned the miss. I did not over-own the entire system. I acknowledged the consequence, named the capacity issue and redirected attention back to the work that still needed to happen.

Their response came back quickly:

“Thank you, Murray, for being accountable here. We do acknowledge that there is a lot going on. How would you like to proceed?”

That was the shift. The moment accountability entered the room, the temperature dropped. The issue became workable again. Accountability and resilience were no longer abstract concepts. They were visible in the system.

Why accountability and resilience belong together

That response felt like magic at the time, but it was not magic. It was mechanics.

My individual accountability lowered the emotional temperature of a wider system. It stopped the conversation from becoming a blame spiral and moved the focus from punishment to priority. That is the bridge between personal and organisational resilience. A person can carry a response that either adds strain to the system or removes it.

The accountable response did not pretend the mistake was fine. It did not remove the consequence. It did not deny the capacity problem. It simply made reality usable.

The first problem is the mistake. The second problem is everything we do to avoid admitting the mistake. Most of the time, the second problem is more expensive.

Leaders need to understand this because the way they respond to mistakes determines whether people bring them reality or theatre. If every error becomes a public hanging, people will hide problems. They will manage perception and sit in meetings saying “on track” while privately wondering whether the wheels are supposed to make that noise.

The leadership tension is simple: make the truth safe enough to surface and the standard high enough to matter. Individually, it is the same. Accountability is not saying, “Everything is my fault.” It is asking, “What part of this is mine, and what can I do next?”

That is the practical connection between accountability and resilience. Accountability keeps reality visible. Resilience keeps the system moving. Together, they reduce the size, cost and drag of mistakes.

We need to stop treating accountability like the punishment phase of failure. Accountability is not the bit where everyone finds out who broke the thing and gathers round with moral snacks. It is the bit where reality becomes usable again.

Because accountability and resilience turn potential mountains into speed humps. And a resilient system is not one where nothing goes wrong. It is one where reality is reported quickly enough to still be useful.