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

I set the rule on a Monday morning: no typing unless absolutely necessary. Passwords, terminal commands, anything that genuinely required a keyboard was allowed. Everything else, emails, documents, Slack messages, notes, had to be spoken.

I expected to last three days before giving up. I made it the full week, and the results were strange enough that I kept parts of it going long after.

Day One Was Uncomfortable

The first thing I noticed was how self-conscious I felt speaking into my computer. I work from home, so there was nobody to overhear me, but I still felt watched. Narrating my own thoughts out loud had an oddly exposing quality.

The second thing I noticed was how often I reached for the keyboard on instinct. Muscle memory runs deep. Every time a notification came in, my fingers were already moving before my brain caught up with the rule.

By noon I had dictated four emails, one Slack thread, and about 400 words of a draft I'd been stuck on for two weeks. I was tired in a different way than usual. More mentally alert, less physically tense.

By Day Three, Something Shifted

The self-consciousness faded. I stopped performing for an imaginary audience and just talked. The emails I was dictating started sounding more like me and less like a professional impersonating themselves.

I also started noticing how much time I normally spend staring at a blank document. When you're typing, the blankness is a visual fact. It stares back at you. When you're speaking, you just start somewhere and the words come. The friction of beginning almost disappeared.

I was using VoiceInk for most of this, pressing a hotkey and speaking directly into whatever app had focus. No copy-pasting from a separate transcription window, no switching context. The words just appeared. It sounds like a small thing. It isn't.

The Productivity Numbers Surprised Me

I tracked my word output that week out of curiosity. My normal writing days average around 800 to 1,000 words of usable prose. That week I averaged just over 1,600. The drafts were rougher and needed more editing, but there was more material to work with.

Email time dropped significantly. I'd been spending around 45 minutes a day on email. That week it was closer to 20. Speaking a response is just faster than writing one, especially for anything longer than two sentences.

What Was Actually Hard

Code. Code was hard. I gave myself a pass on anything in the terminal or an IDE, and I needed that pass.

Proper nouns and names were inconsistent. I spent more time correcting those than I expected.

And some thinking requires typing. There's a certain kind of slow, structural thinking that happens when you're deliberately placing each word. Outlines, for me, are better typed than spoken. The physical act of typing an outline feels different from narrating one.

What I Kept After the Week Ended

I went back to typing, but not to the same ratio as before. Now I dictate first drafts of almost everything longer than a paragraph. I dictate emails unless they're one-liners. I dictate notes during and after calls while the ideas are still fresh.

I type when precision matters from the start, code, outlines, anything that requires me to see the structure as I build it.

The biggest lasting change is that I start writing faster now. The week of voice-only broke a habit I didn't know I had: waiting until the sentence was perfect in my head before committing it to the page. Speaking forces you to commit. Typing lets you stall indefinitely.

If you've been curious about voice dictation but keep putting it off, one week is enough to find out whether it works for you. The answer might surprise you.