The best tweak to my content system this week wasn't a tool. It was a Sunday review.
I've spent weeks building automation: a Notion calendar that feeds a pipeline which posts to X daily, LinkedIn three times a week, and mirrors to Bluesky. The machine works — a thread assembled, posted, and mirrored itself while I watched, and I didn't touch a thing.
Then I found the bug. In a rebuild, the workflow had silently reset from Vancouver time to UTC. My "9 AM" posts were scheduled for 2 AM. Nothing in the logs screamed. The only reason I caught it was a deliberate Sunday read-through of the whole system.
So I made that permanent: every Sunday I spend 20 minutes reviewing next week's queue — the X posts, the LinkedIn posts, the newsletter anchor. I edit what's off-key, approve what's solid, and the week runs itself.
The lesson: automation doesn't remove review; it moves it. The machine handles the assembly line. A human still owns the taste, the tone, and the boundary between "ready" and "not a chance."
What shipped this week: one 6-tweet thread live on X and mirrored to Bluesky, 20 content rows queued across two weeks, a review ritual that takes less time than a coffee, and a queue that fills itself every Sunday morning.
Tools I leaned on: n8n (the orchestrator), Notion (the queue), the X API and Bluesky's app password (the senders), and a cron — still the most underrated tool in the stack.
Next week: the full teardown of the pipeline that runs this newsletter — every node, one by one, with the numbers.