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

I set a simple rule on a Monday morning: no typing unless absolutely necessary. Passwords, terminal commands, the occasional proper noun the software butchered. Everything else would be spoken.

I expected friction. I got something more interesting.

Day One Was Awkward

The first thing I tried to dictate was an email to a client. I opened it, pressed the key, and said absolutely nothing for four seconds. Typing gives you a kind of cover. You can think while your fingers stall on filler words. Speaking is more exposed.

Once I started talking, though, the email came out in about ninety seconds. It was longer than what I would have typed, but it also said more. I usually edit myself down to efficiency when typing. Speaking, I explained things more fully. The client responded the same day, which was unusual.

By the afternoon I'd dictated six emails, a meeting summary, and a rough outline for a project proposal. My hands hadn't touched the keyboard except to type a password.

The Surprising Part: Thinking Changed

By day three I noticed something I hadn't expected. My thinking during the day felt less fragmented. I wasn't context-switching between ideas and keystrokes. When I needed to capture something, I just said it. Voice notes replaced typed notes. VoiceInk dropped words directly into my notes app mid-thought, without me opening anything new or breaking focus.

I started narrating problems out loud. Not for the transcription, just because speaking had become the default mode for processing. Two bugs I'd been stuck on for days resolved themselves while I was dictating my notes about them.

Where It Broke Down

Day four. Open-plan coffee shop, crowded, loud. Dictation became impractical and mildly antisocial. I typed everything that afternoon. It reminded me that voice has context requirements that typing doesn't. You need to be able to speak without disturbing people or feeling self-conscious.

Code was also genuinely hard. I'm not a full-time developer, but I write scripts regularly. Dictating variable names, brackets, and syntax is a different skill, and I hadn't developed it. I defaulted to typing for anything that required precision formatting.

The Wrist Thing

On day five I realized my wrists didn't hurt. I get a dull ache after long writing days, something I've accepted as normal for years. Five days of minimal typing and it was gone. Not dramatically gone, just quietly absent.

That was more motivating than any productivity gain. Pain you've normalized doesn't register as a problem until it stops.

By Day Seven

My word count for the week was about 40 percent higher than the previous week. Some of that was the experiment making me more intentional about capturing thoughts. Some of it was speed. I also wrote a 1,200-word article in just under twenty minutes by talking through it the way I'd tell it to a friend.

The quality wasn't worse. It was different. More direct, less polished in the first pass, but faster to edit because the structure came out naturally when I spoke it.

What I Kept After the Week Ended

I didn't go fully voice-only. I still type code, messages in noisy places, and anything requiring unusual formatting. But I dictate almost everything else now. Emails, notes, first drafts, documentation, daily summaries.

The switch cost me about two days of awkwardness and returned something I hadn't expected: mental space. Less time on mechanical output meant more time actually thinking.

If you've been curious about voice dictation but assume it's not for serious work, try it for one day. Not forever. Just a day. The friction is real, and it does pass.