Here's a pattern anyone who writes regularly will recognize: you can explain your topic fluently to a colleague, but the moment the cursor blinks on an empty page, the fluency vanishes. That's not a talent deficit. It's a task-design problem.
The blank page asks you to do three jobs at once
Facing an empty document, you're simultaneously deciding what to say, in what order, and in which words. Each job is manageable alone; stacked, they overload working memory. The freeze you feel is your brain refusing to juggle.
Editors have known the fix for a century
Newsrooms never start reporters from a blank page. They start from a structure — the inverted pyramid, the nut graf, the house style. Structure removes two of the three jobs, leaving only "which words", and suddenly writing feels like filling in rather than conjuring.
A generated skeleton does the same thing
When a draft arrives with a title, headings, and rough prose already in place, your role shifts from author to editor — and editing is psychologically easier than authoring. You react instead of invent. You disagree with a sentence and fix it, which is a far smaller cognitive step than producing that sentence from nothing.
The value of a generated first draft isn't that it's finished. It's that it's wrong in useful ways — every flaw you spot is a decision made.
A practical protocol
- Generate a draft before you feel ready. Readiness follows momentum, not the other way around.
- Read the headings first and fix the structure before any sentence.
- Speak your objections out loud, then type what you just said. Your spoken register is usually your best writing voice.
- Keep a "cut file" for good sentences that don't fit — future posts start there.
Talent was never the bottleneck. The starting point was. Move the starting point, and the writing follows.