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

It started as a productivity experiment and became something weirder: a week where I tried to do nearly everything on my Mac with my voice instead of my keyboard. No dramatic injury, no doctor's orders. Just curiosity about whether voice input was actually usable for daily work, or whether it was a niche tool I'd been romanticizing.

The answer was both.

Day One: Slower Than Expected

The first morning was humbling. I dictated an email that should have taken three minutes and it took nine. Not because the transcription was bad, it was surprisingly accurate. The slowdown was me. I kept stopping to think in the middle of sentences, something I never noticed when typing because the pause looks like nothing. Out loud, it felt like failure.

I also kept saying "delete that" when I wanted to backspace, then remembering I wasn't using a voice command system. I was using VoiceInk, which transcribes what you say and drops it into whatever app is active. It's not a full voice control setup. That distinction mattered more than I expected.

Day Three: Something Clicked

By Wednesday I stopped trying to compose perfect sentences before speaking them. I just talked. The editing could come later. This is obvious advice that took me three days to actually internalize.

My word output went up noticeably. I dictated a 900-word article draft in about 25 minutes, which is fast for me. The draft was rougher than usual, more conversational, but it had more ideas in it. I cut it down in editing, but the cutting felt easier than the usual problem of not having enough to work with.

The other surprise: I started dictating notes to myself throughout the day. A thought while making coffee, a sentence I wanted to remember while reading. I'd pull up a notes app, press the hotkey, speak for ten seconds, and move on. The friction was low enough that I actually did it.

What Genuinely Did Not Work

Code. I write occasional scripts and trying to dictate variable names, brackets, and function calls was not worth the effort. Voice and code have a difficult relationship, and I didn't solve it in a week.

Also: anything requiring precise editing. Rearranging paragraphs, adjusting formatting, fixing a specific word three lines up. The keyboard is faster for surgical edits, and pretending otherwise wasted time.

Shared spaces were a problem on day four. I work from home but had a call with my partner in the next room. Dictating out loud felt intrusive in a way typing never does.

What Actually Stuck

After the week ended, I didn't go voice-only. But I kept two habits.

First: dictating first drafts. Any piece of writing longer than 300 words, I now start by talking. The draft is messy but it exists, and a messy draft beats a blank page every time.

Second: voice notes throughout the day. Ideas don't wait for convenient moments. Being able to speak a sentence into a text field in two seconds means I actually capture them.

The week didn't convert me into a voice-first person. But it showed me where voice input earns its place, and where the keyboard still wins. Most people never figure that out because they never seriously try the alternative.

Should You Try It

If you're curious, a full week is a good commitment. Short experiments let you quit before the awkward phase ends. Three days in, most people are still fighting the tool. By day five, they're starting to work with it.

You don't need special hardware. A decent built-in microphone works. Start with something low-stakes, a journal entry, a rough email, a list of ideas. See what happens when your output speed stops being the constraint.

It might not change everything. It changed enough for me.