I Stopped Typing for a Week. Here Is What Actually Happened.

I told myself it was an experiment. Seven days, voice only. No typing except for passwords and code. I had been using VoiceInk casually for a few weeks, mostly for emails I did not want to sit and write. This time I wanted to push it further and see what broke.

A lot broke. Some things did not, and that was the interesting part.

Day One: Slower Than Expected

The first morning was humbling. I dictated a reply to a client email, and it took longer than typing would have. Not because the transcription was slow, it was not. But I kept stopping, restarting, and adding verbal filler I then had to delete. "So, um, I think what I want to say is" showed up in my draft three times before I caught myself.

I realized I had been half-thinking with my hands. Starting to type a sentence was how I figured out what the sentence was. Without the keyboard, I had to do that work in my head first.

Day Three: Something Shifted

By Wednesday I stopped fighting the silence before speaking. I would pause, find the sentence, then say it. The drafts got cleaner. A 300-word email that took me 20 minutes on day one took about 6 minutes by midweek.

I also noticed I was writing longer paragraphs. When typing, I have a habit of cutting myself short. The physical effort of typing a long sentence makes short sentences feel efficient. Speaking does not have that friction, so I stopped amputating ideas before they finished forming.

The Frustrations Were Real

I want to be honest about what did not work. Proper nouns were a consistent source of annoyance. Software names, people's names, and technical terms required cleanup. I kept a short list of corrections I made repeatedly, and by day four I had a rhythm for catching them.

Noise was also a factor. Working from a coffee shop was possible but required a quiet corner and some awareness of the people nearby. Dictating into a laptop microphone with background noise produced noticeably messier output than dictating at my desk with a decent mic.

And there were moments where I simply did not want to speak. Late in the evening, after calls and meetings, talking felt like one more demand on a depleted resource. I broke the experiment twice during those moments and typed short messages instead. I am not sure that counts as failure.

What I Wrote That Week

I tracked output loosely. Monday through Sunday I produced roughly 11,000 words across emails, a project proposal, meeting notes, and a personal essay I had been avoiding for two months. My typical week runs around 6,000 to 7,000 words. The increase was not all attributable to voice, I had a deadline that week, but I finished earlier than usual and with less of the physical tiredness that comes from long keyboard sessions.

The personal essay surprised me most. I had been stuck on it. When I dictated the opening section instead of typing it, I got through two paragraphs without stopping to second-guess them. They needed editing. They also existed, which the typed version had not managed to do in three separate attempts.

What Stuck After the Week Ended

I went back to typing. Of course I did. The keyboard is still faster for certain things, short precise inputs, code, anything that requires surgical placement of characters.

But I kept voice for first drafts. That is the change that stayed. Whenever I am starting something from nothing, I speak it first. The draft is rougher and arrives faster, and editing a rough real draft is easier than editing a blank page.

If you have been curious about going voice-first, you do not need to commit to a full week. Start with one type of writing you do every day and dictate it for three days in a row. That is enough time to get past the awkward part and find out what is on the other side.