## TL;DR

Batch a week's content in one run by separating the phases: outline everything first, then draft everything, then review everything once, then schedule. Context-switching between writing and editing is what makes content slow; batching each phase keeps you in one mode. One focused session beats five scattered ones.

```text
how to batch-produce a week of content in one run
```

## Use this when

- Your time comes in blocks, not daily slices
- Running a weekly publishing cadence solo
- A pipeline stage keeps stalling on context switching

## Not for this skill when

- Content must react to same-day news (batching adds lag)
- Quality drops after the third piece (batch smaller)
- Review needs distance (sleep on drafts, then review)

## Steps

1. Outline the whole week first. Titles, one-line angles, and key points for every piece, no prose yet. Expected: five to seven outlines in under an hour.

2. Draft in one mode. Write all the drafts back to back without editing; editing mid-draft is the context switch that kills speed. Expected: rough drafts, all of them.

3. Take a break, then review once. Fresh eyes catch what tired writing missed; one review pass over everything. Expected: edited drafts ready to schedule.

```
batch phases:
  1. outline all (no prose)
  2. draft all (no editing)
  3. break
  4. review all (one pass)
  5. build packs + schedule
```

4. Build the packs and schedule. Assets per the checklist, scheduled dates set, queue loaded. Expected: the week runs itself from here.

5. Note what worked. Which pieces were easy, which dragged; adjust next week's batch size. Expected: the batch process improves weekly.

## Variant phrasings

### content batching workflow

Outline all, draft all, review once, pack and schedule. Separate the modes.

### producing a week of posts in one day

Phased batching: outlines, then drafts, then one review pass.

### batch content creation for solo teams

One mode at a time beats scattered effort; review after a break.

## Why it happens

Writing and editing use different mental modes, and switching between them is expensive. Batching keeps you in outline mode, then draft mode, then edit mode, so each mode's momentum compounds instead of resetting.

## Edge cases / pitfalls

- Do not batch more than you can review well; a week's worth is the sweet spot for most.
- Time-sensitive pieces do not batch; pull them out and handle separately.
- If drafts need overnight distance, split the batch across two days, not one.
- Track per-piece time; batching should reduce it, and the data tells you if it does.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst__M921wZYfQYFf9Es3nSjbg