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

I set the rule on a Monday morning: no typing except for passwords, code, and proper nouns the software mangled. Everything else, emails, documents, Slack, notes, had to come through my voice. Seven days. I figured I'd last three.

I made it the full week. Here's what actually happened.

Day One Was Humbling

The first hour was rough. I kept instinctively reaching for the keyboard, typing a word or two, then stopping myself. Dictating a simple email took four minutes because I kept second-guessing whether to speak punctuation aloud or let the software infer it.

VoiceInk infers it reasonably well. I learned to trust that and stop narrating every comma. By the afternoon, my emails were coming out faster than usual. Not dramatically faster, but noticeably. The sentences were longer and more direct. I wasn't trimming thoughts to save keystrokes.

The Meetings Changed

By day two, something unexpected happened in my afternoon calls. When I needed to take a note, I just spoke it quietly while the other person was still talking. No switching to a window, no typing sounds, no lost thread. The note appeared in my document and I stayed present in the conversation.

This felt significant. Typing notes during a meeting is always a split-attention task. Speaking them quietly barely registers as an interruption to your own focus. My meeting notes from that week were more complete than usual and took less effort.

What Actually Broke

Day three surfaced the real limits. I needed to write a technical spec with code snippets, precise variable names, and version numbers. Dictation was nearly useless. Saying "open bracket, close bracket, back-slash, letter n" is slower than typing it by an order of magnitude. I burned twenty minutes on something I'd have typed in four.

I bent the rules and used my keyboard for that document. The experiment wasn't about suffering for its own sake.

Slack was also harder than expected, not because of the dictation but because of the context-switching. Short messages felt over-engineered when spoken. Saying "sounds good, see you then" aloud into a microphone felt strange for two words. Typing would have taken one second.

Day Five: The Flow Appeared

Something shifted midweek. I stopped thinking about the tool and started just talking. A blog post that normally takes me ninety minutes to draft came out in forty. I didn't plan it differently. I just spoke the way I'd explain it to someone across a table, and the structure followed naturally.

This is the thing dictation advocates keep saying and you don't believe until it happens to you. Speaking forces you to commit to a sentence. You can't hover over a word and nudge it. You say the thought, it's there, you move forward. The draft is messier in places, but it exists, which a draft paralyzed by over-editing does not.

What I Kept After the Week Ended

I didn't stay voice-only. The experiment clarified where voice is clearly better and where it isn't. I now dictate first drafts of anything over 300 words. I dictate meeting notes. I dictate emails that require any real thought.

I type Slack messages, code, and anything involving special characters. The keyboard didn't lose its job. It just lost the jobs it was never good at.

The week also fixed a bad habit I didn't know I had. I was editing while writing, which is the fastest way to produce nothing. Dictation breaks that habit because you can't easily go back. You have to move forward.

If you're curious whether voice dictation would work for your actual workflow, a week is enough time to find out. The first two days are awkward. By day four, you'll have an honest answer.