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

I did not plan to write about this experiment. I planned to quietly fail at it by Wednesday, go back to my keyboard, and never mention it to anyone. Instead, something shifted around day three, and here I am dictating this article.
The setup was simple. For one full work week, I would use voice input for everything I could. Emails, notes, article drafts, Slack messages, meeting summaries. Anything that required producing words, I would speak instead of type. I kept my keyboard for navigation and shortcuts. Pure text generation was voice only.
Day One: Slower Than Expected
Monday was humbling. I use VoiceInk on my Mac, so the mechanics were already familiar. Press a key, talk, words appear. I had used it occasionally for long emails. Using it for everything was different.
I kept stopping mid-sentence. Not because the transcription was wrong, but because I was self-editing out loud the way I normally self-edit while typing, which is to say constantly and destructively. I would say half a sentence, decide it was bad, stop, restart. The voice equivalent of hammering the backspace key.
I produced less on Monday than a normal day. But the words I produced were cleaner than my usual first drafts. That surprised me.
Day Three: Something Clicked
By Wednesday I stopped trying to speak in perfect sentences. I started talking the way I think, which is messier and faster and more honest. The transcription kept up. I started trusting it.
I dictated a 900-word article draft in about 25 minutes. My normal time for a first draft that length is closer to an hour, including all the staring at the screen and rewriting sentences I have not finished yet. The dictated draft needed editing, but it had energy. It sounded like a person.
I also noticed my shoulders. They were not tense. I spend most of my day slightly braced over a keyboard without realizing it. Talking to my laptop while leaning back was a genuinely different physical experience.
What Actually Broke
Some things did not work well. Short, precise text was awkward. Addresses, code snippets, anything requiring exact formatting slowed me down. I cheated and typed those. Technical terms occasionally came out mangled, though VoiceInk handles most of them accurately, the exceptions were annoying.
Slack messages took adjustment. I write terse messages normally. Speaking terse messages felt strange. I ended up slightly more verbose in chat, which my colleagues did not complain about.
What Surprised Me Most
I thought the experiment would be about speed. It turned out to be about volume. I wrote more in that week than in a typical week, not because I was working more hours, but because starting was easier. The activation energy for opening a draft and typing the first sentence is higher than it sounds. Pressing a key and talking out loud felt lower-stakes somehow.
Writer's block is partly a typing problem. When your output mechanism is your voice, there is less room for the paralysis that comes from staring at a cursor.
What I Kept After the Week Ended
I did not go fully voice-only after Friday. But I kept dictating first drafts. I kept using voice for long emails. I kept the habit of reaching for the microphone when I had something complex to explain and not enough patience to type it carefully.
The keyboard is still there. It is good at what it does. But it is no longer my only option, and that small shift changed how I work more than I expected.
If you have VoiceInk already, try one day. Not a week. Just one morning of speaking your drafts and see whether the words come out differently than when you type them. For most people, they do.
Don't type. Speak.
VoiceInk Pro for a full year at $50 instead of $69. Wispr Flow charges $144 a year; this is about a third of that. Mac and Windows, cancel anytime.
Get a year for $50Code READER50 is applied at checkout. Not ready to pay? Download VoiceInk free.