I Stopped Typing for a Week. Here Is What Happened.

I made myself a rule on a Monday morning: no typing unless absolutely necessary. Passwords, terminal commands, proper nouns that dictation mangles. Everything else goes through my voice. I gave it seven days.

By Friday I had changed the way I write.

Day One Was Awkward

The first hour was uncomfortable in a way I did not expect. Not technically, the setup was straightforward, VoiceInk running in the background, a single key to hold while I spoke. The discomfort was social and psychological. Speaking out loud felt performative, even alone in my apartment.

I kept starting sentences and stopping. I would dictate three words, cringe, delete them. I was editing out loud the same way I edit while typing, except it felt more exposed.

I wrote maybe 200 words in that first hour. Normal for a slow day, bad for an experiment meant to prove dictation was faster.

Day Two and Three: The Shift Starts

Something changed around Tuesday afternoon. I stopped monitoring my own voice and started just talking. The self-consciousness burned off.

I dictated a long email to a client. It took four minutes. I reread it and changed two words. Under normal circumstances that email would have taken me fifteen minutes, with multiple rewrites and a final read-through where I second-guess every sentence.

The email I dictated was more direct. Less hedged. I think speaking removed the option to overthink.

The Unexpected Places It Worked

I dictated a grocery list while walking to the kitchen. I left myself a three-minute voice note about a project idea I had in the shower, then dictated it into a doc when I got to my desk. I drafted an article outline during a walk, speaking into my phone, then cleaned it up later.

None of that would have happened if I needed to sit down and type. The ideas would have evaporated.

For longer writing, the gains were real. I wrote a 2,000-word piece on Wednesday in about 90 minutes. That includes time for two short breaks. My average for 2,000 words while typing is closer to three hours.

What Broke Down

Code was off the table. Even with voice coding tools available, I did not want to spend the week learning a new system. I typed my terminal commands and my code.

Proper nouns and technical vocabulary created small interruptions. I would say a name, watch VoiceInk guess wrong, fix it with a quick keystroke, and move on. Not a dealbreaker, but worth noting. A few minutes of custom vocabulary work at the start would have fixed most of it.

Concentration-heavy editing still happened at the keyboard. Dictation is for generating. Cutting, restructuring, tightening, those are keyboard tasks.

What the Week Proved

My output volume went up. I do not have a perfect word count comparison, but I published two pieces that week when my usual is one. I cleared my email backlog on Tuesday and kept it clear.

More importantly, my first drafts were better. Not polished, but more complete. I followed arguments to their conclusions instead of stopping halfway through because the typing felt slow. Dictation has a momentum that typing does not.

The awkwardness of day one disappeared entirely by day four. By the end of the week, reaching for the keyboard to write a paragraph felt like the slower choice.

One Week Is Enough to Find Out

I am not suggesting you throw away your keyboard. I did not. But if you write anything for work, articles, emails, documentation, notes, there is a real chance that voice is faster for you and you do not know it yet because you have never seriously tried.

Seven days is a reasonable test. Set up a tool like VoiceInk, pick your lowest-stakes writing tasks first, and give it until the end of the week before you judge it.

The awkward part passes faster than you expect.