How to apologize without over-explaining
You know you were in the wrong. The draft keeps growing, and somehow the longer it gets, the less it sounds like an apology.
Why this one gets stuck
An apology has one job: to make the other person feel that you understood what you did. Explaining is a different job, and it asks something of them — that they weigh your reasons and reassure you. Past a certain length an apology stops being about the person you hurt and starts being about your own discomfort. They can feel that switch even when they could not name it.
What actually makes it land
- Name the specific thing you did. Not “if I upset you” — what you actually did.
- Say what you understood about its effect. That is the part that lands, not the remorse.
- Say what changes, in one line, and only if you mean it.
What to leave out
- ✕“I'm sorry you felt…” — it relocates the problem into their reaction.
- ✕Context that works as a defence. If the reason genuinely matters, it belongs in a later, separate conversation.
- ✕Asking to be forgiven in the same message. It turns an apology into a request.
Two messages you can send
Both name the thing and stop. Neither asks for anything back.
Short
I'm sorry about yesterday — I talked over you in front of everyone, and I can see how that landed. It wasn't fair, and I'll be more careful.
When it needs a little more
I've been thinking about Thursday. I said I would handle it and then went quiet for a week, which left you covering for me with no warning. I'm sorry — that was mine to carry, not yours. I am not going to do that again.
Yours is never quite the example.
The examples above are a starting point. SAY works from your actual situation — the thread, the person, the history — and writes the message for it. Say it out loud, badly, and it takes it from there.
Try it freeTwo languages, natively