Blunt vs clear: why short writing still confuses people

Blunt measures what you took out. Clear measures what the reader ends up with. They come apart constantly, which is why the shortest message in a thread so often causes the longest thread.

Most people file both words under the same heading, somewhere near "at least it isn't waffle". Only one of them is scored on the other person's screen.

What bluntness actually measures

Bluntness is a property of your text: how much you cut, and how hard the sentence lands.

You can grade it alone, at your desk, with no reader present. Count the softeners. Notice whether the verb shows up in the first four words.

Clarity cannot be graded that way. It happens at the far end of the wire or it does not happen at all, and the writer is the worst-placed person in the conversation to judge it. You already know which invoice you mean, and which of the two things your team named with the same word.

So a message can be extremely blunt and completely opaque. It usually is.

The short message that starts the long thread

The blunt version costs a round trip, because the parts it deletes are the parts the reader needs in order to move.

"This isn't ready." Honest and useless. The reader now has to ask what is missing and when you want it back, and by the time they have composed that question your attention has gone somewhere else entirely.

The clear version is barely longer. "Not ready to send. The figures on page two came from the old export, can you refresh them and resend today?" Same verdict, same spine, no return trip.

Blunt messages tend to delete a predictable set of things:

• The reason, which is the part that ends the argument before it starts.
• The ask, so the reader cannot tell whether they are being informed or assigned.
• The date, which is what turns an opinion into a plan.
• Any sign of where they stand with you, which they will now invent on their own.

None of that gets dropped on purpose. It was in your head, it felt obvious, and obvious is not a property that travels.

Clear writing is usually longer than blunt writing

Clarity costs words. A few, not many, and the people proudest of their brevity are exactly the ones who will not spend them.

Here is the part worth arguing about: most workplace bluntness is laziness in a good jacket. Cutting is easy and feels rigorous. Working out what this particular reader is missing, and then writing that one sentence, is a pass you have to be bothered to do.

Skipping the pass does not remove the work. It moves the work to the reader, where it costs more, because now two people are doing it and one of them is guessing.

Count round trips, not words. A message that ends the topic wins even when it is the longer one, and especially when the short version would have come back twice and finished in somebody's calendar.

When blunt is the right instrument

Bluntness earns its place when being misread costs more than being disliked.

Some moments need the box dropped on the table:

• Something is on fire and the next sentence has to be an instruction.
• You sent the gentle version twice and it was filed as a suggestion.
• A boundary is being tested, and a hedge is an invitation to test it again.
• Someone asked for your verdict and wants the verdict, not the tour.

Notice what those have in common. The context is already shared, so a short sentence can lean on it.

Bluntness borrows clarity from what the reader already knows. When the shared context is thinner than you assumed, the loan defaults, publicly, in a thread other people are reading.

That is why blunt travels badly outward. A teammate of two years can decode "no, not like that" without effort. Someone three teams away fills the gap with the least generous reading available, which is also how bad news arrives as blame when you meant it as a fact.

How to check whether you were clear

Since you cannot read your own message as a stranger, check it against the reply you expect it to produce.

Read what you wrote, then predict the next message in the thread. If your honest prediction is a question, you have found the sentence you left out. Put it in and predict again.

The checks I actually run:

• Could the reader repeat your decision to someone else in one sentence, without reopening the thread?
• Do they know whether they have to do something, and by when?
• Does it still make sense to a person who was not in the meeting you are referring to?

The missing sentence usually lives at the end, which is why the way a message closes decides whether anything happens after it.

I built Unvent partly because my own drafts fail that test in one direction, every time. My head produces the blunt version, and I notice at the moment of sending, which is the worst moment to start rewriting. Taking the Direct rewrite keeps the verdict I meant and puts back the line that tells the person what happens next.

The trouble with "I'm just direct"

People who introduce themselves as blunt are usually describing how they like to feel while writing. The result at the other end went unmeasured.

The phrase never appears after a message that worked. It shows up afterwards, as an explanation, usually to a third party.

The honest test is what happens downstream. Did the thing get fixed, and did anyone have to hold a meeting about your tone? Directness that has curdled into a personality creates a small unpaid job for whoever sits nearest you, translating your sentences into ones the room can use.

In writing, the sting also outlives the point. Speech evaporates. A sentence sits in the scrollback and gets reread at midnight by someone who missed the friendly part of the conversation, so price that in before you decide that feedback is best served bare.

The edit that fixes a blunt message is almost never a softener. It is a fact: the reason, the ask, or the date you left out. Put one of them back and the message stops sounding cold, because most coldness in writing is the sound of information that went missing on the way.