I Stopped Typing for a Week. Here's What Happened.

I did not plan it as an experiment. My right wrist had been aching for three weeks, and my physio gave me a direct instruction: stop typing as much as possible, or we will be having a much longer conversation in six months. So I stopped. Or tried to.

Day One: Humbling

I set up VoiceInk on my Mac on a Sunday night. Monday morning I sat down to write my usual to-do list and could not get through it without laughing at myself. "New doc, hyphen, check, hyphen." I was saying punctuation out loud like I was dictating a telegram from 1940.

The transcription was accurate. I was the problem. I had no idea how to speak in sentences that were also meant to be read. I wrote about 200 words in an hour that would normally take ten minutes.

Day Two and Three: Finding a Rhythm

By Tuesday I had stopped announcing punctuation for everything and started letting sentences land more naturally. I discovered that if I just spoke the way I would explain something to someone sitting across from me, the output was actually cleaner than my usual typed prose.

Wednesday I wrote a 600-word article almost entirely by voice. It took 35 minutes including editing. That was not slower than my normal pace. It was roughly the same, and my wrist felt fine.

I also noticed something I had not expected: I was less precious about first drafts. When you type, each word feels considered because each word cost you a keystroke. When you speak, the words come fast enough that you stop treating them as individual investments. The draft is rougher but there is more of it, and more is easier to edit than nothing.

Day Four: The Weird Part

I had a 2,000-word piece due Thursday. I dictated the whole first draft in one sitting, walking around my apartment with my laptop open on the kitchen counter. The draft took about 25 minutes. It was messy and had three tangents that went nowhere, but the core argument was all there.

Editing it took another 40 minutes. Total time: just over an hour for 2,000 publishable words. My usual process for a piece that size is closer to three hours.

I texted my editor: "I think I've been doing this wrong for years."

Day Five and Six: The Limits Show Up

Not everything works well by voice. Code, obviously. Anything with specific formatting, like a spreadsheet or a structured outline with nested bullets, took more effort to dictate than to type. Replying to short emails was faster by voice. Writing a long email with precise technical language was slower because I kept having to go back and fix terms.

I also found that noisy environments killed the workflow. A coffee shop was impossible. My home office, quiet, worked well.

Day Seven: A New Default

By Sunday I was not thinking of dictation as the alternative anymore. It had become the first instinct for anything longer than a sentence or two. I was reaching for my voice the way I used to reach for the keyboard.

My wrist improved enough that my physio said I could ease back into normal typing. I told her I was not sure I wanted to.

What I Took Away

A week of voice-first writing changed two things. It fixed the immediate physical problem, which was the point. But it also showed me that the keyboard, for long-form writing, had been slowing me down in ways I had completely normalized.

The gap between thinking and writing is real. Speaking closes it in a way that typing never will.

If your wrists are tired, or if you are just curious what your writing looks like when it comes out faster than your inner editor can intercept it, give a week of dictation a real try. The first day is awkward. The rest is interesting.