I Stopped Typing for a Week. Here's What Happened.
I did not expect to miss punctuation this much. That was my first real thought on day two of my week without typing, standing in my kitchen, dictating a grocery list into VoiceInk and then pausing to wonder how to add a comma between "eggs" and "bread." I said "comma" out loud. It worked. I felt absurd and also impressed.
Here is what a week of voice-only input actually looked like.
Day One: Slower Than Expected
I had assumed voice would feel faster immediately. It didn't. The first morning I dictated three emails and it took twice as long as usual, not because the transcription was slow, but because I kept stopping to think. Typing lets you half-think while you write. Speaking forces you to commit to a full sentence before it leaves your mouth.
By the afternoon, I'd written about 800 words of an article. That part did feel faster. The ideas came in longer runs. I wasn't stopping to fix typos.
Day Three: The Fatigue Shift
Something interesting happened around day three. My hands felt different. Not healed, exactly, I don't have serious RSI, but there was an absence of the low-grade tension I usually carry in my forearms by mid-afternoon. I hadn't noticed that tension until it was gone.
My voice got slightly tired by evening, which I hadn't anticipated. Talking for eight hours is its own kind of work. I started being more deliberate, choosing words before I spoke them, not rambling. That discipline showed up in the writing.
Day Five: Finding a Rhythm
By day five I had stopped thinking about the process. I'd walk to the window, dictate a paragraph, come back to the screen to read it. The physical separation, standing to speak, sitting to review, turned out to be useful. Each dictation session was a small commitment. I wasn't just noodling. I was delivering a paragraph.
I wrote the fastest first draft I've produced in years on day five. Just over 1,200 words in about 40 minutes. Not polished, but complete. The bones were there.
What Broke Down
Code didn't work. I tried. Dictating variable names and brackets is miserable and I gave up after 10 minutes. For anything technical, the keyboard is still the right tool. Short replies, search queries, and anything requiring precise formatting also felt awkward by voice.
Voice is not a replacement for typing. That was never really the question.
What Surprised Me
I expected to feel slower overall. I didn't. Long-form writing, email drafts, meeting notes, brainstorming, all of it came out at roughly the same pace or faster, with less physical effort.
I also expected the transcription to be a constant source of errors. Using VoiceInk locally, the accuracy was high enough that I stopped worrying about it. An occasional wrong word, easy to fix on review, but not the steady stream of corrections I'd imagined.
Most of all, I did not expect to enjoy it. There's something satisfying about speaking a paragraph and watching it appear, complete, on the screen. It feels direct in a way that typing doesn't.
Would I Do It Again
I'm back to typing for most things. But I now dictate first drafts almost every time. The week forced me to build the habit, and the habit stuck.
If you've been curious about voice dictation but never committed to it seriously, seven days is long enough to find out whether it fits how you work. The first two days are awkward. After that, it starts to feel normal. After a week, typing a long article feels slightly inefficient by comparison.
That comparison alone is worth something.
Don't type. Speak.
VoiceInk Pro for a full year at $50 instead of $69. Wispr Flow charges $144 a year; this is about a third of that. Mac and Windows, cancel anytime.
Get a year for $50Code READER50 is applied at checkout. Not ready to pay? Download VoiceInk free.