Module 3: Batching
The 2-hour Batch Session that produces a full week of content.
Why Batching Works
Creating one post at a time is the most expensive way to create. Every session has a setup tax: opening the tools, remembering where you left off, getting into the writing headspace, deciding what to write about. That tax runs 15–20 minutes — and you pay it fresh every single time you sit down. Five scattered sessions a week means paying it five times. One batch session means paying it once.
Then there's the switching cost. Your brain doesn't glide between writing a post, answering email, and prepping a call — each switch dumps your mental cache and forces a rebuild. Creators who "squeeze in content between meetings" aren't saving time; they're creating in the most cognitively expensive conditions possible, which is why a single post takes them an hour and feels exhausting.
Batching flips both costs. One 2-hour block, one setup tax, zero switches — and something else happens around minute 40: creative momentum. The first post is the hardest; by the third, you're in flow and the words come faster. Post five takes half the time of post one. Scattered creation never reaches momentum. Batched creation lives in it.
The setup tax
Batching pays the tax once
Build brief
Track your creation for one week: how many sessions, how long each, how many pieces finished? Calculate your real minutes-per-piece. (You'll compare this against batched time in the calculator below.)
Saved
The Batch Session
The Batch Session is one focused 2-hour block that produces a full week of content. Here's the exact protocol. 0:00–0:15 — Prep. Open your swipe file, pick 5 developed ideas (one per weekday, rotating pillars), open your templates. No writing yet — just loading the raw materials. 0:15–1:15 — Draft. Write all five posts fast. Ugly is fine. No editing, no second-guessing, no checking your phone. The rule: forward motion only.
1:15–1:45 — Polish. Now edit all five. Read each aloud once — your ear catches what your eye misses. Fix the hooks first (the first line decides everything), then cut 10% of the words, then check each post against its pillar: does it belong? 1:45–2:00 — Schedule. Load all five into your calendar or scheduler with dates, pillars, and formats noted. Close the laptop. You're done for the week.
The session rules are non-negotiable. Phone on do-not-disturb, in another room. One browser tab. A visible timer counting down — time pressure is a feature, not a bug. And the golden rule: never batch from zero — always batch from the bank. If your idea bank is empty, the session becomes an idea-hunting session wearing a batching costume, and it will feel terrible. Prep (Module 2's review) feeds the session; the session doesn't replace it.
The protocol
The 2-hour batch session
Build brief
When is your 2-hour block? Name the exact day, time, and location. Then list what you'll do to protect it (phone away, door closed, calendar marked busy).
Saved
Batching time-savings calculator
Play with the numbers — everything updates live.
Hours per week, scattered:0
Hours per week, batched:0
Hours saved per year:0
Protecting the Block
The batch session only works if it happens, and it only happens if it's protected like a client meeting. Same day, same time, every week — the rhythm matters more than the specific slot. Saturday morning works for many creators (the week is done, the mind is clear); Friday afternoon works for others (harvest the week's conversations). Pick yours and put it on the calendar as a recurring, non-movable block.
Tell people about it. "I'm unavailable Saturday 9–11, that's my creation block" turns a private intention into a social commitment. Turn off notifications — not silent, off. Close the inbox tab. The world survived two hours without you before content existed; it will survive now. The block is a meeting with your future audience. Treat no-shows the way you'd treat standing up a client.
When you miss a week — and you will — run the half-session recovery: a 1-hour block producing 3 posts instead of 5, pulling only from your most developed ideas. Don't try to "make up" the missed week with a 4-hour marathon; marathons teach your brain that batching is punishment. The system survives misses. What kills it is the shame spiral of trying to compensate.
Build brief
Write your contingency plan: what is your half-session recovery (when, how long, how many posts)? And what will you tell yourself — in one sentence — when you miss a week, so you recover instead of spiraling?
Saved
Sam tried batching: he sat down for 2 hours with no prepared ideas and spent the whole session staring at his swipe file, hunting for topics. He concluded batching doesn't work. What's the real problem?
Your turn: Write your batch session agenda: your exact 2-hour block (day/time/place), your 5 idea slots for next week (pillar + working title each), and your 3 non-negotiable session rules.
Saved.
Your next 24 hours
Run a 30-minute mini-batch today: pick 2 developed ideas from your bank, draft both posts fast with no editing, then polish. Time it. That's the batching muscle — you're just training it at half weight first.
Steal this template
THE 2-HOUR BATCH SESSION
0:00–0:15 PREP: open swipe file, pick 5 developed ideas (rotate pillars), open templates. No writing.
0:15–1:15 DRAFT: write all 5 fast. Ugly is fine. No editing, no phone, forward motion only.
1:15–1:45 POLISH: read each aloud once. Fix hooks first, cut 10% of words, check pillar fit.
1:45–2:00 SCHEDULE: load all 5 into calendar/scheduler. Close laptop. Done for the week.
Rules: phone in another room, one tab, visible timer, never batch from zero.
Module 3 cheat sheet
- Scattered creation pays the 15–20 minute setup tax every session; batching pays it once.
- Creative momentum kicks in around minute 40 — post five takes half the time of post one.
- The Batch Session: 15 min prep, 60 min draft (no editing), 30 min polish, 15 min schedule.
- Session rules: phone away, one tab, visible timer — time pressure is a feature.
- Never batch from zero: the weekly idea review must feed the session with 5 developed ideas.
- Missed a week? Run the 1-hour half-session (3 posts), not a 4-hour marathon.