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

I did not plan to write 10,000 words on a Tuesday. I planned to write 2,000, which is already a stretch goal for me. But something happened around 10am that changed the pace of the whole day, and by 9pm I had more usable first-draft material than I had produced in the previous two weeks combined.

The only thing I did differently was stop typing.

How the Day Started

I had been fighting a chapter for three days. The ideas were there. The structure was roughed out in my notes. But every time I sat down to type it, I would write 300 words, hate them, delete half, rewrite, and end up with something worse than what I started with. The editing instinct kept ambushing the writing instinct.

On Tuesday morning, on a mild impulse, I set up VoiceInk and decided I would speak the chapter instead. Not as a serious experiment. More as a way to break the paralysis.

What Actually Happened

I started talking. I described what I wanted the chapter to do. I explained the argument out loud the way I would explain it to a friend who had not read the book. I did not try to write clean sentences. I just talked.

The words appeared in my document in real time. Not perfect words. Rambling words, repeated words, words that contradicted each other two sentences later. But they were words, and they were coming fast, and the chapter was getting longer.

I hit 2,000 words before lunch without noticing. I had not stopped to reread. I had not deleted anything. I just kept talking.

The Afternoon Shift

After a break, I came back and read what I had. About 60 percent of it was genuinely usable. Some of it was better than anything I had typed that week, because it had the rhythm of actual speech, which is often closer to how I want my prose to sound anyway. The other 40 percent was scaffolding: thinking out loud that had served its purpose and could go.

I kept going. Section by section, I would spend two minutes reviewing my outline notes, then speak for twenty or thirty minutes. The ratio of generation to editing flipped completely from my normal process. I was creating fast and editing slowly, which is the right order.

What Made It Work

A few things mattered. First, VoiceInk's transcription was accurate enough that I was not spending time fixing errors every paragraph. When the output is full of mistakes, you stop to correct constantly and lose the flow. Accuracy is not a nice-to-have. It is load-bearing.

Second, I kept my outline visible on a second screen. Knowing where I was going meant I did not have to hold the structure in my head while also generating sentences. The cognitive load split in a useful way.

Third, I gave myself full permission to be bad. Dictated first drafts are ugly. They repeat themselves. They meander. That is fine. The job is to exist, not to be good. Good is for the second draft.

The End of the Day

By 9pm I had 10,200 words. After an editing pass the next morning, I kept 7,400 of them. That is more than I typically write in a week of normal typed drafting.

I am not saying everyone will get those numbers. My topic was one I had been thinking about for months, so the ideas were ready. What dictation did was remove the bottleneck between the ideas and the page.

What I Changed After That

I still type plenty. Short emails, code, anything that needs precision from the first word. But for first drafts of anything longer than a few paragraphs, I speak now. The keyboard comes back for editing.

If you write for work or for yourself, one afternoon talking into a document is worth trying. The worst case is you end up with a weird transcript. The best case is you find out your ideas move faster than you thought.