Mentavo
"Sorry, I can't make it."
That would have covered it. Instead what follows is: "…because I've already been out twice this week and I have an early start tomorrow, and honestly I'm pretty wrecked at the moment, otherwise I'd say yes immediately, it's really not about you."
Five sentences for information that would have fitted in one.
And often a message afterwards, in which the whole thing gets contextualised once more.
How this differs from people pleasing
The two get lumped together, but they sit at different points.
With people pleasing the boundary never gets drawn at all. You agree although you don't want to, because harmony feels more important in the moment than your own state.
With overexplaining the boundary does get drawn. The no stands. The person has done what the advice recommends.
They just don't go quiet afterwards. They supply reasons, apologise, qualify, offer alternatives, describe their circumstances. The decision has been made, but it isn't allowed to stand.
Which is why "just say no" barely helps here. The no has already been said. The problem starts after it.
What the explanation is actually looking for
On the face of it, the goal is to be understood.
Usually it's something else: for the refusal to be accepted without anyone being disappointed. So not understanding, but agreement.
The difference is substantial. Understanding can be produced – short, clear information is generally enough. Agreement can't. The other person is allowed to be disappointed, however good the reason.
Continuing to explain is an attempt to steer someone else's feeling. It doesn't work, and that's exactly why it doesn't stop. As long as no confirmation arrives, every further sentence feels like the attempt that's still missing.
Why several reasons land weaker than one
There's an uncomfortable side effect.
A short statement is a statement. An extensively justified statement is an invitation to assess.
Give five reasons and you've supplied five points of attack. Each can be dismantled individually: "Come later then." "It'll only take an hour." "Next week works too."
A decision turns into a negotiation – not because the other person is being unfair, but because the form invites it.
There's a further effect, rarely intended: the longer the justification, the more it sounds as though the refusal genuinely required justifying. Short answers assume your decision is fine. Long ones implicitly question it.
The assumption underneath
Almost always the same thought sits below it: that your own wish isn't a sufficient reason on its own.
"I don't feel like it" feels inadmissible. "I'm exhausted" feels better. "I have something on" feels safe – which is why one occasionally gets invented.
What's at work is a ranking of reasons in which your own needs sit at the bottom and only become valid through external circumstances.
That ranking also explains why boundaries produce a guilty conscience in some people, even harmless ones. The piece on why setting boundaries can feel selfish goes into that mechanism.
The part that happens inside your own head
A second driver is your picture of what the other person is now thinking.
In many cases the long explanation isn't a response to anything said, but to an assumption: he thinks I'm unreliable. She's definitely hurt. That must have sounded like an excuse.
These assumptions are interpretations, not information. How easily they grow into entire scenarios is covered in the piece on constantly interpreting what other people might be thinking.
What's striking is that the follow-up often arrives with a delay – hours later, by message, although the conversation was long over. What triggers it then isn't the situation, but your own thinking about the situation.
In writing it's especially hard
In conversation an answer ends at some point, because the other person starts speaking. In writing it doesn't end by itself.
A message can be revised as often as you like before sending. And because reading your own lines back makes you notice each time that something might read as curt, the text grows with every pass. "Sorry, that doesn't work for me" becomes three lines, then five.
There's also no reaction to go on. In conversation you see immediately how something lands. With a message there's a pause in which nothing comes back – and that pause frequently gets filled with more sentences, sometimes in a second message afterwards.
So a simple rule for yourself helps: write one version, cut it once, send it. Not because short messages are better, but because the second and third revision almost always add justification and rarely add information.
When explaining is the right call
This isn't an argument for being terse. Explanations are often appropriate.
The difference comes down to one question: does the explanation serve the other person – or me?
It serves them when they get something out of it: when they have to plan around it, when the refusal affects them, when trust depends on it, when it concerns shared work where the reason is relevant.
It serves me when I mainly want to lower my own unease. For that it's a poor instrument, because the relief only lasts until the next thought.
A practical marker: when the urge to add something appears while you're still speaking, the informative part is usually already over.
What can change in small steps
A radical switch rarely works. Gradual changes are more realistic.
One reason instead of three
The refusal stays the same, the surface area gets smaller. One reason is almost always enough.
Nothing afterwards
The explanation ends with the conversation. If you still want to write a message two hours later, you can draft it and leave it; the next day it's rarely still necessary.
Sitting through the pause
A short no is often followed by silence. That silence isn't rejection, just the moment the other person takes to respond. Many explanations start exactly here – not as an answer, but as a reaction to a few seconds of uncertainty.
Recording such situations over a few weeks sometimes reveals a pattern. In Mentavo, short notes and check-ins can be traced back side by side, and it occasionally becomes visible that the need to justify appears far more often with particular people or in particular states. That explains nothing on its own, but it does show where it begins.
Questions that show the difference
- Who does the explanation I'm about to give actually serve?
- What would I say if I could assume my no would be accepted?
- Who do I explain myself to most – and why there in particular?
- What would be the shortest honest version of my answer?
What this article doesn't claim
This piece offers no diagnosis and describes no condition. Explaining at length is common, friendly in many contexts, and by no means a problem in itself.
Nor does it claim short answers are always the better choice. In some relationships and cultures, detailed justification is simply the usual form of politeness.
If the pressure to constantly justify yourself becomes a lasting burden, or is tied to strong fear of rejection, a conversation with a professional is a better route than further self-observation.
Conclusion: a no is information
Most people don't overexplain because they speak uncertainly. They do it because they're trying to pre-empt a reaction they can't control.
A short no isn't unkind. It's a piece of information about where you are – and the other person may do with it as they like.
That's the real demand here: the refusal doesn't have to be well received in order to be fine.
