Against the Content Calendar
The content calendar was supposed to be a planning tool. For a lot of teams it's become the plan itself — a grid of dates that has to be filled regardless of whether anything worth publishing is actually ready on any given date. That's backwards, and readers can tell.
Readers can smell a filled slot
A piece written because a date arrived, rather than because it was ready, tends to read thin in a specific way — competent sentences with nothing underneath them. Nobody names this out loud in the room where it gets approved, but it's why some newsletters get opened every time and others get skimmed, then eventually filtered to a folder nobody checks.
The cadence question, answered honestly
"How often should we publish" is usually the wrong first question. The right one is "how often do we actually have something worth a reader's five minutes," and then building the cadence around that answer, even if it's less impressive-looking on a slide. A monthly letter that's always worth opening beats a weekly one people learn to scroll past.
What changes in practice
We plan themes and deadlines loosely, and we protect the right to miss one if the piece isn't there yet. That costs us a little predictability. It's bought us a subscriber list that still opens the email — which was the actual point of having a newsletter in the first place, not the calendar that produces it.
