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

The experiment started as a dare I made to myself. Seven days. No typing for anything that could be spoken instead. Emails, documents, notes, messages, all of it through my voice. I expected to feel like an idiot. I expected to quit by Thursday.

I did not quit by Thursday.

Day One Was Uncomfortable

The first thing I noticed was how strange it felt to speak into silence. Typing has a sound, a rhythm, a physical feedback loop. Speaking into a quiet room felt exposed, even though nobody was listening. I kept my voice low and tentative, which made the transcription worse.

I was using VoiceInk, which runs locally on my Mac. No audio leaves the machine, which helped me relax once I remembered that. By the afternoon I was speaking at a normal volume and the accuracy climbed noticeably.

I wrote three emails that first morning. They were longer than my usual emails. Not padded, just complete. I had stopped editing myself mid-sentence because the friction of fixing a dictated word is lower than rewriting a typed one.

By Day Three, My Pace Changed

Something shifted around Wednesday. I stopped thinking about the tool and started thinking about what I wanted to say. That is the state you want when writing, and I usually have to warm up for 20 minutes to get there. With dictation, the warm-up was shorter because I was not fighting the keyboard to get started.

I dictated a 900-word article draft in about 12 minutes. It needed editing, but the structure was sound and most of the sentences were keepable. Normally a draft like that takes me 45 minutes of typing and deleting and retyping.

I also noticed I was using longer, more complex sentences when I spoke. When I type, I simplify on the way in. When I speak, the full thought comes out before I can second-guess it.

The Hard Parts Were Real

I am not going to pretend it was seamless. Some things were genuinely harder.

Code was off the table. I write some light scripts and markdown, and voice is not the right tool for syntax. I allowed myself to type for code.

Slack messages in an open office would have been awkward. I work from home, so it was not a problem, but I was aware of how social the context of speaking can be.

Editing is still faster with a keyboard. Voice is for generating, not for refining. Once I accepted that and stopped trying to dictate my edits, the workflow made more sense.

What the Week Actually Cost Me

About two hours of adjustment, mostly front-loaded into the first day and a half. After that, I was not slower. I was faster on first drafts, roughly the same on everything else, and noticeably less tired at the end of the day.

My hands, which had been starting to ache by late afternoon for the past few months, felt fine by the end of the week. That alone would have been worth it.

What I Kept After the Experiment

I did not stay fully voice-first. I type this article, for instance. But I changed what I reach for by default. Long drafts, long emails, meeting notes, any time I have more than a paragraph to produce, I speak it first.

The shift is not ideological. It is just the faster path. Speaking at 150 words per minute beats typing at 70, and the quality of my first drafts improved because I stopped editing before I had anything to edit.

If you are curious, try one week. Pick the task where you feel slowest and route it through your voice instead. You might quit by Thursday. Or you might not.