How to produce multiple pieces of content efficiently by batching similar tasks together. This system lets you publish 2-3 high-quality pieces per week without burning out.
Traditional content creation: do everything for one piece sequentially, then start the next from scratch.
SEQUENTIAL (slow, high context-switching cost):
Piece 1: research β outline β write β edit β publish
Piece 2: research β outline β write β edit β publish
Piece 3: research β outline β write β edit β publish
Batched content creation: group identical tasks across multiple pieces.
BATCHED (fast, low context-switching cost):
Research day: Research piece 1, 2, 3
Outline day: Outline piece 1, 2, 3
Writing day 1: Write piece 1, 2
Writing day 2: Write piece 3
Edit day: Edit piece 1, 2, 3
Publish week: Publish piece 1 (Mon), 2 (Thu), 3 (next Mon)
Batching works because the cognitive overhead of "getting into research mode" or "getting into editing mode" only happens once per batch, not once per piece.
This system produces 4 pieces every 2 weeks (2/week publishing cadence):
| Day | Task | Time | Output |
|---|---|---|---|
| Monday | Research & collect sources for 4 pieces | 3 hours | Research notes for all 4 pieces |
| Tuesday | Write detailed outlines for all 4 | 2 hours | 4 outlines with bullet points under each section |
| Wednesday | Write first drafts for pieces 1 & 2 | 4 hours | 2 rough drafts (focus on getting ideas down) |
| Thursday | Write first drafts for pieces 3 & 4 | 4 hours | 2 rough drafts |
| Friday | Edit all 4 drafts (structural edit) | 3 hours | 4 structurally sound drafts |
| Day | Task | Time | Output |
|---|---|---|---|
| Monday | Final polish piece 1 + publish + promote | 2 hours | Piece 1 live |
| Tuesday | Create all social assets for pieces 1-4 | 2 hours | Threads, LinkedIn posts, images batched |
| Wednesday | Final polish piece 2 | 1 hour | Piece 2 ready |
| Thursday | Publish piece 2 + promote | 1 hour | Piece 2 live |
| Friday | Final polish pieces 3 & 4 + scheduling | 2 hours | Pieces 3 & 4 ready for next week |
Total production time: ~22 hours across 2 weeks = ~11 hours/week for 2 posts/week.
Sit down with all your content briefs for the batch. Open all sources, papers, documentation, and competitor articles at once. Take notes for ALL pieces in one session.
Why this works: Research mode requires deep reading and synthesis. Context-switching between "read deeply" and "write fluently" is expensive. Do all reading at once.
Tips:
Block 3-4 hours of uninterrupted time. Write one full draft, take a 10-minute break, then write the next. Don't edit during the writing phase β just get words down.
Why this works: Writing flow takes 15-20 minutes to establish. Once you're in flow, you can maintain it across multiple pieces if you don't break to edit.
Tips:
Edit all drafted pieces in a single session. Each piece gets three passes:
1. Structural pass: Is the argument logical? Are sections in the right order? Any redundancy?
2. Clarity pass: Jargon without explanation? Paragraphs that could be sentences? Passive voice?
3. Polish pass: Transitions, opening hooks, closing CTAs, internal links, SEO title/meta
Why this works: Editing requires a different mindset than writing. The critical eye, once activated, works efficiently across multiple pieces. Also: editing your own work is easier with time-distance, and batching naturally creates that gap.
After publishing, batch all promotion assets:
Why this works: Each platform has its own voice and constraints. Adapt to one platform's format once, then crank out all the content for it before switching to the next platform.
If your editorial calendar has recurring formats, batch by type:
Write all tutorials for the month in one batch. They share:
Write all opinion pieces together. They share:
Listicles are the fastest to batch because they're modular:
Not all tasks require the same energy level. Schedule batches according to your daily energy:
| Energy Level | Best Tasks |
|---|---|
| Peak (morning for most people) | First-draft writing, research synthesis |
| Medium (mid-day) | Editing, outlining, structuring |
| Low (afternoon) | Formatting, scheduling, social posts, admin |
Don't fight your biology. If you write best at 6 AM, protect that time for drafting. If you're sharpest at 10 PM, batch your editing sessions there.
Batching only works if you stay ahead of your publishing schedule. Maintain a buffer:
| Buffer Level | Status | Action |
|---|---|---|
| 4+ pieces ready | Comfortable | You can take a week off without missing a publish date |
| 2-3 pieces ready | Normal | Standard operating mode |
| 1 piece ready | Warning | Prioritize next batch β cancel non-essential meetings |
| 0 pieces ready | Emergency | Publish a lighter-format piece (listicle, quick take) to buy time |
Goal: Never publish from a position of zero buffer. The stress of a deadline destroys quality.
You don't need specialized software, but these workflows help:
| Need | Low-tech Solution | Tool Solution |
|---|---|---|
| Track piece status | A column in your editorial calendar CSV | Trello/Notion kanban |
| Store research | Markdown files per piece | Notion databases, Raindrop |
| Draft without distraction | Any markdown editor + full screen | iA Writer, Typora |
| Schedule social posts | Pre-written + manual posting | Buffer, Typefully |
| Track publishing dates | CSV calendar + phone reminders | Google Calendar events |
The system in this toolkit (CSV + markdown files) works perfectly for batching. The editorial calendar shows what's scheduled, the briefs guide your writing sessions, and the repurposing tracker ensures nothing gets left unpromoted.
| Pitfall | Solution |
|---|---|
| Trying to batch too many pieces (8+) | Start with 4. You can increase once the rhythm feels natural. |
| All pieces in the same pillar | Force pillar diversity in each batch β it keeps writing fresh. |
| Skipping the buffer and publishing as you write | Finish the full batch before publishing the first piece. |
| Perfectionism during first-draft batches | Remind yourself: editing day exists. Drafts are for IDEAS, not perfection. |
| Ignoring energy levels | Track your best hours for 1 week, then permanently assign them to writing. |
| Not resting between batches | Production weeks should be followed by lighter weeks. Don't batch every single week. |
How to choose, develop, and evolve the core themes that define your content brand. Your pillars are the answer to "what is this creator known for?" β get them right and everything else (topics, SEO, audience growth) follows.
Without pillars, content creation is reactive. You chase trending topics, respond to whatever caught your attention today, and end up with a scattered portfolio that attracts no one specifically.
With pillars, you build compounding authority:
| Pillars | Best For | Trade-off |
|---|---|---|
| 2-3 | Narrow niche experts, SEO-focused creators | Deep authority, but risk of running dry |
| 4-5 | Most technical content creators | Good balance of depth and variety |
| 6-7 | Media companies, prolific creators (3+ posts/week) | Breadth, but harder to build depth in each |
Recommended starting point: 4 pillars. You can always split a successful pillar into two, or merge underperforming ones later.
Draw a 2Γ2 matrix:
HIGH audience demand
β
βββββββββββββββββΌββββββββββββββββ
β β β
β INVEST β GOLDMINE β
β (build β (your best β
β expertise) β pillars) β
β β β
LOW ββββββΌββββββββββββββββΌββββββββββββββββΌβββββ HIGH
expertiseβ β β expertise
β β β
β IGNORE β HOBBY β
β (don't β (10% pillar β
β bother) β at most) β
β β β
βββββββββββββββββΌββββββββββββββββ
β
LOW audience demand
For each candidate pillar, brainstorm 20 specific article ideas in 5 minutes. If you can't hit 20, the pillar is too narrow. If you hit 50+ easily, it might be too broad (consider splitting).
Your pillars should be distinct but related. A reader interested in one pillar should plausibly care about the others.
Good pillar set (for a backend engineer):
These overlap naturally β a reader interested in architecture likely also cares about productivity and leadership.
Bad pillar set (too disconnected):
These attract completely different audiences. You'd be better off with separate channels.
Each pillar naturally lends itself to certain formats:
| Pillar Type | Best Formats | Example |
|---|---|---|
| Technical Deep Knowledge | Deep dives, tutorials, benchmarks | "How database indexes actually work" |
| Opinions & Frameworks | Opinion pieces, comparisons, decision guides | "Why microservices are a bad default" |
| How-To & Practical | Tutorials, how-tos, tool comparisons | "Setting up CI/CD with GitHub Actions" |
| Career & Growth | Personal essays, frameworks, advice | "The skills that got me promoted to staff" |
| Industry Analysis | Trend reports, predictions, commentary | "The state of frontend frameworks in 2025" |
Design your pillar mix to include at least 2 different pillar types. This creates natural variety in your content without feeling random.
Assign each publishing slot to a specific pillar. Simple and predictable.
Week 1: Pillar A, Pillar B
Week 2: Pillar C, Pillar A
Week 3: Pillar B, Pillar D
Week 4: Pillar D, Pillar C
Pros: Guarantees balance. Easy to plan.
Cons: Inflexible when timely content arises.
Set target percentages and aim to hit them monthly, but don't lock specific days.
Architecture: 35% (aim for 3 per month if publishing 8/month)
Productivity: 25% (aim for 2 per month)
Leadership: 25% (aim for 2 per month)
Commentary: 15% (aim for 1 per month)
Pros: Flexible. Can respond to timely opportunities.
Cons: Requires monthly tracking to avoid drift.
Plan 4-6 piece "seasons" within a pillar, then rotate to another pillar's season.
January: Architecture Season (4 connected pieces on distributed systems)
February: Productivity Season (4 pieces on developer workflows)
March: Leadership Season (4 pieces on engineering management)
Pros: Deep topical authority. Can become ebooks/courses.
Cons: Readers only interested in one pillar may disengage for entire months.
Recommended: Start with Weighted Random. Graduate to Narrative Arcs once you have a large enough audience that won't churn during off-pillar months.
1. Don't abruptly kill a pillar. Taper it: 30% β 15% β 5% β retired over 3 months.
2. Write a capstone piece that summarizes and links everything in the retiring pillar. This becomes an evergreen resource page.
3. Announce the new pillar to your audience. "I'm going to be writing more about X because Y." Transparency builds trust.
4. Run a 4-piece trial in the new pillar before committing. If engagement validates it, formalize it.
Each pillar should have:
This creates a topical cluster that search engines reward with authority. You'll rank for broader terms as Google sees you comprehensively covering the topic.
ββββββββββββββββ
β Pillar Page β (targets broad keyword)
β "Distributed β
β Systems" β
ββββββββ¬ββββββββ
β
ββββββββββββββββββΌβββββββββββββββββ
β β β
βββββββΌββββββ βββββββΌββββββ βββββββΌββββββ
β Cluster β β Cluster β β Cluster β
β Article β β Article β β Article β
β "CAP β β "Saga β β "Event β
β Theorem" β β Pattern" β β Sourcing"β
βββββββββββββ βββββββββββββ βββββββββββββ
Track these metrics per pillar (monthly):
| Metric | What It Tells You |
|---|---|
| Total views | Overall interest level |
| Views per article (average) | Consistency β is this pillar reliably attracting readers? |
| Email signups attributed | Does this pillar attract your ideal audience? |
| Social shares per article | Engagement quality β are people compelled to spread this? |
| Search impressions growth | Are you building topical authority in search? |
| Backlinks gained | External validation β are others referencing your work? |
| Revenue attributed | Is this pillar converting to products/services? |
| Your enjoyment (1-5) | Sustainability β can you keep writing in this pillar? |
Review quarterly. The best pillar is one that scores well on BOTH audience metrics AND your enjoyment. High-performing but soul-crushing pillars lead to burnout. Fun but low-performing pillars are hobbies, not strategy.
Get the full Editorial Calendar System and unlock everything.
Get the complete guide with every chapter unlocked, including code samples, diagrams, and best practices.
Access all interactive tools with complete data, all workload profiles, and the full scenario library.
Downloadable source code, configuration files, and working examples from every chapter.
Free updates for life. Every new chapter, tool, and improvement included.