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

I gave myself one rule: no typing for seven days unless the task was technically impossible without it. Passwords, code, spreadsheet formulas. Everything else, voice only.

I expected to feel slow and frustrated. I did not expect to feel embarrassed.

Day One: The Awkwardness Is Real

The first thing I noticed was social. I share an apartment. Dictating felt theatrical, like I was performing work rather than doing it. I moved to a back room and closed the door.

The second thing I noticed was that I had no idea how to start a sentence by speaking it. Typing gives you a kind of privacy. You can write half a thought, delete it, write it again. Speaking forces commitment. You have to begin.

By afternoon, I had written more words than any Monday in recent memory. They were messier. But there were more of them.

Day Three: The Filler Word Problem

I started listening to my own playback and cringed. I said "basically" fourteen times in one email draft. I said "kind of" before almost every strong claim, as if apologizing in advance for having an opinion.

This was useful information. Those habits existed in my typing too. I just could not hear them there.

I started treating dictation like a first draft I would tighten later. That reframe helped. I stopped trying to speak in polished sentences and started speaking in complete thoughts.

Day Four: Something Shifted

I was writing a long piece about product strategy. I paced around the room while I talked. I stopped looking at the screen.

The ideas came faster. Not because I was speaking, exactly, but because I had stopped watching myself write. The self-monitoring that happens when you see your words appear in real time was gone. I was just thinking out loud into VoiceInk, and it was keeping up.

I wrote 2,200 words that afternoon. My previous record for a single sitting was around 900.

Day Five: Practical Friction

Not everything worked. Writing code comments by voice was fine. Writing variable names was not. I kept dictating words the transcription engine heard correctly but that were not the names I had actually used in the codebase.

Emails with specific product names, URLs, or unusual capitalization needed cleanup. That was expected. The ratio of useful output to cleanup time was still strongly positive.

The other friction point was silence. I could not dictate and think at the same time, not deeply. Typing lets you half-think, half-type, which feels productive even when it is not. With voice, the pauses were obvious. I had to actually know what I wanted to say before I said it.

That turned out to be a feature.

Day Seven: The Honest Assessment

At the end of the week I had written roughly 18,000 words across documents, emails, and notes. My wrists felt better than they had in months. I was tired in a different way, more mentally, less physically.

I did not love dictation for everything. Short replies, quick edits, anything that required precise cursor control: I wanted my keyboard back. But for anything that required sustained output, voice was faster, less fatiguing, and surprisingly good at getting me past the blinking cursor problem.

The blinking cursor problem is real. When you type, starting is the hardest part. When you speak, starting is just opening your mouth.

What I Kept

I went back to typing after the week. But I kept dictation for first drafts, for long emails, and for any day when my hands feel tired before noon.

If you have never tried working voice-first for more than an hour, the week-long version is extreme. Start with a single afternoon. Pick something you have been avoiding writing and just talk it out. You might surprise yourself.