Writing replies that add something

A lot of replies say one of three things: nice post, I agree, you’re wrong. All three are honest. None of them gives the next reader a reason to stop.

A good reply is a very small post with one job. It leaves the conversation holding something it did not hold a minute ago: a case, a limit, a better question. Here is how we would write one.

Find what the page is missing

Read the whole post first. Yes, all of it. Plenty of bad replies answer a sentence the writer already dealt with two paragraphs down.

Then read the replies already there. If someone has made your point, you have three options: add to it, sharpen it, or leave it alone. Leaving it alone is underrated.

Now ask one question: what would a reader know after my reply that they do not know now? If the answer is “that I liked this” or “that I have an opinion”, keep thinking. If you can name the thing in five words, you have a reply. Everything after this is just how to say it.

Five things worth adding

Take a made-up post to work with. It says: “Stop outlining short posts. The outline takes longer than the post.” Here is what a useful reply could bring to it.

• A case. “Tried this on a how-to last month. Fine for opinions, but I lost a step in the instructions and only spotted it after posting.”
• A limit. “True under 150 words. Past that, I need at least a list of the points or I repeat myself.”
• A question the writer can actually answer. “Does this hold for a thread, where the order matters more?”
• A source. A link to the page where you read the thing, plus one line on why it matters here. Bare links read like ads.
• A next step. “If you skip the outline, try writing the last line first. It gives you the same sense of direction.”

Notice what those have in common. Each one could be quoted on its own and still be worth reading. Each one also gives the writer something to answer, which is how a thread keeps going without anyone having to beg for engagement.

Plain thanks are fine too, by the way. Just make them specific. “The line about losing a step made me reread my last draft” tells the writer far more than “great post” ever will.

Point at the line you mean

Replies get read out of order. Someone lands on a post weeks later, scrolls straight to the bottom and finds “this is so wrong”. Wrong about what?

So name your target. A few quoted words do it:

“The outline takes longer than the post”: only if you outline in full sentences. Three words per point takes about a minute.

That reply makes sense to a stranger. It also survives delay, which matters here: on ReedSpot, guest replies wait for a moderator before they appear, so other replies may land while yours is in the queue. “Like the person above said” can point at nobody by the time it goes up. A quoted phrase still points at the right thing.

Same goes for vague pronouns. “This” and “that” are fine in a chat, where everyone can see what you are looking at. In a reply, swap them for the actual noun.

Disagree with the claim

Our community guidelines put it in eight words: “Reply to the post, not to the person.” Most heated threads go wrong right there. Compare:

• At the person: “You clearly haven’t written anything longer than a caption.”
• At the claim: “This breaks for me on anything with steps. If I skip the plan, I skip a step.”

The second is a stronger attack on the idea, and it costs nobody any face. The writer can answer it without defending their whole career first.

A shape that works almost every time:

1. Say what you accept. One clause is enough. “Agreed for opinion posts.”
2. Say where it breaks. Be exact about the case.
3. Say why. Your reason, or your example.

Then drop the armour. Skip “with respect”, “no offence” and “just my two cents”. Those phrases warn the reader that something rude is coming, or apologise for a point you should simply make. And watch your certainty: if you saw something happen once, say once. “Worked for me on one how-to” is a smaller claim than “this never works”, and much harder to knock down.

Want to fire one off while annoyed? Write it, then wait a few minutes. Annoyance is a decent reason to start a reply and a poor reason to send it.

One point, then stop

Everything we said about a short post that stands on its own applies here, with less room. One point, in the first line. A reason or an example. Done.

Cut the warm-up:

• Before: “Interesting read, lots to think about here, and I can see where you’re coming from, but I do wonder whether…”
• After: “Does this hold for how-tos?”

Cut the sign-off too. “Anyway, that’s just me” lets the air out of a good reply.

Two points? Pick the better one. Still itching about the other? That itch may be telling you something. A reply that keeps growing past a couple of short paragraphs is often your next post in disguise, and growing a short note into an article covers what to do with it. If you do write it up, drop a short reply under the original with a link. The writer gets the credit for starting it, and readers get somewhere to go.

Check it before you press Reply

Thirty seconds, four questions:

1. What does this add? Name it. If you can’t, don’t send it.
2. Would a stranger follow it? Read it without the post above it. Does it still say what it is about?
3. Could the writer answer it? “Why would anyone think this?” is a jab with a question mark. “What made you drop outlines?” has an answer.
4. Would you sign it? Your name goes on it. Say it the way you would across a table.

Take that last one seriously on ReedSpot. A reply takes only a name and a comment, with no account, so you have no edit button afterwards. Fixing or removing one means a request through the contact page. Typos are forgivable. A sentence you wish you hadn’t written takes longer to undo than it took to type.

And if yours doesn’t show up straight away, it hasn’t been lost. Moderators read guest replies before they go up, and the help page explains what happens while one waits. No need to send it twice.

Try it on the next post that makes you want to type something. Before you do, finish this sentence: “The thing this page is missing is…”