Three Frameworks for Newsletter Writing: Format, Flexibility, and Reader Feedback — Ship30for30
Craft email (Mar 21, 2026) presenting three frameworks for newsletter writers. Despite the sales wrapper, the three frameworks are concrete and opinionated — particularly the controversial “70% formatting” claim.
Framework 1: No Single Correct Newsletter Format
Outliers defy every best practice. Short newsletters work, and so do long ones. Stories work, and so does pure data. The warning: do not cherry-pick 1-2 successful writers and extract sweeping conclusions from their individual circumstances. The only metric that matters is whether readers are receiving value.
Framework 2: 70% Formatting, 30% Content
The most actionable claim in the email. Cole (5,000+ articles published) argues formatting is the dominant factor in newsletter success. A well-formatted piece with mediocre content outperforms brilliant content in a wall-of-text format because readers skim before they read. Three formatting priorities: make it visually appealing, visually organized, and visually easy to skim. If readers cannot extract value at a glance, the quality of the underlying content becomes irrelevant.
This is a strong version of the “readability beats writing quality” argument. It aligns with the CopyThat principle that friction kills engagement before craft can save it.
Framework 3: You Do Not Know What Your Readers Want
Writers either (a) assume they know and get humbled, or (b) assume they cannot know and never start. Both are wrong. Every prolific creator discovered what their readers wanted by writing, not by planning. The more they wrote, the more they learned, the better their writing got, the more readers they attracted. The advice: stop waiting to have it “perfectly planned out” and start publishing.
Takeaway for Sanity Check
The 70/30 formatting claim is the highest-signal idea here. It reframes newsletter quality away from prose craft and toward visual information architecture — headers, whitespace, bullet structure, scannable hierarchy. Worth testing against Sanity Check’s own formatting patterns.