Systems Note: Make the Draft Reviewable

Published: 2026-06-15 · Author: Tony Easterling

Publishing gets harder when every issue starts from an empty page. The goal is not to automate a voice into existence; it is to make the first useful version easy to review.

The system I am building

The newsletter workflow gathers current source material, creates a structured draft, and stops there. The draft is separate from publication. It can be checked, edited, approved, and only then added to the public archive.

That separation matters. It turns automation into a handoff rather than a black box. The boring collection and formatting work gets lighter, while the editorial decision stays visible.

Why it matters

Reviewable work is easier to improve than invisible work. A clear draft gives me something concrete to test against the actual projects, product pages, and recent releases. It also makes duplicate publication easier to prevent because each stage has a recognizable state.

Lesson learned

The useful question is not “can this be automated?” It is “where should a person still be able to see and steer the result?” A small approval gate protects quality without bringing back manual busywork.