The week as five sessions instead of seven scrambles. Note what's different in the corner.
There's a chapter in the book I'm writing about the weekly rhythm — how to batch the work so it repeats without willpower. It has a section on burnout. Near the end of that section is a line I wrote months ago, in a confident voice, as advice: take a real day off.
I have not been taking a day off. I've published something every single day since June 29th. Roughly thirty days.
I made the change three days ago. This post is about why it took me that long to follow my own instruction, and what the system underneath it actually is.
The part I did get right: batch by mode, not by post
The instinctive way to blog is one post at a time, start to finish — research it, write it, find the images, format it, publish it, collapse, do it again tomorrow. That's five different kinds of thinking crammed into every day, and switching between kinds of thinking is the most expensive thing a brain does.
So the system batches by mode instead. All the planning happens in one sitting. Drafting happens in drafting sittings. The platform adaptations happen together. Formatting and scheduling happen together. Same total hours, dramatically less friction — a drafting hour flows because I'm never stopping to hunt down an image, and a formatting hour flies because doing five posts is barely longer than doing two once the tools are open and the checklist is running.
Laid out, my week is about five sessions plus a daily check-in:
- A planning session on Saturday, thirty to sixty minutes — next week's plan, slot by slot.
- Two drafting blocks, Monday and Tuesday, a couple of hours each.
- An adaptation block on Wednesday, where each post becomes its three platform versions.
- A mechanics block on Thursday — formatting, scheduling into the right time windows, updating the tracker.
- Ten or fifteen minutes a day of tending: answering comments, glancing at stats, adding anything new to the idea file.
The structural trick is that by Thursday everything is scheduled. The platforms publish on their own clocks and I go live my life. That part has genuinely worked.
The part I got wrong
Here's the thing about a system that works: it makes overwork feel effortless.
Because the scheduling is done early, and because each individual day is manageable, I never hit the wall that would have told me to stop. There was no dramatic exhausting night. There was just thirty days in a row, and a quiet background hum of I could probably also do Sunday.
I only noticed because I sat down and asked a plain question — would dropping to six days actually hurt anything? — and the honest answer came back no. Search platforms reward a rhythm you don't break far more than they reward one extra post. I'd already published more than the target I set for the first month. Nothing was gained by the seventh day except the erosion of the person doing it.
So Sunday is off now. And the condition I've put on it, which I think matters more than the decision itself: it isn't a catch-up day. The moment it becomes the day where the thing that slipped on Tuesday gets finished, I've just renamed the seven-day week.
I want to be honest that I don't fully trust myself on this yet. It's been three days.
The other defense: a buffer
The rhythm I described runs hand-to-mouth — this week's sessions feed this week's slots. That works until life doesn't cooperate. A visit, a flu, a genuinely empty news week.
So the answer is banking evergreen posts — the explainer and personal material that doesn't expire — whenever the energy runs ahead of the calendar. Two or three per platform is enough to absorb a bad week without breaking the streak. News posts can't be buffered, which is exactly why the week mixes fixed slots with news slots: a bad week can quietly become an evergreen week and nobody reading notices anything except a slightly quieter Tuesday.
I started this properly last week. Next Saturday's post is already written, sitting in a folder waiting for one link to be pasted in. That is a genuinely new feeling and I recommend it.
And it got tested faster than I expected — the same week I wrote this. Two news posts came out of the schedule, and the pre-written ones slid straight into the gaps.
On publishing into silence
The chapter says the dangerous weeks aren't the busy ones — they're the quiet ones. Months two and three, when the system runs perfectly and almost nobody reads. I'm in that stretch now. The numbers are still small enough that I'm not going to dress them up as a trend.
The defense I've found most useful is counting what I actually control. Posts published. Weeks unbroken. How many drafts are banked. Those obey effort. Views in month two mostly don't. I'll put real numbers on this next week — the first Tuesday of the month is a progress report, and it's going to say whatever it says.
So the confession this week is a small one, but it's the one I've got: I wrote the advice, published it in a chapter, and then took a month to actually take it. I don't think that makes the advice wrong. I think it means advice is easy to write and rhythm is a thing you have to install in a real life, which resists.
Here's my question for you: have you ever built yourself a system that worked so well it let you overdo something — where the efficiency was exactly what hid the problem? I'd like to know it's not just me. Tell me in the comments.
Subscribe if you want to see whether the day off survives contact with a busy week.
Tags: blogging for money, field notes, blogging burnout, weekly blogging schedule, content batching, blogging consistency, miguktv
Comments
Post a Comment