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

I set a simple rule on a Monday morning: no typing except for passwords and code. Everything else, emails, notes, articles, Slack messages, had to be dictated. I expected to feel productive. I did not expect to feel exposed.

Day One: The Awkwardness Is Real

The first thing I noticed was how strange my own voice sounded when I was trying to write. Speaking conversationally is easy. Speaking in complete, structured sentences while staring at a blank document is its own skill, and I did not have it yet.

I dictated my first email three times before I was happy with it. The words came out fine, but I kept stopping to think mid-sentence, which left a trail of half-phrases on screen. By the afternoon, I had learned to pause before speaking rather than mid-thought. That was the first real adjustment.

Day Two and Three: The Friction Starts Lifting

By Wednesday I had stopped noticing the setup. Press the key, talk, done. VoiceInk's transcription is fast enough that the words appear almost as I say them, which helped. When there is a long delay between speaking and seeing text, your brain starts to drift. When it is near-instant, the loop stays closed.

I wrote a 900-word article on Tuesday morning in about 22 minutes, including a quick edit pass. My usual time for a first draft that length is closer to 50 minutes. I checked my word count three times because I did not believe it.

The Surprising Part: My Writing Got Looser (In a Good Way)

I have a habit of over-editing while I write. I will type a sentence, read it, delete half of it, and retype. Voice broke that habit because there is no natural pause point for mid-sentence deletion. You finish the thought, then you edit. That forced sequence produced cleaner first drafts than my usual stop-and-second-guess approach.

Several people commented that my writing that week felt more direct. I had not changed my editing process. I had only changed the input method.

What Did Not Work

Slack was genuinely hard. Short, punchy messages do not suit dictation well. Saying "sounds good" out loud feels absurd. I ended up typing those anyway and accepting the rule-break. Voice is better for longer-form output. Anything under two sentences is probably faster to type.

Code was off-limits by my own rule, which was the right call. Dictating variable names and syntax is possible with the right tools, but that was not the experiment I was running.

Day Seven: Did I Want to Go Back?

On Sunday I sat down and just typed for a while to see how it felt. It felt slow. Not dramatically, but noticeably. Like switching from a wide road to a narrower one. You can still get where you are going; you are just more aware of the constraints.

I did not go fully voice-only after the experiment. But I stopped defaulting to typing for first drafts. Now the split looks roughly like this: dictation for anything over 200 words, typing for everything short and structural. That combination is faster than either alone.

What the Week Actually Taught Me

The awkwardness on day one is not a sign that voice dictation is not for you. It is a sign that you are learning a new output method, and new output methods always feel wrong before they feel right.

The payoff is real. More words per hour, less hand fatigue, and a writing voice that sounds more like how you actually think. That last one surprised me the most.

If you have been curious about dictation but have not committed to a real trial, a week is long enough to get past the learning curve and see what is actually on the other side. Give it the same patience you gave typing when you were learning it.