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

I did not plan to go a full week. I started on a Monday because my right wrist was aching after a long weekend of writing, and I figured I would give it two days of rest. Seven days later, I had not gone back.

Day One: Slower Than Expected

The first morning was humbling. I sat down to write a client email and realized I had no idea how to compose out loud. I kept stopping mid-sentence, second-guessing my word choices, and restarting. What would have taken me three minutes to type took closer to eight.

I almost quit before lunch.

The issue was not the software. I was using VoiceInk, and the transcription was accurate. The issue was me. I had spent twenty years composing text through my fingers, and my brain had no idea how to send the signal a different way. The words were there. The path was not.

Day Three: Something Shifted

By Wednesday I noticed I was no longer stopping to plan sentences before speaking them. I was just talking. The same way I would explain something to a colleague, except it was landing in my document instead of evaporating.

My first drafts were rougher. More conversational, less structured. But they were also longer, and they came faster. A 600-word piece that usually cost me 45 minutes of stop-start typing took about 20 minutes of talking plus 10 minutes of editing. The math was already in voice's favor.

My wrist stopped hurting by day three. That alone was worth something.

The Unexpected Part

I expected to miss typing. I did not expect to notice how much typing had been shaping my thinking.

When you type, you write in short bursts. You pause, assess, continue. The rhythm is staccato. That rhythm turns out to influence how you construct sentences. Short. Punchy. One idea at a time.

Speaking pushed me toward longer, more connected thoughts. I found myself building arguments in real time instead of assembling them piece by piece. Some of that was worse. Some of it was genuinely better writing, the kind that sounds like a person rather than a document.

What Did Not Work

Code was a hard no. Even simple terminal commands felt absurd to dictate. I kept a keyboard within reach for anything technical.

Editing was slower. Voice is for generating, not refining. Once I had a draft, I went back to typing for cleanup. That felt right. The two modes have different jobs.

I also found long Slack threads exhausting to dictate. Short replies, fine. But back-and-forth conversations have a quick, punchy rhythm that typing serves better.

Day Seven: What I Kept

At the end of the week I did not delete my keyboard shortcut for VoiceInk. I also did not stop using my keyboard. What I changed was the default.

Now, anything over a paragraph gets dictated first. Emails, articles, notes, meeting recaps. I type the short stuff and talk the long stuff. The wrist pain has not come back.

The bigger change is mental. I no longer treat the blank page as a place to carefully construct sentences. I treat it as a place to talk until something worth keeping appears. Editing is a separate session, with a keyboard, later.

That separation, generating by voice and refining by hand, is the actual workflow I was looking for without knowing it.

Worth Trying

One week is enough to know whether voice dictation will work for you. The first two days will feel wrong. The third day usually does not.

If your hands are tired, your drafts are slow, or you keep losing thoughts before they make it to the page, it is worth finding out what happens when you just start talking.