There is no such thing as a mistake without an author. There is only a mistake whose author has been successfully misplaced.
The principle holds three things, and everything below is just those three in detail:
- Accountability should exist before the error, not after it.
- Collective decisions without personal consequences produce unclaimed outcomes.
- If nobody owns the mistake, the system that produced it will repeat it.
The Scene
The quarterly review where the number is bad. Everyone in the room can explain the number; nobody owns it. "We" appears in every sentence. The integration that slipped from three months to eighteen was a collective journey. The budget was approved by committee. The hire that didn't work out was a consensus call. By the time the consequence shows up, the decision has been socialised so thoroughly that it no longer has a parent — just a large extended family, none of whom were home at the time.
Why Smart People End Up Here
This is not cowardice, and it is not stupidity. It is a rational response to how most organisations price being wrong.
A clear owner of a decision collects the upside when it works and eats the blame when it doesn't. In most companies the blame is priced higher than the credit — losing is punished harder than winning is rewarded. So people learn, correctly, that the safe move is to make sure no decision is ever entirely theirs. Collective decisions aren't made because the group is wise. They're made because a group cannot be fired.
What the Principle Reveals
"Every mistake has a name and a surname" is not a line about taking responsibility. It's a diagnostic.
The moment you insist that every decision has exactly one owner — one human who answers for it — the org chart you actually have becomes visible, as opposed to the one framed on the wall. You find out which decisions have owners and which are orphans. And orphaned decisions are the ones that repeat: if nobody owned the mistake, the system that produced it is still running, unmodified, waiting to produce it again.
What You Can Actually Do
Assign the name before the outcome, not after. A name discovered after the error is just blame. A name assigned before it is a control. The owner doesn't have to make the decision alone — they have to be the single person who answers for it.
When something stalls, ask for the name. This is the field-tested version, and it works in any company on any Tuesday. When an approval won't move, a ticket won't close, a decision won't get made — stop asking "what's the status" and start asking whose name is on this, and who do they report to. Friction has a way of evaporating the moment a specific person realises the next sentence involves their manager's calendar. You're not being aggressive. You're restoring the name the process quietly deleted, and letting everyone see that escalation is now one short email away.
And this is exactly why your CTO doesn't like open source. A commercial vendor is, among other things, a name to put on the incident. When the thing breaks at 11pm before a board deck, the CTO wants a contract, an SLA, and a support line — not because the paid software is necessarily better, but because there is now a named party who answers for the failure. Open source removes the name. The code can be excellent and the accountability still nobody's. That's the real objection, and it's a rational one.
Where This Shows Up
- Financial. The budget line that grew forty per cent over the year, approved in pieces, owned by no one. Attach a single name to that line and the overrun tends to stop growing the same quarter it acquired one.
- Organisational. The cross-department project where Sales, Operations, and Finance each did their part correctly and the project still failed. Three correct parts, no owner of the whole. The whole is the orphan.
- Political. "We all agreed" is frequently the sound an organisation makes when it wants a decision without an owner. Watch who proposes resolving things by consensus, and notice when they propose it.
The Only Useful Question
The next time something has gone wrong and the explanation arrives in the passive voice, you don't need a root-cause workshop. You need the simplest question in management, asked out loud: who, specifically. First name, last name. Everything you can actually do about it starts there.