You apologise and somehow it gets worse. She’s angrier than before you opened your mouth, or she goes quiet in a way that feels final, and you’re standing there genuinely confused because you did the thing you were supposed to do.

Why the standard advice fails

The usual guidance — “just say sorry and mean it” — misses the problem entirely, because the problem isn’t sincerity. Most men who give bad apologies mean them.

The issue is what happens once shame enters the room. Instead of staying focused on the person who was hurt, the apology slowly turns into a way of managing your own discomfort. You explain why it happened. You provide context. You name your stress levels or your own hurt from earlier in the argument.

You end up defending yourself inside what was supposed to be a repair, and the other person, who came in needing acknowledgement, leaves feeling like they just got cross-examined.

The other problem is speed. A quick “sorry” often means: can we please stop feeling this now? It might be sincere, but it still feels like you are trying to close the conversation before anything has really been understood. The person on the receiving end can usually feel that. They may not say it directly, but the apology does not land.

You have pressed mute on the conflict. You have not repaired it.

And because nothing was actually understood, the same wound comes back at the next friction point, slightly larger than before.

A functional apology is a sequence, not a statement. It has four moves — acknowledgement, understanding, repair, no self-defence — and the order matters because each move answers a specific question the other person is carrying.

Miss one, or do them out of order, and the apology may sound right while still leaving something unresolved. The goal is not to feel better. The goal is to leave the other person with nothing left unanswered.

Move 1 - Acknowledgement

The first move is specific acknowledgement. Not “I’m sorry if you felt hurt” — that is an apology for the other person’s reaction, which is a different thing entirely. Specific acknowledgement names the actual behaviour: what you did, said, or failed to do. “I raised my voice at you in front of the kids” lands differently from “I’m sorry things got heated.” Specificity signals that you saw it, which is the precondition for everything that follows. If you cannot name it specifically, stop. You are not ready. Sit with what you actually did until you can describe it in one clear sentence.

Move 2 - Understanding

The second move is demonstrated understanding. This is where most apologies stall. You have named what you did; now you name what it caused. Not what you intended, but what landed.

“That would have felt dismissive” or “that probably made you feel like you could not trust me in that moment”.

This move is genuinely hard because it requires you to put your own discomfort down long enough to accurately imagine someone else’s experience. The practical way to get there is to ask one question, silently, before you speak: what did that cost them?

Hold the answer in your head for thirty seconds before you open your mouth. The apology that follows will be different.

Move 3 - Repair

Repair means naming what changes going forward — a specific, honest statement of what you will do differently, not a promise that it will never happen again.

“I won’t do it again” is a hope, not a plan.

“When I feel that way, I’ll take ten minutes before I say anything” is a plan.

The repair needs to be small enough to be real. One concrete thing. If you over-promise, you create the next wound before this one has even healed. The standard is simple: what does this actually require me to do differently, and is it something I can commit to this week?

Move 4 - No self-defence

The fourth move is not defending yourself. The rule is simple: no explanation of why you behaved that way goes into the apology itself. Explanations belong in a different conversation, at a different time, only if the other person wants them. Inside the apology, context sounds like excuse. Even if the context is legitimate — even if you were under real pressure, even if something happened earlier that contributed — it dilutes the acknowledgement and shifts the weight back onto you.

The apology has one job. Let it do that job cleanly.

This does not mean you have to absorb insults or contempt. If the other person is naming the impact, listen. If the conversation turns into attack, pause it without defending the original behaviour: “I’m not arguing with what I did. I’m trying to own that. But I don’t want this to turn into us attacking each other.” Then come back later and restart with ownership: “I want to finish what I was trying to say earlier. What I did was…”

The sequencing problem: These four moves work best in order. Repair before understanding comes across as impatience. Understanding before acknowledgement sounds like analysis of a problem you have not yet owned. If the conversation drifts, start again. You can do this explicitly: “Let me start over. What I actually did was…” Starting over is not weakness. It is precision.

The honest caveat

This framework will not repair a pattern. If you are making the same apology every three weeks, the apology is not the problem. Repeated injury to the same wound doesn’t heal with increasingly well-constructed apologies — it needs a different kind of conversation about what keeps generating the injury, and probably some external support to have it. A functional apology closes one moment. It does not substitute for addressing why the same moment keeps happening.

Before tomorrow, think of one specific thing you did or said in the last two weeks that you either apologised for badly or did not apologise for at all.

Write down one sentence: What did I actually do?

Not why. Not what they did. Not the whole story. Just what.

That sentence is where the apology starts.