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

I did not plan to make it a whole week. I started on Monday morning because my right wrist was sore and I needed to write a long client proposal. I figured I'd dictate that one document and go back to typing. I didn't go back.
Day One: Slower Than Expected
The first morning was humbling. I kept stopping mid-sentence, saying "no wait" and then going silent while I tried to figure out what I actually wanted to say. I wrote maybe 600 words in an hour. Normally I'd hit that in 20 minutes.
The problem wasn't the tool. VoiceInk transcribed everything accurately and fast, appearing right where my cursor was without any extra steps. The problem was me. I had no idea how often I used typing itself as a thinking mechanism, pressing keys while my brain caught up.
Voice doesn't let you do that. You have to know what you're going to say before you say it.
Day Two and Three: Finding a Rhythm
By Wednesday I had developed a small habit. Before speaking a sentence, I'd pause for a beat and finish the thought in my head. It felt slow at first. Then it started to feel like something else: editing before output instead of after.
My first drafts were cleaner. Not perfect, but structurally better. Less backtracking. Fewer sentences that started in one direction and collapsed in the middle.
I also noticed I was less tired in the afternoons. My wrist stopped aching by Tuesday.
The Email Problem
Email was harder than I expected, for a specific reason. My emails got longer.
When typing, there's natural friction that keeps messages short. When speaking, a 40-word reply becomes a 120-word reply without any effort. I had to consciously cut after dictating, which added a step I wasn't used to.
By day four I had adjusted. I'd dictate the full thought, then do one quick pass to trim. It was still faster than typing the whole thing, and the emails were arguably more useful because I'd actually said everything I meant to say.
Writing That Surprised Me
Thursday I had to write a 1,500-word article. I dictated the whole first draft in about 18 minutes. I know because I looked at the clock when I started and again when I finished.
The draft needed editing. But there was a draft. That's not always guaranteed when you're staring at a blank document.
Something about speaking the words made the writing feel less precious. It's easier to delete a paragraph you said out loud than one you labored over with your fingers.
What I Missed About Typing
Code. I write some light scripts and markdown by hand, and dictating syntax is genuinely awkward. I cheated on day five and typed a short bash command rather than say "backtick bash newline" out loud.
Also, typing in public. Dictating in a coffee shop is not something I managed to do without self-consciousness, though I've since learned that whispering works better than I expected.
What I Kept After the Week
I went back to typing, but not all the way back. Now I dictate first drafts, long emails, and any document where the main challenge is getting thoughts onto the page. I type for editing, code, and short replies.
The split works well. Voice for output, keyboard for refinement. It cut the sore wrist problem down to almost nothing.
If you've been curious about dictation but haven't tried it for more than five minutes, give it a full day. The first hour is the hardest part.
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.