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

I typed my first word on a computer when I was seven. In the thirty years since, I have never seriously questioned whether the keyboard was the right tool. It just was the tool. Then my right wrist started aching, and my doctor said the word I had been ignoring for two years: tendinitis. So I decided to try something I had always dismissed as a gimmick. I would not type for a week.

Day One: Slower Than Expected

I set up VoiceInk on my Mac on a Sunday night. Monday morning, I sat down to write my usual task list and felt immediately, embarrassingly lost. I said "write a task list" and then just sat there. It turns out that I think through typing. The physical act of pressing keys was woven into how I processed what I wanted to say.

I got through my emails by mid-morning, but it took twice as long as usual. I said "um" constantly. I forgot to say punctuation. I ended up with sentences like "the meeting is on Thursday um no Friday send an invite to the whole team period."

Day Three: Something Shifted

By Wednesday I had stopped trying to type with my voice and started actually speaking. The difference sounds subtle but it is not. Typing with your voice means mentally composing a sentence, then reading it aloud. Speaking means just talking.

I dictated a 600-word article that afternoon. It was rougher than my usual first drafts, but it was all there. The structure, the argument, the examples. I spent maybe 20 minutes cleaning it up. Normally a first draft that length takes me 90 minutes, most of which is staring at a half-finished sentence.

Day Five: 4,000 Words Before Lunch

I had a deadline on Friday for a long piece I had been avoiding. I sat down at 8am with coffee and started talking. Not performing, not dictating carefully, just explaining the topic out loud the way I might explain it to a colleague. VoiceInk kept up with me without any noticeable lag. The audio never left my machine.

By noon I had 4,000 words. They needed editing, maybe more than usual, but the hard part was done. The ideas were out. I have never done that in four hours by typing. The closest I have come is about 1,800 words, and I was exhausted after.

What Did Not Work

Code and technical writing were harder. Anything with precise formatting, file names, or jargon needed more cleanup. I also found that short, administrative tasks like filling in forms or renaming files were faster with a keyboard. Voice is not better than typing in every situation. It is much better in specific ones.

I also had to get comfortable with imperfect output. Dictation captures speech, not polished prose. You have to let go of editing in real time. That is a habit change, and it does not happen by day one.

Day Seven: I Did Not Go Back All the Way

The week ended and I did not abandon my keyboard. What I did do was rethink which tasks should default to voice. Long emails, article drafts, meeting notes, brainstorming: all voice now. Forms, code, quick replies: keyboard.

My wrist pain dropped noticeably within the week. That alone was enough to keep going.

The real surprise was not the speed, though the speed was real. It was that talking felt closer to thinking than typing ever did. I got more of my actual ideas on the page, not the edited-down version I had time to type.

If you have been curious about dictation but assumed it was for people with disabilities or for tech enthusiasts with patience to spare, I would push back on that. Give it three days. The awkward part passes faster than you expect.