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

The rules were simple. For one week, anything longer than a URL or a password had to be dictated. Emails, documents, Slack messages, notes to myself at 11pm. If it required more than a few words, I had to say them out loud.

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

Day One: The Silence Problem

The first thing I noticed was silence. Not the ambient noise of an office, but the silence inside my own head when I tried to begin a sentence out loud. Typing has always given me a way to stall. You look like you are working even when you are thinking. Speaking exposes the pauses.

My first dictated email took four attempts to start. Not because I did not know what to say, but because I kept waiting for the feeling of being ready that typing had always disguised.

By the afternoon I stopped waiting for it. I just started talking. Most of the time, the sentence sorted itself out by the end.

Day Three: The Output Problem Disappeared

Something shifted on day three. I was drafting a long document and I realized I had been going for twenty minutes without stopping to reread. Normally I edit as I go, which means I am constantly reading backwards instead of writing forwards.

With dictation, going back felt disruptive. So I kept moving. The draft was rough when I finished, but it was finished. The whole thing took forty minutes. The same document the week before had taken most of an afternoon.

I used VoiceInk to drop text directly into my writing app. No intermediate step, no copy-pasting from a transcription window. That frictionless handoff turned out to matter more than I expected.

Day Five: The Unexpected Benefit

My hands felt different. Not dramatically, but noticeably. I have low-grade tension in my forearms most days, the background hum of too many hours on a keyboard. By day five it had quieted down.

I also started thinking differently about structure. When you type, you can bury a bad opening and fix it later. When you speak, you hear it immediately. A clunky sentence sounds clunky out loud in a way it does not always look clunky on screen. I started revising my openings before they landed in the document, just to avoid the sound of them.

Day Seven: What I Kept

I did not become a voice-only person. Code, terminal commands, anything with special characters, those stayed on the keyboard. Typing is precise in ways that matter for certain tasks.

But by the end of the week I had changed the default. Long-form writing, email, notes, anything where the goal is getting thoughts into text, those moved to voice and mostly stayed there.

The output numbers were not subtle. My average daily word count across the week was about 2,400 words. The week before, across similar working days, it was closer to 900. Some of that is draft quality differences. Even accounting for that, the gap was real.

What the Experiment Actually Taught Me

The hardest part of the week was not the technology. VoiceInk worked quickly and accurately enough that it stopped being the thing I thought about. The hardest part was learning to tolerate the exposed feeling of speaking without a script.

That discomfort was worth sitting with. On the other side of it was something I had not had in years: the feeling of writing at the speed of thinking.

You do not need a week-long experiment to find out if it works for you. An afternoon of dictating one thing you would normally type is enough to get a real sense of it. Start with something low-stakes, and just talk.