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

I want to be upfront: I did not actually stop typing for a full week. I still typed passwords, terminal commands, and the occasional snarky reply that felt wrong to say out loud. But for all writing, notes, emails, and documents, I went voice-only for seven days. What I found was stranger and more useful than I expected.

Day One Was Humbling

The first morning I tried to dictate an email and kept stopping mid-sentence. Not because the transcription was wrong, it was mostly fine. I stopped because I didn't know what I wanted to say until I'd already started saying it. With typing, I could sit quietly and think. With dictation, the silence felt like failure.

This was the first thing I learned: I had been using the act of typing as a thinking tool, not just a transcription tool. The slow pace of typing gave me time to figure out what came next. Remove the keyboard and the scaffold disappears.

By Day Three, Something Shifted

Once I stopped waiting to know exactly what I'd say before I said it, things got faster. I started treating dictation like thinking out loud, which is what it actually is. The quality of the first draft was rougher. The quantity was significantly higher.

On day three I wrote 2,200 words of a long article in about 40 minutes. That would have taken me close to two hours at the keyboard, including all the micro-pauses and self-corrections. The draft needed more editing than usual, but it existed, which is the first requirement of any draft.

The Email Revelation

Emails were the biggest surprise. I had a backlog of about a dozen messages I'd been avoiding because they required thought and I didn't want to invest the typing effort. I cleared all twelve in one sitting by speaking them. Some took 90 seconds. One took four minutes.

I'd been using typing friction as an unconscious filter for what was worth saying. Some of that filtering is good. But in this case, I was just delaying useful communication because the interface made it feel expensive.

Using VoiceInk to pipe directly into my email client meant there was no extra app to open, no copy-paste step. I just pressed a key, spoke, and the words appeared in the compose window. That directness mattered more than I thought it would.

What Got Harder

Anything structural was worse by voice. Trying to dictate a bulleted list or a table felt awkward. I had to stop and reach for the keyboard anyway. Technical writing with specific formatting, file paths, variable names, was slower to dictate than to type.

I also found that dictating in public felt strange. I work from home, but even so, speaking my emails out loud made them feel less private somehow. The inner monologue wanted to stay inner.

What I Kept After the Week Ended

I didn't go voice-only after the experiment. I didn't plan to. But I kept dictation for three specific things: first drafts of any document over 300 words, email replies that require more than two sentences, and capturing ideas when they arrive mid-thought and I don't want to lose the thread.

For those cases, voice is faster, less fatiguing, and pulls out more natural language than typing does. My typed prose tends toward the formal. My dictated prose sounds more like how I actually talk, which for most of what I write is a better starting point.

Try the Uncomfortable Thing

The first two days of this experiment were genuinely uncomfortable. I'd been typing for so long that it felt like thinking itself. It isn't. It's just one way to get thought onto a page, and it's not always the best way.

If you haven't tried dictating your writing, a week is too long for a first test. Start with one email or one paragraph. Notice whether the words come out differently when you speak them. They usually do.