Foundations
Define the one job your newsletter does
6 min read
A newsletter with no defined job becomes a dumping ground. Not because anyone decides it should — because nobody decides it shouldn't. Without a stated purpose, there's no grounds for saying no to anything, so everything goes in, and you're back to the noticeboard problem from lesson one within a quarter.
Here's the thing nobody tells the accidental comms owner: every editorial argument you will ever have — what leads, what gets cut, whether the CFO's reminder deserves three paragraphs — is really an argument about what the newsletter is for. Have that argument once, on purpose, and you never have to have it again item by item.
So: define the job in one sentence, and every editorial decision gets easier. This lesson is how.
The four jobs (pick one primary)
Almost every internal newsletter worth sending is doing one of these:
- Alignment — everyone knows what the company is focused on this quarter, and who's driving it. The lead item is always the priority, the progress, the decision. This is the natural job for a company that's growing fast or changing direction, where the real risk is fifty people rowing in forty directions.
- Culture — distributed people feel connected to the team and its wins. New starters, recognition, the human stuff leads; strategy rides in the back. The natural job for remote and hybrid teams, where the newsletter is doing work the kitchen used to do.
- Operations — people know what's changing (policy, tools, process, rota) and what to do about it. Unglamorous and absolutely vital in shift-based or regulated workplaces, where a missed change isn't an inconvenience, it's an incident.
- Recognition — good work gets seen by the whole company, not just one manager. The rarest primary job, and a strong choice where the actual problem is that effort disappears into silos.
You can serve secondary jobs — a culture newsletter can carry an operations item, and should. But one job leads, and when you're unsure whether something belongs, you ask: does this serve the primary job? If it only serves a secondary one, it gets a line and a link, not a feature slot.
What you can't do is weight all four equally. A newsletter that's 25% each of everything has no shape, and a newsletter with no shape is a newsletter nobody can learn to skim — which means nobody learns to read it either.
How to choose when they all sound important
They all sound important. That's the trap. Choose by asking what your company would actually lose without the newsletter — not what it would be nice to have.
A 60-person SaaS company, remote-first, hiring fast: nobody's missing policy updates (there barely are any), but new people are joining teams they've never met and shipping into silence. The thing that's genuinely missing is connection. Job: culture.
A 140-person clinic group across five sites: staff feel plenty of connection inside their own site. What actually goes wrong is a rota change or a protocol update reaching four sites out of five. Job: operations — and a culture section riding along in every issue, because morale still matters, it just doesn't lead.
Two quick cross-checks before you commit:
- Ask both directions. What would leadership say the job is? What would a reader say? If those answers differ — and they usually do — you've found exactly where your editorial fights will come from. The right answer is usually closer to the reader's version than the sender's.
- Look at what already gets read. If you have past issues with any tracking on them, the clicks are a vote on what people want this thing to be. Readers voting overwhelmingly for people content while you lead with strategy is a job mismatch, measured.
Wrong-but-decided beats undecided, by the way. You can change the job in six months with one sentence in one issue. You can't retro-fit a spine into six months of dumping ground.
Write your sentence
One sentence, this shape:
"Our newsletter exists so that [who] [does/feels/knows what] every [cadence]."
For the SaaS company: "Our newsletter exists so that every employee feels connected to what the rest of the team is doing and shipping, every two weeks."
For the clinic group: "Our newsletter exists so that every member of staff, at every site, knows what's changing and what to do about it, every Monday."
Notice each sentence quietly writes your subject lines for you. The culture one produces "Three new faces, a shipped feature, and Priya's onboarding fix." The operations one produces "This week: new referral form, car park closure dates, flu jab clinics." Different jobs, different newsletters — visibly, from the inbox.
Keep it to one sentence. If yours has an "and also" in it, you haven't chosen yet.
Put the sentence to work
A sentence in your head is a wish. Deploy it:
- Pin it where you plan. Top of your content doc, or on your comms calendar in the Playbook hub — wherever you look before every issue. It's the filter that keeps the noticeboard from creeping back.
- Tell your stakeholders. Send it to your manager and the people who feed you content: "Here's the job of the newsletter — this is how I'll be deciding what leads and what gets a link." Now every future no is impersonal. You're not rejecting their item; the sentence is.
- Use it at the moment of collection. If you're gathering updates through the app's submission form, the sentence tells you what to ask for. A culture newsletter prompts "share a win or a shout-out"; an operations one prompts "what's changing that people need to know?" You get better raw material because you asked a better question.
- Re-read it quarterly. Jobs drift. The startup that needed culture at 60 people may need alignment at 150. Changing the sentence deliberately is strategy; letting it blur is how dumping grounds happen.
This week
Write your sentence. Fill in the three blanks, out loud if it helps, and don't move on until it survives the "and also" check.
Then send it to your manager with one line: "This is the job I'm running the newsletter to do — shout if you'd pick a different one." Five minutes of your time, one small moment of exposure. What you get back is the single most useful thing an accidental comms owner can own: a mandate. When the noticeboard requests start arriving — and they will — you won't be defending your taste. You'll be pointing at a sentence your boss already agreed to.
Enjoying this?
This is a free preview. Get the full course, the comms calendar and templates.
Get the Playbook