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

I set a rule on a Monday morning: no typing unless absolutely necessary. Passwords, code, proper nouns that voice gets wrong. Everything else, I would speak. Emails, documents, Slack messages, notes to myself. All of it, out loud.

I expected to feel more productive. I did not expect to feel so strange.

Day One: The Embarrassment Phase

My first dictated email took four minutes. Not because the words were hard to find, but because I kept stopping, second-guessing myself, and restarting. I was performing for no one. There was nobody in the room. But speaking a professional email out loud felt oddly exposed in a way that typing the same words never did.

By midday I had also discovered that I say "so" at the beginning of almost every sentence when I speak. My transcript looked like a ransom note assembled by someone with a very limited vocabulary.

I kept going.

Day Three: The Shift

Something changed on Wednesday. I stopped monitoring myself and started just talking. The emails got shorter and clearer. My notes started sounding like thinking instead of filing. A document I had been procrastinating on for two weeks got drafted in twenty-two minutes because I stopped trying to write it and just explained it out loud instead.

I was using VoiceInk for most of this, pressing a shortcut key and speaking directly into whatever app I had open. The speed was close to real-time. There was no cloud round-trip, no waiting. That immediacy turned out to matter more than I expected. Any lag would have given me time to hesitate.

The Numbers, Roughly

I didn't run a formal experiment. But I tracked my word count each day that week. My typical writing days produce around 800 to 1,200 words of finished or near-finished prose. Wednesday I hit 2,400. Thursday, 2,100. Friday was shorter because I had meetings, but I still cleared 1,500 before noon.

The quality was not perfect. There were run-on sentences, weird repetitions, places where I clearly lost the thread mid-thought. But the raw material was there. Editing a messy draft is a different, easier job than producing nothing.

What Got Harder

Some things genuinely did not work well. Dictating anything with specific formatting, code snippets, or precise punctuation was slow and frustrating. I still typed those. Technical writing with lots of symbols is not a voice-first task, at least not yet.

I also found that noisy environments killed my focus. Not because the microphone couldn't handle it, but because speaking out loud while other sounds compete for your attention is cognitively exhausting in a way that typing quietly is not.

What Surprised Me Most

The biggest surprise was what happened to my thinking, not my output. When I typed, I edited as I went. I would write a sentence, delete half of it, rewrite it, move on. My inner critic and my inner writer were fighting for the same keyboard.

Dictation forced me to keep moving. I couldn't easily backspace a spoken word. I had to finish the thought and then decide later if it was worth keeping. That forward momentum changed the texture of the work. Ideas that would have been quietly deleted at the sentence level survived long enough to turn into something.

Would I Do It Again

I didn't stay fully voice-first after the week ended. But I kept dictating for anything that is fundamentally about generating ideas: first drafts, brainstorming, long emails, this article. Typing stayed for editing, code, and anything requiring precision.

The experiment didn't replace one tool with another. It gave me a clearer sense of which tool fits which job.

If you have never tried dictating your work for a full day, that is the experiment worth running. Not a week. Just one day. The results will probably surprise you.