🎧 Listen to this article (7:35)
Everybody makes mistakes. The interesting part is what happens after you realise you have made one.
It is easy to think accountability means admitting fault and saying sorry. Those things matter, but they are only the beginning. Accountability covers the whole sequence: recognising what happened, understanding your part, doing what you reasonably can to make it right, and changing what the failure shows can be improved.
Sorry is not the finish line
A sincere apology matters because intent matters. There is a difference between deliberately causing harm and making an honest mistake.
But good intentions do not remove accountability. You can genuinely say, “I didn’t mean for that to happen,” while still accepting that it did happen and that something now needs to be done about it.
Intent helps explain the past. Accountability deals with what happens next.
That might mean correcting the immediate problem, changing a habit, improving a checklist, adding a safeguard or redesigning a process. When a failure exposes something that can be improved, the response should leave something behind. If you decide nothing needs to change, you should be able to say why. If the same failure happens again in exactly the same way, it is reasonable to ask whether you actually learned anything.
A good response can build trust
Some mistakes rightly reduce trust, especially careless or repeated ones. But a mistake does not automatically tell you everything you need to know about the person who made it.
Before something goes wrong, you mainly know how somebody behaves when things are going well. After a mistake, you discover whether they deny it, minimise it, blame somebody else or try to hide it.
You might instead discover that they recognise the failure, own their part, repair what they can and change the way they work. The mistake does not earn them points. Their response can.
A mistake tells you what somebody did. Their response tells you something about their character, awareness and self-governance, by which I mean the standards somebody holds themselves to even when nobody else is enforcing them.
Fault and responsibility are not the same thing
Recently, a client website I manage went offline. The hosting provider caused the underlying problem, not me.
But that did not make it only somebody else’s problem. I still had to investigate what was happening, contact the host, keep the client informed, confirm the site was back up, and check it again afterwards.
Fault tells you who caused the problem. Responsibility tells you what you do about it.
That distinction matters because accountability is not only about confessing to mistakes. Sometimes nothing is your fault, but you still have something you are responsible for doing next.
The response should match the stakes
Accountability does not mean treating every mistake like a public inquiry. If I make a small mistake in my work, notice it immediately and correct it before it affects anybody, there may be little value in broadcasting a forensic account of everything that happened. I still need to understand the mistake and learn from it.
If the same mistake causes a client to lose money, exposes somebody to risk or creates serious consequences, the required response changes. The duty to learn remains the same, but who needs to know, how much they need to know and how quickly they need to know it may all change.
The difficulty is that the person who made the mistake is often also the person deciding how serious it was. That creates an obvious temptation to minimise.
One useful check is to judge the mistake not only by what happened, but by what reasonably could have happened. If you are unsure whether the consequences are significant enough to involve somebody else, that uncertainty may itself be a reason to ask for another view. Where legal, regulatory or safety obligations apply, they set the minimum response required.
Transparency does not mean saying everything to everyone
There is a difference between maintaining the complete source of truth and deciding how much of that information another person actually needs.
Now imagine a different case, where an update I make causes a brief interruption to a client website. Internally, I might record exactly what changed, when the interruption started, how long it lasted, what caused it, what was affected and what I changed afterwards.
The client may only need to know that an update I made caused a short interruption, that I fixed it and that I changed how I test updates so the same thing is less likely to happen again.
Those are not two different truths. They are two resolutions of the same truth.
The full record matters because you cannot genuinely improve a system if you rewrite the story of why it failed. Communication can be compressed, but it should not be distorted. A useful test is simple: if the client later read the full record, would they feel that the shorter explanation had misled them? If the answer is yes, it was not compression. It was concealment.
What happens when everyone wants you to stay quiet?
So far, most of this has been about your own mistakes. It gets harder when the failure belongs to a group, and your part is deciding whether to go along with hiding it.
Imagine something serious has gone wrong in a team. You want to record what happened accurately and fix the underlying problem, but others want to minimise it, remove uncomfortable facts, or present a version that protects the organisation. Now accountability has a price.
Usually there are steps before dramatic action is necessary. You can refuse to sign off on something inaccurate, raise the issue internally, escalate it above your manager or use whatever formal process exists.
But increase the stakes. What if people have been seriously harmed? What if somebody could be harmed again? What if staying silent protects your career while leaving other people exposed to the same danger?
At some point, walking away may protect you while doing nothing for them. Speaking up may then become part of the responsibility. It is easy to admire from the outside and much harder to do when your own income, career, relationships or reputation are at risk. That is why it is a test, not a slogan.
Self-governance is easier when the people around you agree with your principles. The harder question is what you do when the people around you want you to do the wrong thing.
You cannot control forgiveness
Accountability also has limits. You can apologise sincerely, repair everything you can reasonably repair, change your behaviour, and try to do better next time. You still cannot force somebody to forgive you.
Trust belongs to the other person. So does forgiveness. “I said sorry, so you have to forgive me” turns an apology into a transaction. Sometimes the consequence of a mistake is that a relationship changes permanently, and accepting that can itself be part of accountability.
Accountability is not self-punishment
There also comes a point where accountability has done its job. Once you understand what happened, repair what you reasonably can, change what needs changing, and accept the consequences, continuing to punish yourself does not make you more accountable.
Shame without learning improves nothing. The useful question is whether anything has changed because you learned from what happened.
Accountability is not simply saying, “I was wrong.” It is being able to say, “I understand what went wrong, I have done what I can to put it right, and I have changed something so I can do better next time.”
You cannot change what happened. You can change what happens next.
