Every Piece Needs a Reason to Exist
Open most companies' content calendars and you'll find a grid before you find a reason. Tuesday's slot gets a blog post because Tuesday has a slot, not because anyone identified something worth telling a reader on a Tuesday. That's how you end up with a year of adequate, forgettable writing that technically fulfilled a plan.
The question that should kill more drafts than it does
Before a piece gets written, someone should be able to answer: what does a reader know, believe, or do differently after this that they didn't before? "Raise awareness" doesn't count — it's the answer you give when there isn't a real one. A piece that can't clear that bar shouldn't get written just because the calendar has room for it.
Why this is harder than it sounds
Killing a scheduled piece feels like falling behind, even when it's the right call. The instinct to protect the plan is strong, and it's exactly backwards — the plan exists to serve the reader, not the other way around. The teams that write the least forgettable content are usually the ones most willing to leave a slot empty.
What we actually do differently
Every piece on our own calendar has to survive one question before it gets a deadline: if we skipped this one, would anyone notice, and would that be bad? If the honest answer is "no," we use the slot for something else, or we don't fill it. That discipline is most of what separates a newsletter people open from one they've learned to skip.
