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

I did not plan it as an experiment. My right wrist had been aching for two weeks and my physio said to cut back on typing if I could. So on a Monday morning I opened my laptop, set up VoiceInk, and told myself I would try to get through the day without using the keyboard for anything longer than a URL.

That was day one. I ended up doing the whole week.

The First Two Days Were Awkward

I kept stopping mid-sentence to think. When I type, my fingers pause and nobody notices. When I dictate, silence feels like failure. I caught myself saying "um" and "like" in documents, then cringing when I read them back.

I also had to retrain my instinct to reach for the keyboard every time I wanted to make a note. My muscle memory was deep. Coffee in hand, idea in head, fingers already moving before I had made a conscious decision. Breaking that loop took deliberate effort.

But by the end of day two, something shifted. My sentences were longer. Less choppy. When I typed, I wrote in bursts and then stopped to think. When I dictated, I kept going, because slowing down felt unnatural.

Day Three: Emails Got Easier

Email had always been the thing I dreaded most. Not because the messages were hard, but because starting them was. The blank reply field, the cursor blinking, the weird formality of written communication even with people I knew.

Dictating changed the register immediately. I spoke the way I would have spoken in person, then cleaned it up slightly on the read-through. The emails came out warmer and faster. I sent three difficult messages on Wednesday morning that I had been putting off for days.

One person replied and said it was the clearest email I had ever sent them. I did not tell them it was because I had talked it out loud.

What Actually Broke

Code. I write a little and dictating syntax is painful. Brackets, semicolons, camelCase function names, none of it flows naturally from speech. I ended up typing my code and dictating my commit messages and comments, which was a reasonable compromise.

Slack was also awkward. Short messages felt strange to dictate. I would speak six words, see them appear, and feel like I had used a crane to move a pebble. For quick back-and-forth I went back to typing.

Passwords and form fields were obvious exceptions, but those barely count as writing.

By Friday, My Output Was Up

I tracked my word count loosely across the week. My average on a normal typing week runs somewhere around 1,800 to 2,200 words of usable output per day, including notes, drafts, and messages. By Thursday and Friday of the voice week I was consistently over 3,000.

Some of that was cleanup overhead going down as I got faster. Some of it was the wrist pain fading, which put me in a better mood. But a real portion of it was simply that the gap between thinking and writing had closed.

What I Kept After the Week Ended

I went back to typing for code and short messages. That felt right.

But I kept dictating for first drafts, long emails, meeting notes, and anything that started with a blank page. VoiceInk made that easy because I could stay in whatever app I was already using. No switching, no setup, just press and speak.

My wrist is better. My drafts are longer. My emails are warmer.

I did not expect a forced experiment to change how I work. But the week showed me that the keyboard is a tool I was using out of habit, not because it was always the best tool for the job.

If your wrist hurts, or your drafts feel thin, or you just want to see what writing feels like at speaking speed, try talking instead. One week is enough to find out.