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

I typed my first word in a terminal at age twelve. For the next twenty years, the keyboard was the only way I moved thoughts from my head to a screen. I was fast, around 90 words per minute, and I was proud of it. Then my right wrist started aching, and a friend suggested I try dictating everything for a week. I said I would, mostly to prove it would not work.

Day One: Awkward and Slow

The first morning was uncomfortable. I felt ridiculous speaking to my computer. My sentences came out clunky and over-formal, like I was leaving a voicemail for someone I did not know well.

I dictated three emails and a set of meeting notes. It took longer than typing would have, not because the transcription was slow, but because I kept stopping, second-guessing my phrasing, and starting over. The problem was entirely psychological. I was editing while speaking, which is the same mistake people make when they type.

By the afternoon I had loosened up a little. I started treating it like thinking out loud, which, it turns out, is exactly what it is.

Day Three: Something Shifted

By Wednesday I noticed something I did not expect. My emails were better. Not more polished, but more direct. When you speak a message, you naturally get to the point faster because holding a long preamble in your head while talking is genuinely difficult. The spoken version strips out the filler.

I also wrote a 900-word article draft in about twelve minutes. I timed it. Typing the same draft would have taken me closer to twenty-five minutes, and I would have stopped several times to rearrange sentences mid-thought. Speaking it, I just talked through the argument start to finish and then edited the transcript.

I use VoiceInk for the capture. Press a key, speak, release, and the text lands wherever my cursor is sitting. No switching apps, no copying. It runs locally on my Mac so nothing is sent anywhere. That matters to me for client work.

Day Five: The Hard Parts

Not everything worked well. Writing code comments by voice felt unnatural. Proper nouns and technical terms needed correction constantly. Anything requiring precise formatting, tables, URLs, structured data, was genuinely faster to type.

I also found that I needed a quiet space. Dictating in a coffee shop was not practical, not because the app struggled, but because I felt self-conscious narrating my thoughts six inches from a stranger.

These are real limitations. Voice input is not a universal replacement for typing. It is a better tool for specific tasks.

Day Seven: What I Kept

At the end of the week I went back to typing for most things. But I kept voice for three specific workflows that have stayed with me since.

First, all first-draft writing. I now speak every rough draft and edit the text afterward. The drafts are looser and faster and require less effort to start.

Second, email. Speaking an email is almost always faster than typing one, and the results are consistently more conversational and clear.

Third, quick notes and capture. When I have a thought I want to hold, I press the key, speak a sentence or two, and it lands in my notes app instantly. This has replaced a lot of half-written sticky notes and forgotten ideas.

What the Week Actually Taught Me

The experiment was not about replacing typing. It was about discovering which tasks I was using typing for out of habit rather than because it was the right tool.

A lot of them, it turned out, were habit.

If your wrists ache, or you find yourself staring at a blank document waiting to start, or you just want to write faster without thinking harder, a week of voice-first work is worth trying. The awkward first day passes quickly.