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

I didn't have a dramatic reason to stop typing. No injury, no deadline crisis, no doctor's note. I just wanted to know what would happen. So on a Monday morning, I opened VoiceInk, set it to trigger on a double-tap of my right Option key, and decided that anything longer than a password would be spoken, not typed.

By Tuesday I was ready to quit.

The First Two Days Were Rough

Talking to your computer feels absurd in a way that's hard to prepare for. My first dictated email was a disaster. I said "um" four times, I trailed off mid-thought, and I accidentally said the word "period" instead of actually ending a sentence, which then appeared literally in the text. Classic.

I also work in a shared apartment. My partner, a very patient person, asked if I was on a call. Three times. On Tuesday.

I nearly gave up because my inner editor, the voice that polishes sentences as they arrive, had no mechanism to operate. Typing lets you fix as you go. Speaking doesn't. That terrified me in a way I didn't expect.

Something Shifted on Day Three

By Wednesday afternoon, something clicked. I stopped trying to speak in finished sentences and started narrating my thinking instead. Instead of saying "The report should include a summary of Q3 results," I'd say "Okay so the report, I want a section up top with Q3, revenue and churn, just the highlights, two or three lines max."

It was messier. It was also faster. And when I cleaned it up, the underlying ideas were better because I hadn't strangled them into shape during capture.

I wrote 2,400 words that day. That's not unusual for me on a good day, but Wednesday wasn't a good day. It was a Wednesday.

What Actually Got Easier

Emails got dramatically faster. Not because I spoke faster than I typed, but because I stopped overthinking them. When you type an email, there's a temptation to edit it into something polished before you send it. When you speak it, you say what you mean and move on.

Meeting notes improved. I dictated observations immediately after calls while they were fresh, instead of staring at a blank doc an hour later trying to reconstruct what was said.

Long-form drafts felt different. The prose was rougher on first pass, but there was more of it, and it had a voice that my typed drafts sometimes lack. I sounded like a person.

What Didn't Work

Code. Obviously. VoiceInk is not a code dictation tool and I wasn't using it like one. Anything with special characters, precise syntax, or specific formatting stayed on the keyboard.

Short, fast inputs, passwords, search queries, single words, were still faster to type. I broke my rule constantly for those and felt no guilt.

Open-plan offices would make this hard. I had the luxury of a door.

What I Kept After the Week Ended

I didn't go fully voice-first permanently. That was never the realistic outcome. But I kept dictating emails, first drafts, and any kind of note-taking. Those three categories alone probably cover 60 percent of my daily word output.

My wrists, which had been quietly complaining for months, felt noticeably better by the end of the week. That wasn't the point of the experiment, but it became a reason to continue.

The biggest surprise was how much I'd been using typing as a form of procrastination. The blank page is less scary when you're just talking at it.

If you're curious whether voice dictation would work for you, the only way to know is to try it for a few days. Pick one part of your workflow and go voice-first. Don't fix everything at once. Just open a gap and see what comes through.