Why internal newsletters fail (and the one fix)

Most internal newsletters fail for the same reason: they're written to inform when they should be written to be read. Those are different jobs, and almost nobody tells you that when the newsletter lands on your desk.

An informing newsletter is a noticeboard — everything leadership wants pushed out, dumped in one place. It's complete, it's dutiful, and nobody opens it twice. A read newsletter earns the next open. It's edited down to what the reader actually cares about, it has a recognisable shape, and it respects their time.

That distinction sounds small. It's the whole game. Every failure mode below is what happens when "inform" quietly wins.

The four ways internal newsletters die

Yours is probably showing symptoms of at least one. That's fine — they're all fixable, and they all trace back to the same root cause.

The noticeboard. Every department gets a slot because every department asked for one. Finance's reminder about expense codes sits at the same length and weight as the product launch. Nothing is chosen, so nothing stands out, so readers learn there's no reward for reading. Picture a 60-person SaaS company where the monthly email runs to fourteen items because saying no to a head of department feels political. Readers don't file a complaint. They just stop opening, one by one, and nobody tells you.

The megaphone. Every item is leadership talking downwards — strategy updates, policy changes, reminders to complete training. No people, no wins, no faces. It reads like being talked at in a meeting you can't leave. The sections colleagues actually read — new starters, recognition, the human stuff — never made it in, because nobody senior asked for them.

The essay. Each item gets three earnest paragraphs because the person who submitted it wrote three earnest paragraphs and cutting felt rude. Now think about a 140-person clinic group: most staff don't sit at a desk. They're reading on a phone between patients, standing up, in about ninety seconds. Three paragraphs on the new rota policy doesn't survive that. One clear line with a link does.

The ghost. It launched with energy, shipped four issues, went quiet during a busy month, and now restarting feels embarrassing. This one is usually a production problem, not a content problem — the newsletter took four hours an issue, so it was the first thing dropped. (Later in the Playbook there's a 90-minute routine that fixes exactly this.)

Noticeboard, megaphone, essay, ghost. Four symptoms, one disease: the newsletter serves the senders, not the readers.

The fix: edit for the reader, not the sender

Before anything goes in, ask one question:

"Would the person receiving this care?"

If the honest answer is no, it doesn't go in — or it goes in as a one-line summary with a link, not three paragraphs. That's the entire fix. Everything else in this Playbook is technique layered on top of it.

This is uncomfortable, because it means leaving things out that someone senior asked you to include. The skill of internal comms is saying "we'll link to it" instead of "we'll feature it." Here's the script, because you'll need it this month:

"That's definitely going in — I'll run it as one line with a link so it doesn't get lost in the middle of a long issue. The full detail is one click away for anyone who needs it."

Notice what that does. Nobody gets told no. The item still ships. But your reader gets an issue where every full-length item earned its place — and the sender usually thanks you, because a sharp line in a read newsletter beats three paragraphs in an ignored one.

The subject line tells the same story. "March Update from Head Office" is a noticeboard announcing itself. "New starters, the pricing change, and who fixed the office wifi" is an edited issue announcing itself. Same company, same month, same material — one of them gets opened.

"Nobody reads it" is usually the wrong diagnosis

When an internal newsletter is "failing," the open rate is rarely the smoking gun. Internal opens typically land somewhere between 60 and 75% when the email comes from a name people trust — colleagues do open things from their own company. The failure is quieter: they open, skim four seconds, find nothing for them, close. Opens hold up for months while actual readership is already gone. Then opens sag too, and by the time the number looks bad, the habit of ignoring you is well set.

Which is why clicks tell you more than opens ever will. A click is a reader voting for a specific item; an open is often just a reflex. If you're sending with the app that came with this Playbook, open and click tracking is already baked into the HTML it exports, even sending from your own Outlook or Gmail — so from your very next issue you can see which items got votes and which got scrolled past. That's your Care column, measured.

A simple test to run this week

Open your last three issues. Go item by item and mark each one Care or Don't care — judged from the reader's seat, not yours. Be honest: "the leadership team wanted this in" is not the same as "a reader wanted this in."

Then count:

• A third or more marked "Don't care"? That's your open-rate problem expressed as one number. You don't have a writing problem; you have an editing problem, which is much easier to fix.
• Everything full-length? You're not editing at all yet — you're forwarding. The one-line-with-a-link move is your biggest single upgrade.
• No people content anywhere? You've built a megaphone. The most-read sections in almost any internal newsletter are the human ones, and you're shipping issues without them.

Don't fix anything yet. Just get the number. The rest of the Playbook — the one-job principle in the next lesson, the content engine, the people sections, the production routine — is how you fill the Care column reliably, every issue, without it eating your week.

One number, from three old issues, in fifteen minutes. That's the whole assignment. It's the least glamorous exercise in this course and the one most people quote back afterwards — because it's the moment the problem stops being "people don't read newsletters" and becomes "we were sending things nobody asked for." One of those is out of your control. The other one, you can fix by Thursday.