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

I have been typing since I was nine. For twenty years, the keyboard has been how I think. So when I decided to go voice-only for a week, I expected to feel slow, clumsy, and frustrated. I was right about two of those.

Day One: Slower Than I Expected

The first morning was rough. I use a Mac for everything, writing, email, Slack, code review notes. Switching to voice felt like writing with my non-dominant hand.

I set up VoiceInk and started with email. Simple enough, I thought. But I kept pausing mid-sentence, waiting for the words to appear, second-guessing whether I'd spoken clearly. I wrote six emails in forty minutes. Normally that takes fifteen.

I almost quit by noon.

Day Three: Something Shifted

By Wednesday, I stopped thinking about the tool. That was the turning point.

I was drafting a project brief, something I'd been putting off for two days. I pressed the key, started talking, and just... kept going. I described the problem, the proposed solution, the risks, the timeline. I didn't stop to reread. I didn't delete and retype. I talked like I was explaining it to a colleague.

When I stopped, there were 600 words on the screen. It had taken eleven minutes.

The brief was not perfect. But it was done, and it was structurally sound. That had never happened to me in eleven minutes before.

What Got Easier

Emails got fast by day four. Once I stopped performing for the microphone, I just said what I meant. My emails got shorter and clearer too, probably because rambling out loud sounds obviously worse than rambling in text.

First drafts became genuinely easier. I have always struggled with the blank page. Talking at it turns out to be much less intimidating than staring at it. I started every draft by saying, out loud, what I was trying to accomplish. That alone usually gave me the first paragraph.

Meeting notes improved. I dictated directly into Notion while someone was talking, capturing the actual words rather than compressed shorthand I'd misread later.

What Stayed Hard

Anything that required precision took longer. Code-adjacent things, command-line notes, anything with special characters or specific formatting. Voice is not faster for structured syntax.

Proper nouns were a recurring problem. VoiceInk handled most of them well, but names of internal tools and people required correction. I kept a text expander running alongside it to help.

I also missed the physical rhythm of typing. There is something about the keystrokes that signals to my brain that I am working. Voice felt more casual, and some days I had to consciously treat it as seriously as I would a keyboard.

The Number That Surprised Me

I tracked my word output that week. I wrote about 18,000 words across all formats, emails, documents, notes, drafts. My average week before that was around 9,000.

I did not work more hours. I worked the same hours and produced twice as much text. A lot of it needed editing, but so does everything I type.

What I Took Back to My Regular Workflow

I did not stay fully voice-only after the week ended. I don't think that's the right approach for most people. Keyboards are still better for some things.

But I kept voice for first drafts, long emails, and any document over 300 words. That alone has changed how I feel at the end of a writing day. My hands are less tired. My drafts start faster. The blank page is less scary when I know I can just talk at it.

If you have been curious about voice dictation but haven't committed to a real test, try seven days. Not one afternoon. Seven days. The first two will be hard. The rest might change how you write.