July 29, 2026 Jo Builds 5 min read

Why your long messages get skimmed

Hand-colored engraving of an Eleus butterfly, Drury 1837

Long messages get skimmed because the reader decides how much to read before they read any of it. They clock the size of the block first, and a big one gets filed under later. Later usually means never. So the point you buried in the middle never gets seen, and the reader is already gone by the second line.

I used to think a long message showed effort, and effort would be rewarded. It is not. The reader is not grading you. They are clearing a backlog, and your message is one of forty small things asking for a piece of their attention.

Nobody reads your message the way you wrote it. You wrote it top to bottom, once, calmly. They read the first line, whatever is bold, and the shape of the paragraphs, in a few seconds, and then decide whether to come back. Most of the time they do not come back.

So the job is not to write less. Some messages genuinely need six paragraphs. The job is to build the message so it survives a skim, so the few seconds a real reader gives it are enough to land your point.

The first line is the only line you can count on

The first line is the one part of your message you can assume gets read, so it has to carry the point by itself. This is not a style preference. It is how the tools show your message before anyone opens it. Gmail prints the opening words of your email as gray preview text right next to the subject, and phone notifications and Slack previews do the same thing: they surface the top of the message and nothing else. Whatever you put first is the version most people will ever see.

So put the thing you need where the preview will catch it. If your message opens with "Can you review the pricing section before the Monday client call?", that ask rides along in every preview and every notification. If it opens with "Hi, hope the week is treating you well, I have been meaning to loop back on a couple of things," the preview shows a warm nothing, and the reader has no reason to tap in.

A few openers reliably waste that line, because not one of them says anything a reader can act on:

This feels blunt while you write it. It does not feel blunt to read. Someone opening a clear first line feels relief, not rudeness, because you already did the work of deciding what mattered.

Bold one thing, or the bolding stops working

Bold works by being rare, so the moment you bold more than one thing it stops pointing anywhere. When a single phrase is bold, a skimming eye lands on it first, which is the whole reason to bold at all. When six phrases are bold, none of them win, and the reader is back to reading everything to find the part that matters, which is the exact chore you were trying to spare them.

So pick the one thing the reader has to act on and bold only that. Maybe it is a deadline. Maybe it is a decision you need from them. Maybe it is the single number the whole message is about. Let it be the only loud thing on the screen, and it will do the work of a paragraph on its own.

White space gives a skimming eye somewhere to land

White space is what lets a reader skim at all, because the gaps between paragraphs are the footholds the eye grabs on the way down. A single dense block has nothing to grab, so the eye slides off it and the message goes unread. Break the same text into short paragraphs with air between them and a reader can catch one piece at a time and still come away with the shape of what you said.

People resist this because splitting one paragraph into three feels like you are dumbing it down. You are not. The words are the same. You have only made them survivable on a small screen, where a wall of text stays a wall no matter how good the sentences are.

Use a list only when the items are really separate

A list only helps when the items are genuinely separate things, and it actively hurts when you chop one argument into bullets to look organized. If the pieces have to be read in order, or each one leans on the last, that is an argument, and arguments belong in sentences. Fake bullets just hand the reader the reassembly work you skipped.

Real list material is anything a reader might act on one at a time or come back to later:

Your reasoning is not list material, and neither is a story you are telling to make a case. Both go flat and choppy the second you bullet them. When I catch myself reaching for bullets to organize a thought, it usually means the thought is not clear yet, and the bullets are hiding that from me.

Write for the reader who is already tired

Write for the tired, half-distracted version of your reader, because that is the person who actually opens the message. The reader with a free hour and full attention is a fantasy you are quietly writing to, and they are not the one holding the phone. Anything that only works for the rested reader is a line you will lose.

The check that finally worked for me is simple. Read only your first line and your one bold phrase, in that order, and nothing else. If those two alone tell the reader what you need and by when, the message will survive. If they do not, no amount of careful writing underneath will save it, because the underneath is exactly what gets skipped.

This is the pass where Unvent earns its keep for me. It takes the draft I already typed and hands the point back to the top, in the same box I was writing in, so the version that goes out leads with what matters instead of the warm-up I wrote to get myself going.

The person who writes the shortest clear version of a hard message is not being lazy. They spent the same effort you can see in the long one. They just spent it before hitting send, instead of asking the reader to spend it after.

Say it in the first line, and mean it

Unvent takes the draft you already wrote and hands the point back to you at the top, so a tired reader gets it on the first pass. It works right in the box you were typing in.

Get Unvent, free on Chrome
u

Jo Builds makes Unvent, a Chrome extension that rewrites whatever you are typing, in place, in the tone you pick. More on the about page.