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

I typed somewhere between 4,000 and 6,000 words a day. Emails, documents, Slack messages, code comments, notes to myself. All of it through the keyboard. When a friend told me to try dictating everything for a week, I said sure, mostly to prove it wouldn't work.

It half-worked. That half changed how I write.

Day One: The Silence Problem

The first thing I noticed was how often I sit in silence, thinking, before I type anything. When you're dictating, silence becomes awkward in a way it never is at a keyboard. I kept feeling like I needed to be talking, which made me rush, which made my sentences worse.

I also discovered how many tiny tasks I do without thinking. Renaming a file. Searching a tab. Copying a URL. None of these were impossible by voice but all of them were slower. I cheated on those. I told myself shortcuts for system tasks don't count.

Day Three: Email Got Easier

By Wednesday I was dictating emails without hesitating. This surprised me most. Email had always felt like a place where I chose every word carefully, deleted a lot, rewrote openers. Dictating email turned out to require less of that, not more.

Speaking a reply out loud forces you to commit to a tone. You can't quietly hedge the way you can at a keyboard. The emails I sent that week were more direct than usual. One colleague replied to ask if I was okay because my note was "unusually concise." I took that as a compliment.

VoiceInk made this practical. I'd hit the shortcut, dictate into whatever email was open, and the text landed where my cursor was. No extra steps, no copying from another app.

Day Five: The Long-Form Shift

I had a report due Friday. About 1,500 words. I dictated the whole first draft in one session, standing at my desk, speaking to no one in particular.

It took 22 minutes. The draft was not clean. Some sentences ran long, a few thoughts repeated, the transitions needed work. But the structure was right and all the ideas were there. Editing that draft took another 25 minutes. Total time: under an hour for a polished 1,500-word document.

My keyboard version of that same report would have taken the better part of a morning.

What Actually Broke

Code. I write code every day and dictating code is, for now, genuinely painful. Variable names, syntax, brackets. I tried it for about 20 minutes on day two and gave up. Voice for code comments worked fine. Voice for code itself did not.

Short reactive messages also stayed awkward. A two-word Slack reply is not worth the overhead of switching modes. I kept the keyboard for anything under 10 words.

What Stuck After the Week Ended

I didn't quit typing. But I didn't go back to typing everything.

First drafts of anything over 300 words, I dictate. Meeting notes, I dictate. Long emails where I'm explaining something complex, I dictate. Anything where I need to think out loud and capture simultaneously, I dictate.

My hands are at the keyboard for maybe 60 percent of what they used to be. The ache in my right forearm that I'd been ignoring for two years has mostly gone quiet. That alone was worth the experiment.

The biggest surprise was not the speed, though the speed was real. It was that talking felt closer to thinking than typing ever did. The keyboard always felt like translation. Speaking felt like just saying the thing.

If you're curious, try it for two days before you decide. One day isn't enough to get past the awkward phase. Two days usually is.