There is a message in your drafts folder. It is four hundred words long. Its entire purpose is to say the word no.
I know this because I have written that message roughly six hundred times. It opens with a paragraph about how much you value them. It moves into a paragraph about how complicated things are at the moment. It contains the phrase "I really wish I could." Somewhere in the fourth paragraph, buried in a subordinate clause, is the actual answer, and it is so heavily upholstered that a reasonable person could read the whole thing and come away thinking you said maybe.
That message is not kind. It only feels kind. Let us talk about how to write the other version, because this is a learnable skill and it will improve your working life more than almost anything else on this blog.
Two ways to get it wrong
Mush is one. Long, warm, apologetic, and unclear. The reader has to do detective work to find out what you decided, and if they get it wrong they will come back with a follow up question, and now you have to say no twice.
Armour is the other. Short, cold, procedural. "Unfortunately this is not something we offer." Technically clear, and it lands like a slap, particularly from a person the member thought they had a relationship with.
The good version is short and warm, which sounds like a contradiction until you see it done. It is not a middle point between mush and armour. It is a different thing built from a different structure.
Why mush is genuinely unkind
Three reasons, and they are worth internalising because the instinct to soften is so strong.
It wastes their time. Someone waiting on an answer would much rather have it in the first sentence than in the fourteenth.
It creates false hope. Ambiguity gets read optimistically, because people read hopefully. You meant "no." They heard "not right now." In three weeks they will ask again, and the second no will feel like a change of heart rather than a repetition, and they will be more hurt than if you had been clear the first time.
And it makes it about you. Four paragraphs of your regret, your difficulties, and your wishes puts you at the centre of a message that was supposed to be about their request. The reader ends up managing your feelings about your own decision, which is a strange thing to hand somebody.
The structure: the thing, the reason, the door
Almost every hard message fits into three short parts.
The thing. Your answer, in the first or second sentence, in plain words.
The reason. One reason. Honest, brief, not defensive.
The door. What is possible, or what happens next, or simply a warm close that does not reopen the decision.
Here is a request to be featured, declined.
"I am not going to do a spotlight on your work this month. I keep those for members who have been around a while and I want to hold that line so it stays meaningful. If you are still keen in the spring, ask me again and I will happily look at it then."
Three sentences. Clear, warm, no wobble, and it ends somewhere pleasant. Compare the four hundred word version. The short one is the kinder one and it is not close.
Lead with the answer
Whatever you do, do this. The answer goes at the top.
We are all trained to build up to bad news, which works in speech, where tone carries the warmth. It fails badly in writing, because the reader is scanning for the verdict and everything before it registers as stalling. By the time they find it they are braced and slightly irritated.
"I cannot do this." "The answer is no." "I am going to keep the price where it is." First sentence.
Then the warmth, which now reads as genuine because it is not doing the work of concealment.
One reason, and only one
Multiple reasons weaken a decision. This is counterintuitive and completely reliable.
When you give five reasons, you invite five negotiations. Each one is a door. "Well, what if the timing were different? What if I helped with that part? What if we did it in a smaller way?" You have handed over a map of your defences.
One reason is a fact. Five reasons is a case, and cases can be argued with.
Also, pick the true one. Not the most flattering one, not the most professional sounding one. If the real reason is "I do not want to," you can say a version of that: "This is not something I want to take on right now." Nobody can argue with a preference honestly stated, and people respect it far more than an invented scheduling conflict.
Cut the apology stack
Count the sorrys in your draft. If there is more than one, delete the others.
"Sorry, I know this is annoying, sorry for the delay, sorry to be difficult" reads as anxiety, and anxiety in a decision maker makes the other person uneasy. It also subtly asks them to reassure you, which is not their job in this conversation.
One clean acknowledgement is plenty. "I know this is not the answer you were hoping for." Then move on.
Also delete "unfortunately," "I am afraid," and "just." They add nothing and they make you sound smaller than you are.
Do not borrow authority you do not have
A tempting move is hiding behind policy. "Unfortunately our policy does not allow this."
If it genuinely is a written policy, fine, name it. If it is not, do not invent an institution to stand behind. You are a person making a decision, and members can tell. The invented-policy voice makes you sound like a call centre and it removes the one thing your community is actually built on, which is that a specific human is running the place.
"I have decided not to" is stronger, more honest, and oddly more respected than "our policy states."
When you are correcting someone
Different flavour of hard message, same structure, with one extra rule: name the behaviour, not the person.
"That reply came across as pretty sharp and I do not think you meant it that way" is a sentence somebody can act on. "You are being aggressive" is an identity claim they have to defend.
Two more things that help. Be specific about which message, because vagueness makes people paranoid about everything they have ever posted. And say what you want instead, not just what you want stopped. "Can you keep feedback on the work rather than the person" gives them somewhere to go.
And send it privately. Always. A correction delivered in public is a punishment whether or not you meant it as one.
The anger you might be feeling
Sometimes the hard message is hard because you are irritated, and the mush is a lid on that.
Write the angry version. Genuinely, in a document that is not a message box, with no recipient. Get it all out, including the unfair parts. Then close it and write the real one from the calm remainder.
The angry draft is not wasted work. It tells you what the actual issue is, which is often not the thing you were about to write about. And it removes the risk of a stray sharp edge, which is what people remember for years.
Wait a night if you possibly can. Almost nothing in community management genuinely needs a reply within two hours, and the version you write in the morning is always better.
When you are the one who got it wrong
The same principles invert neatly.
Lead with it. "I got this wrong." One sentence on what happened, no elaborate explanation, because explanation reads as excuse. Then what you are doing about it, specifically. Then stop.
Do not over-apologise here either, and do not spiral. A founder performing extended self flagellation puts members in the position of comforting the person who made the mistake, and it makes it harder for anybody to raise the next problem with you.
"I got this wrong. The session link was broken for the first fifteen minutes and I did not notice. I have added a checklist to my prep so it does not happen again, and the recording is up now." That is a complete apology and it takes eleven seconds to read.
One boundary about aftermath
Whatever the hard conversation was, keep it where it happened.
Do not paste the exchange into a group chat, do not post a subtweet about it, do not describe it to another member even vaguely, and do not use it as a teaching example anywhere it could be recognised. If you need to process it, take it to a peer outside your community with the identifying details stripped out.
This is not just etiquette. Everybody in your community is quietly assessing what happens to people who disagree with you. Handling one difficult conversation discreetly buys you more trust than a year of welcome messages.
Do this this week
Open the draft you have been avoiding. You know the one.
Delete everything except the actual answer. Put it in the first sentence.
Add one honest reason. Delete the other four.
Remove every sorry after the first, plus every "unfortunately," "I am afraid," and "just."
Add one warm sentence at the end that does not reopen the decision.
Then send it. It will be about a fifth the length of the version you were writing, it will be considerably kinder, and you are going to feel astonishingly light for the rest of the afternoon. That feeling is the whole reason to learn this, and it gets easier every single time.