Estimated read time: 7 minutes
A few weeks ago, someone asked if I could help with something on a Saturday that was already spoken for. The honest answer was simple. I couldn't. So I opened the text and typed four words: I can't this weekend.
And then I kept typing.
I added that I'd love to, which was only partly true. I added why the weekend was full, in more detail than anyone had asked for. I added an apology, then a second, smaller one. I offered to help another time, and then, because that felt vague, I offered two specific alternatives. By the time I was done, my four words had become a paragraph that read less like a reply and more like a closing argument.
I sat there with my thumb over the send button, and a thought surfaced that I couldn't quite shake: Who am I writing this for? Because it wasn't for them. They had asked a simple question. They would have been fine with a simple answer. Every extra line I'd added was for me. It was an attempt to make sure that when they read my no, they would also read all the evidence that I was still a good person.
The Paragraph Instead of the Sentence
If you're someone who overexplains, you probably know this pattern well. You can't just decline the invitation; you have to lay out your schedule. You can't just say the deadline doesn't work; you have to walk through everything else on your plate. You can't just say you're not up for it; you have to prove that you've earned the right not to be.
From the outside, it can look like thoughtfulness, and sometimes it is. But when I started paying attention to my own paragraphs, I noticed something uncomfortable. The more I cared about how someone would react, the longer my explanation became. A no to a stranger took one line. A no to someone whose approval I wanted could take ten minutes and three drafts.
The length of my explanation was never really about the other person needing more information. It was about how safe I felt letting them be disappointed.
What the Extra Words Are Really For
I've come to think of the part of me that writes these paragraphs as a kind of inner lawyer. The moment I decide to say no, she starts building my case. She anticipates every objection before anyone has raised one. She gathers evidence that I'm busy enough, tired enough, stretched thin enough, that no reasonable person could hold this against me. She's thorough, she's articulate, and she's exhausting.
What she's really doing is asking for permission. Not permission to say no, exactly, but permission to be okay with having said it. If I can get the other person to understand and agree with my reasons, then I don't have to sit with the possibility that they're disappointed in me. Their approval becomes the thing that lets me off the hook.
The trouble is that a boundary that only holds once the other person agrees with it isn't really a boundary. It's a request. And when every no quietly becomes a request, you end up handing other people a vote on decisions that were always yours to make.
Why "No" on Its Own Feels Unfinished
If a simple no feels rude or incomplete to you, there's usually a history behind that. Maybe you grew up somewhere a no without a reason was treated as defiance, and you learned that you'd better have a good explanation ready. Maybe you were the reasonable one, the person whose choices always had to make sense to everyone else. Maybe you simply learned that people were kinder to you when they understood you, and so you became very, very good at being understood.
None of that was a flaw. It was an adaptation. If being thoroughly understood once kept you out of trouble, of course your instinct is to explain yourself thoroughly now. Your nervous system isn't trying to make you look anxious in a group text. It's trying to protect you the way it learned to, long before you had any say in the matter.
But the situations you're in now are usually not the ones that taught you this. The coworker asking about a deadline, the friend asking about Saturday, the committee asking for one more volunteer, most of them don't need a case. They need an answer.
Explaining Versus Justifying
This doesn't mean you should never give a reason. Warmth and context are good things, and a relationship where you can't tell someone why you're tired would be a lonely one. The distinction that has helped me most is the difference between explaining and justifying.
Explaining is offering information because it's useful or kind. I can't this weekend, we've got a family thing Saturday. It's one reason, freely given, and it doesn't depend on the other person agreeing with it.
Justifying is offering information because you need the other person to approve of your decision before you can feel settled about it. It tends to come in stacks. It anticipates pushback that hasn't happened. And it often ends with some version of I hope that's okay, which is the tell that you're still waiting for a verdict.
Here's the question I've started asking myself: if they disagreed with my reason, would I still be saying no? If the answer is yes, then the reason isn't holding the boundary up. I am.
And if I'm the one holding it up, I don't need to include every supporting beam in the text message.
What Happens When You Say Less
The first few times I sent a shorter no, it felt almost physically uncomfortable, like I'd left the house without something important. I watched the screen for the typing bubble. I reread my one sentence and wondered if it sounded cold.
Most of the time, the reply was some version of no worries! and the conversation moved on. That was almost harder to absorb than pushback would have been, because it meant all those years of paragraphs had been protecting me from a reaction that, in most cases, was never coming.
Sometimes, of course, the reply isn't breezy. Sometimes people are disappointed, and saying less means you don't get to cushion that for them in advance. But I've found that a clear, kind sentence usually lands better than a long explanation anyway. Long explanations invite negotiation. They give the other person a list of reasons to argue with, workarounds to suggest, and openings to ask but what if. A simple no leaves less to debate, which is often kinder for both people.
What I Hope You Take With You
If you tend to overexplain, I hope you can be gentle with that part of yourself. The inner lawyer isn't trying to make you look nervous. She's been working overtime for years to keep you safe, and she's very good at her job. You don't have to fire her. You can just let her know she doesn't need to argue every case.
You're allowed to have reasons you don't share. You're allowed to make decisions that make sense to you even if they don't make sense to everyone else. And you're allowed to let someone be a little disappointed without handing them a full account of why they shouldn't be.
A no doesn't become kinder because it's longer. It becomes kinder because it's clear, and because it's honest, and because you won't be quietly resentful later about the yes you didn't want to give.
Something You Can Try
The next time you need to say no in writing, give yourself permission to draft the full paragraph first. All of it: every reason, every apology, every alternative. Don't hold back.
Then go back through it line by line and ask one question of each sentence: Is this information, or is this asking for permission?
Delete everything that's asking for permission. What's usually left is two lines at most: one reason, if you want to share it, and one line of warmth. Something like:
"I can't make it this weekend, but I hope it's a great day."
"I don't have the capacity to take that on right now. Thank you for thinking of me."
"That won't work for me this time, but please keep me in mind for the next one."
Send the shorter version. Then put your phone face down for ten minutes and notice what happens in your body while you wait. That feeling is what the paragraph was protecting you from. You don't have to make it go away. You just have to let it pass on its own, and discover that it does.
