Newsletter Writing Rules

A newsletter is opened or archived based on two lines of text — the subject line and the preview text — before the reader ever sees the body. Write those two lines with more care than any single sentence inside the email, because nothing inside the email matters if those two lines don't earn the open.

Subject line discipline

• Create curiosity that has a real payoff inside the email — a specific claim, number, or open loop the body actually resolves. Curiosity with no payoff trains readers to stop opening; curiosity that delivers trains them to keep opening.
• Keep subject lines short enough to survive mobile truncation — roughly 40–50 characters is safe; anything longer risks getting cut mid-thought on a phone screen, which reads worse than being short.
• Avoid spam-trigger patterns: ALL CAPS, excessive punctuation ("!!!"), "FREE", "Act now", and heavy emoji stacking. These lower deliverability and read as low-trust even to inboxes that don't filter them.
• Be specific rather than clever for its own sake — "3 mistakes that broke our onboarding" beats "You won't believe what happened" every time; specificity is what makes curiosity credible instead of empty.

Preview text is a second subject line

• Never leave preview text to default to the email's first line ("View this email in your browser...") — write it deliberately as a continuation or second angle on the subject line, since most inbox clients show both together.
• Use the preview text to add the detail the subject line didn't have room for, not to repeat it. Redundant preview text wastes half the available real estate before the open.

One job per email

• Decide the single primary action or takeaway before drafting, and build the whole email around it. An email trying to sell a product, announce a feature, and share a blog post all at once dilutes all three and moves the reader toward none.
• Everything that isn't the primary job goes below the fold or gets cut. Secondary content is fine as a P.S. or a small footer link, not as a competing headline.

Scannable structure

• Break the body into short sections with clear visual separation (headers, whitespace, occasional bold) — a reader should be able to skim the whole email in five seconds and still get the gist.
• Keep paragraphs to two or three sentences. Email is read on a phone, often in a spare moment; dense paragraphs get skipped, not read carefully.
• Put the most important point first, not buried after three paragraphs of preamble — readers who don't finish the email should still have gotten the point.

Voice: personal over corporate

• Write from a person, in first person, even for a company newsletter — "we shipped this because..." reads as more trustworthy than "We are pleased to announce..." Corporate voice is the single biggest reason newsletters feel like they're being talked at rather than talked to.
• Let some personality and specific detail through (a real anecdote, an actual number, an opinion) — a newsletter that could have been written by any company in the category isn't earning its subscriber's attention.

Send rhythm

• Promise a frequency the sender can actually sustain, and hold it — consistency (same day, same rough interval) builds more trust than sending often. A newsletter that goes silent for two months and then sends three issues in a week teaches readers to stop expecting anything and to stop opening.
• If frequency has to change, say so explicitly in an issue rather than silently drifting — readers tolerate a stated change far better than an unexplained one.

Link discipline

• Use one primary link per email tied to the primary job, repeated at most two or three times (top, mid, and a closing CTA) rather than scattering many different links that split attention and click-through data.
• Make link text describe the destination ("read the full breakdown") rather than generic text ("click here") — both for scannability and because vague link text reads as low effort.

Unsubscribe-friendliness as trust

• Keep the unsubscribe link visible and one click to complete — no forced login, no "are you sure" gauntlet, no hidden placement. A newsletter that makes leaving hard doesn't retain readers, it just makes them report it as spam instead, which damages deliverability for everyone on the list.
• Treat a clean, easy unsubscribe as a trust signal, not a loss to prevent — readers are more willing to open aggressively-curious subject lines from a sender they trust to let them leave easily.

What makes people archive on sight

• A subject line that's vague, over-familiar in tone from an unfamiliar sender, or that has burned the reader before with a payoff-free open.
• A sender name/from-line that doesn't clearly identify who this is — readers decide to open largely from the from-line and subject line together, not the subject line alone.
• Arriving off the promised rhythm, either much more often than expected (spam-like) or after a long unexplained silence (irrelevance).