Skip to main content

Format: Newsletter

Purpose​

Use for recurring updates that build trust through clarity and consistency.

Canonical Structure​

  1. One-sentence issue promise
  2. Main insight blocks (1-3)
  3. Curated links or resources (optional)
  4. Closing action or reflection prompt

Rules​

Rule: One Theme Per Issue​

Description: Keep each issue centered on one core idea. Negative example: One issue mixing hiring, nutrition, and product analytics. Positive example: Entire issue focused on "how to write sharper intros."

Rule: Treat the Subject Line as the Headline​

Description: Subject line should clearly answer who this is for, what it covers, and why it is worth opening. Negative example: Clever subject line with no indication of topic or payoff. Positive example: Specific subject line naming the problem and the practical outcome.

Rule: Keep Subject and Opening in Promise Lockstep​

Description: First line should continue the exact tension or promise that earned the open. Negative example: Subject line promises one problem, opening paragraph pivots to unrelated updates. Positive example: Subject line names a blocked outcome, and line one immediately deepens that same problem.

Rule: Front-Load Value​

Description: Deliver the best point before any secondary material. Negative example: 300 words of housekeeping before insight. Positive example: Key lesson in the opening, logistics near the end.

Rule: Add a Lightweight Trust Cue Early​

Description: In the intro, include one concise reason the reader should trust this issue. Negative example: Jumping into strong claims with no context or evidence basis. Positive example: One line referencing direct experience, tested practice, or reliable source context.

Rule: Use One-Sentence Block Openers​

Description: Start each major block with a single sentence that states its value. Negative example: Opening blocks with soft preambles and delayed point. Positive example: "This week's core lesson: name the reader outcome in line one."

Rule: Use Consequence-Before-Reveal Sparingly​

Description: When useful, describe the cost of a hidden mistake before revealing the fix. Negative example: Revealing the key lesson in the first sentence, then dragging through setup. Positive example: Briefly naming what goes wrong first, then revealing the specific correction within the next few lines.

Rule: Build a 3-Layer Scan Ladder​

Description: Readers should grasp the issue by skimming the subject line, then subheads, then first sentence of each section. Negative example: Strong subject line but vague subheads and generic section openers. Positive example: Subject line sets promise, subheads map the journey, first lines state each takeaway.

Rule: Format Multi-Point Sections as Lists​

Description: Use bullets or numbering when offering multiple takeaways. Negative example: Dense paragraph containing all lessons inline. Positive example: Three concise bullets under a short heading.

Rule: Use List Sandwiches for Dense Sections​

Description: For list-heavy sections, use one declarative setup sentence, then bullets, then one closing sentence. Negative example: Bullet list dropped with no setup or interpretation. Positive example: One-line context, concise bullets, one-line takeaway.

Rule: Maintain Predictable Section Rhythm​

Description: Repeated structure helps readers orient quickly. Negative example: Different random structure every issue. Positive example: Promise -> 3 lessons -> closing action each issue.

Rule: Keep CTA Singular​

Description: Ask for one action only. Negative example: Follow, share, buy, reply, and fill a form in one closing block. Positive example: "Reply with your current draft opener and I will send one edit suggestion."

Rule: Use Turning-Point Language From Real Readers​

Description: Incorporate direct phrasing from reader/customer moments to improve resonance and specificity. Negative example: Generic emotional claims written from assumptions. Positive example: One quoted turning-point sentence that matches the issue's lesson and audience stage.

Rule: Skip Redundant Conclusions​

Description: If the ending only repeats earlier points, replace it with one useful next action. Negative example: Final paragraph restating the whole issue without adding value. Positive example: Direct readers to one relevant resource, reply prompt, or next implementation step.

Best-Fit Content Intent​

  • roundup-curation
  • announcement
  • how-to-guide
  • case-study
  • cornerstone