Building a newsletter people can use

What I'm trying

I'm building a newsletter designed around utility rather than publishing frequency. The objective is to take information that people within a specific profession need to monitor and reduce the work required to process and use it. The basic process is:

Monitor → filter → explain → make actionable → distribute

This follows what Seth Godin calls permission marketing: earning the right to keep showing up by being anticipated, personal, and relevant, not by interrupting.

Right now, the newsletter covers information relevant to the day-to-day work of the target profession. The important part is not simply summarizing that information. Where possible, I'm turning it into something the reader can use directly in their work.

How I'm doing it

Step 1 — Define the information scope

The newsletter has a narrow editorial scope. I'm monitoring categories that can materially affect the reader's work, such as:

• Regulatory changes
• Legal developments
• Social or employment matters
• Deadlines
• Operational changes
• Relevant industry developments

The scope is defined by the profession rather than by what happens to be interesting that month.

Step 2 — Filter

I'm not trying to provide a comprehensive news feed. The filtering itself is part of the product. For each potential item, I ask:

• Is this relevant to the target reader?
• Does it change anything?
• Is there an action required?
• Is there something their clients need to know?

If the answer is no, it doesn't need to be included.

Step 3 — Provide context

For each selected item, the objective is to answer a small number of practical questions:

What changed? Who is affected? What needs to be done? When does it matter?

This should reduce the amount of additional research required by the reader.

Step 4 — Make parts of the newsletter reusable

Some information doesn't stop with the professional receiving the newsletter. They may need to communicate it to their own clients. For relevant items, I'm therefore including a ready-to-use communication block. The workflow becomes:

Read → understand → copy → adapt → send

The reader can modify the wording if needed, but doesn't have to start from a blank page. This is the part I'm particularly interested in. The newsletter isn't only delivering information. It's potentially removing a small recurring task.

Step 5 — Keep the cadence appropriate to the use case

I'm not optimizing for maximum publishing frequency. The current cadence is monthly. The newsletter should arrive often enough to remain useful, but not so often that creating another edition becomes the objective in itself. If there isn't enough useful information, there is no reason to artificially fill the space.

Step 6 — Look beyond opens and clicks

Standard newsletter metrics remain useful, but they don't capture the full picture. I'm also interested in signals such as:

• Replies
• Forwarding
• Copy usage
• Reader questions
• Requests for additional topics
• People returning to previous editions
• Resources being shared internally or with clients

These may provide better evidence of utility than attention alone.