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

I set a simple rule on a Monday morning: no typing for anything that could be spoken instead. Emails, documents, Slack messages, notes. If it was prose, I had to dictate it. Seven days. I expected to feel productive. I did not expect to feel exposed.

Day One Was Humbling

I started with an email to a client. A normal, boring project update. I pressed the key, opened my mouth, and said absolutely nothing useful for about four seconds. Then I rambled. Then I started over. The email took longer to dictate than it would have to type, and it read like someone had transcribed a phone call.

The problem wasn't the tool. VoiceInk transcribed everything accurately. The problem was me. I had spent years writing by editing as I go, crafting sentences at the keyboard in real time. Speaking requires a different muscle: the ability to commit to a sentence before you know how it ends.

By Day Three, Something Shifted

I stopped trying to speak in final-draft sentences. I let myself talk the way I actually think, messily and in circles, and then cleaned it up afterward. That's when the speed kicked in.

A 400-word project summary that usually costs me 20 minutes to write took about 6 minutes to dictate and 5 minutes to edit. I was ahead on time, and the writing was more direct. Fewer passive constructions. Shorter sentences. Speaking out loud apparently has a natural bias toward clarity.

The Unexpected Benefits

My hands felt different by Wednesday. I hadn't noticed how much low-grade tension I carried in my forearms until it started to ease. I also noticed I was less fatigued at the end of the day. The kind of tired that comes from a full afternoon of keyboard work has a specific texture. That texture was mostly gone.

I also captured more ideas. When a thought hit me mid-afternoon, I just said it. No hunting for a notes app, no typing on my phone, no hoping I'd remember it later. I spoke it, VoiceInk dropped it into my open document, and I kept moving.

Where It Broke Down

Code was off the table. Even with dictation tools designed for developers, I wasn't going to dictate variable names and syntax. That was never the goal.

Punctuation took attention. You have to say "comma" and "period" explicitly, and for the first few days I kept forgetting. By day five it was automatic, but the learning curve was real.

I also struggled with short, choppy messages. A one-line Slack reply felt theatrical to dictate. I started making exceptions for anything under about 15 words. That felt reasonable.

What the Week Proved

I wrote more. Not a little more. Substantially more. My daily word count on documents and emails combined went up by roughly 60 percent. Some of that was the speed gain. Some of it was psychological: when writing feels effortless, you do more of it.

I also wrote looser first drafts, which sounds like a problem but isn't. Loose first drafts are editable. The real enemy of good writing is the blank page, not the rough page. Dictation gets you past the blank page faster than anything else I've tried.

What Stuck After the Week Ended

I went back to typing for short messages and code. But I kept dictation for anything over 100 words. Emails, articles, meeting notes, anything that used to make me stare at a cursor for too long.

The week didn't convert me into a voice-only purist. It converted me into someone who uses the right tool for the task. Speaking is faster for long prose. That's just true. It took seven days of discomfort to make me actually believe it.

If you've been curious about dictation but keep putting it off, try it for three days before you judge it. Day one will be rough. Day three might surprise you.