How I Wrote 10,000 Words in a Day by Talking

I want to be honest about what this day looked like, because most "I wrote 10,000 words" posts skip the details that actually matter. Here's what mine looked like: messy, uncomfortable at first, and by the end, genuinely one of the most productive writing days I've had in years.

The Problem I Was Trying to Solve

I write long-form articles and occasional essays. My usual output was around 1,500 to 2,000 words on a good day. Not bad, but I knew the ideas were there. I'd go on a walk, narrate entire paragraphs in my head, and then sit down at my keyboard and produce something flatter and shorter than what I'd been thinking.

The keyboard was compressing me. I'd read that before and thought it was something writers said to sound interesting. Then I actually tested it.

The Setup

I didn't use any exotic hardware. I have a decent USB condenser microphone I'd bought for podcast recordings, and I installed VoiceInk on my Mac. VoiceInk runs locally, which mattered to me. I didn't want my half-formed draft ideas routing through a cloud server. I just wanted to press a key, talk, and see words appear.

I blocked out the full day. No meetings, no email before noon. Coffee. A rough outline of what I wanted to write, broken into six sections.

What the First Hour Felt Like

Awkward. I kept stopping mid-sentence to think, which is exactly what I do when I type, but somehow it felt more exposed when speaking. I also kept saying "um" and then waiting for it to appear in the text, which it didn't, because VoiceInk is smart enough to handle natural speech.

By the second session, I stopped performing and started talking. That's the shift. Dictation doesn't work when you're reading from an imaginary teleprompter. It works when you talk the way you'd explain something to a smart friend, loose and direct and willing to circle back.

The Output

By lunch I had 4,200 words. They weren't clean words. There were run-on sentences, repeated points, tangents that didn't go anywhere. But the core arguments were there, and some of the phrasing was better than what I'd have typed, because I wasn't editing while I generated.

I took a 45-minute break, did a short walk, and came back. The afternoon was faster. I'd found my dictation voice, that particular cadence that works when you're speaking prose rather than conversation. By 6pm I had 10,300 words across three documents.

The Editing Reality

I'll be straight with you: dictated drafts need more editing. Mine needed a full day of cleanup. Repeated words, structural wobbles, a few passages that made no sense because I'd lost my thread mid-sentence. This is normal.

But here's the thing. I had 10,000 words to edit. That's a much better problem than having 2,000 words and a blinking cursor. Editing is easier than generating. Getting words down is the hard part, and talking made that part dramatically faster.

What I Kept and What I Changed

I don't dictate everything now. Short replies, technical instructions, anything that needs precise language from the start, those I still type. But first drafts of any article over 1,000 words? I talk them out first. Every time.

The combination that works for me: dictate a full rough draft in one sitting, leave it overnight, edit at the keyboard the next morning. The draft is raw, but it's alive in a way that my typed first drafts rarely were.

If you've been stuck at the same daily output for a while and your ideas feel bigger than your drafts, one afternoon of talking might show you exactly where the constraint has been hiding.