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

I told myself I'd do it properly. No cheating, no fallback to the keyboard when things got awkward. For one full week, every word I wrote would be spoken, not typed. This included emails, Slack messages, documents, and a blog post I had due on Thursday. Here's what actually happened.

Day One Was Humbling

I set up VoiceInk on my Mac on a Sunday evening, read the basics, and decided Monday morning would be the start. Monday morning arrived and I immediately typed my laptop password out of pure muscle memory before I'd even had coffee. That set the tone.

The first hour was slow. I kept stopping mid-sentence because I wasn't sure how to punctuate by voice. I'd say a clause, pause, realize I needed a comma, say "comma," and then forget what I was going to say next. My first email took eleven minutes. It usually takes two.

By Day Three, Something Shifted

I stopped thinking about the mechanics and started just talking. The emails got faster. I noticed I was writing longer, more complete sentences because I wasn't tempted to truncate for the sake of my fingers. My replies had more detail. A couple of colleagues mentioned my emails seemed more thorough that week. I didn't tell them why.

The blog post went surprisingly well. I spoke the first draft in about 25 minutes, which is faster than I've ever typed one. The draft was rougher than usual, more conversational, but there was more of it to work with. Editing felt easier because the raw material was richer.

The Frustrating Parts Were Real

Open plan noise is a problem. I work from home but I have a dog, and at one point she started barking mid-paragraph and I ended up with the word "bark" inserted into a sentence about content strategy. I had to be more deliberate about environment than I expected.

Proper nouns were also a consistent friction point. Technical terms, names, niche vocabulary, all of it required either spelling out or going back to fix. If your work involves a lot of specialized language, budget time for that.

Slack was awkward. Short, casual messages felt unnatural to dictate. Saying "sounds good exclamation mark" out loud in my kitchen felt a little absurd. I ended up typing Slack and reserving voice for longer-form writing. That felt like a reasonable compromise rather than a failure.

What I Noticed About My Thinking

This was the part I didn't expect. When I type, I edit as I go. Every sentence gets refined slightly before I move to the next one. When I speak, I can't do that. The ideas come out more linearly, more committed. I found myself planning sentences slightly before I said them, which meant I was structuring thoughts more deliberately.

By day five I was producing more words per hour than I had in months. Not polished words, but words. And in writing, volume of raw material matters.

Would I Do It Again

I'm still using voice for most of my long-form writing. I went back to typing for short messages and code, because that genuinely makes more sense. But my default for anything over a paragraph has shifted.

The week forced me to actually learn the tool instead of dabbling. That's probably the real lesson. Voice dictation used occasionally as a novelty does almost nothing. Used consistently as a primary input, it changes how you write.

If you've been curious about dictation, a week of commitment will tell you more than a month of occasional experiments. It's worth the awkward first few days.