Directory · A
Not sure this is the right entry? Run the check · New here? Start with the premise
Apologizing
2 min read · 384 words
A real apology has three parts: what you did, that it was yours, and what changes. Nearly every failed apology is missing the middle one.
Is this you?
Check whatever lands. Nothing is sent anywhere.
An apology is a repair signal transmitted from one control room to another.
The system has detected that its own machinery’s output caused damage to a neighboring system — a boundary was crossed, an agreement was violated, harm was done. The repair signal communicates three things: the damage is acknowledged, the mechanism that caused it is understood, and the behavior will be adjusted. An apology that communicates all three is a functional repair. An apology that communicates fewer is a partial transmission the receiving system often recognizes as incomplete.
The machinery resists apologizing because the identity defense system reads it as threat. Acknowledging that the organism caused harm triggers the same alarm that fires when the identity file is challenged — the story of I am a good person is being asked to accommodate I did a harmful thing. The system either rejects the data (denial), minimizes it (it wasn’t that bad), or redirects it (they made me do it). These are not moral failures. They are the identity defense protocol from the Identity entry, running in real time.
A functional apology requires overriding the defense system long enough to transmit accurately. The components:
Acknowledgment. What happened. Specifically. Not if I hurt you — which places the damage in question — but I did this. The specificity tells the receiving system that the damage was actually registered, not generically gestured at.
Responsibility. Not I’m sorry you felt that way — which assigns the damage to the receiver’s interpretation. But I did this, and it caused this. The mechanism is owned. The cause is located in the transmitter’s behavior, not in the receiver’s sensitivity.
Adjustment. What changes. The receiving system needs to know that the behavior has been identified as a problem by the system that produced it. Without the adjustment signal, the apology reads as acknowledgment without consequence — which the receiving hardware correctly assesses as incomplete.
The hardest apologies are for patterns, not incidents. The organism that recognizes a single mistake can often override the defense system. The organism that recognizes a repeated pattern is being asked to revise the identity file itself — and that revision, per the Identity entry, feels like a threat proportional to how central the pattern is to the story.
Why the words fight you on the way out
You carry a working story about what kind of person you are, and it's load-bearing. An apology asks that story to absorb a new fact — I did a harmful thing — and the story defends itself first. That's where the standard distortions come from. Denial: it didn't happen that way. Minimisation: it wasn't that bad. Redirection: look what they did. None of these are signs of a bad person. They're the sound of a self-image protecting itself in real time, and everyone's does it.
The practical upshot: a functional apology needs you to hold that defence off for about thirty seconds — long enough to say the true thing before the editing starts. Not forever. Thirty seconds.
This is also why apologising for a pattern is so much harder than apologising for an incident. One mistake can be filed as out of character. A pattern can't — it asks you to revise the story itself, and it hurts in proportion to how central that part of the story is. Which is precisely why the pattern apology is the one that actually repairs anything.
What to actually say
Say what happened, that it was yours, and what changes. In that order, and without the word “but” anywhere in it.
- The three-part apology
I did this. It cost you that. Here's what I'm doing differently.
- When you don't yet know what the damage was
I think I hurt you and I don't fully understand how. Will you tell me? I'll listen and I won't argue with it.
- For a pattern, not an incident
This isn't the first time. I've been doing it for a while and you've been absorbing it, and that's on me.
- When you badly want to explain yourself
There's a reason, but it isn't an excuse. Tell me if you ever want to hear it.
- Instead of “I'm sorry you feel that way”
I did that, and it landed badly. I'm not going to argue with how it landed.
- When they're still angry afterwards
That's fair. I'm not asking you to be done with it yet.
Audit your last apology
Three minutes on one you've already given. It's easier to see the gap in the past tense.
Real questions
What makes an apology actually work?
Three things, and the receiving person is checking for all of them whether they could name them or not. What happened, specifically — specificity proves the damage actually registered rather than being gestured at. That it was yours — the cause located in your behaviour, not in their sensitivity. What changes — otherwise it's acknowledgement with no consequence, which they'll correctly read as incomplete. Miss one and it lands as a partial transmission, which is why a sincere apology can still fail.
Why does “I'm sorry you feel that way” make things worse?
Because it apologises for their reaction instead of your action. It quietly relocates the problem into their feelings, where it becomes a sensitivity issue rather than something you did — and people hear that instantly, even when they can't articulate it. “I'm sorry if I upset you” fails the same way by putting the damage in question. Replace both with the flat version: “I did that, and it landed badly.”
How do I apologise when I don't think I did anything wrong?
Separate intent from effect, and apologise for the effect, which is real whether or not you meant it. “I didn't mean it that way, and it still landed badly — I'm sorry” is honest and complete. What you should not do is apologise for the whole thing to end the conversation, while privately disagreeing. That's a lie with a short shelf life: the behaviour won't change, the apology will be revealed as management, and you'll have spent credibility you needed.
Why do I apologise for everything?
Reflex apologising is usually not about repair at all — it's pre-emptive, a way of lowering your status slightly so nobody has a reason to come after you. The tell is that it fires for things that aren't yours: weather, queues, other people's mistakes, taking up space. It also has a cost worth knowing about. Spend the word constantly and it stops carrying weight, so the one time you need it to mean something, it won't.
How do I apologise for a pattern instead of a single incident?
Name it as a pattern out loud, and do it first — that's the part they're waiting to hear. “This isn't the first time. I've been doing this for a while and you've been absorbing it.” Then skip to the change, and make it small and checkable, because for a pattern your word is already spent; only observable difference counts now. Expect this to feel disproportionately bad. You're being asked to revise your self-image, not just file a correction.
What if they don't accept my apology?
Then it isn't finished, and that's allowed. An apology is a transmission, not a transaction — you don't get to set the timetable for someone else's repair, and pressing for resolution turns the apology into one more thing they have to manage for you. “That's fair. I'm not asking you to be done with it yet” is the right response. What changes their position over time is almost never a better apology. It's the altered behaviour showing up repeatedly when they weren't looking.