I Stopped Typing for a Week. Here's What Happened.

I didn't plan to make it a full week. I thought I'd try voice dictation for a day, write a quick take on it, and go back to my keyboard. That's not what happened.

Day One: Awkward and Slow

The first morning was rough. I kept stopping mid-sentence because I felt strange talking to my laptop. I'd say a few words, pause, second-guess myself, then try again. My first 300-word email took twelve minutes. Typing it would have taken three.

But I stuck with it. I was using VoiceInk, which runs locally and transcribes almost instantly, so lag wasn't the issue. The issue was me. I wasn't used to committing to words before I saw them on screen.

Day Two: The First Hint of Flow

Something shifted on Tuesday. I was writing up meeting notes and I stopped monitoring my own voice. I just talked. The notes appeared. They were rougher than usual but they were done in half the time, and the thinking in them was clearer. Speaking had forced me to complete my sentences instead of trailing off into bullet points.

Day Three: Email Got Weird

Email by voice is strange at first. You have to say punctuation or trust the tool to infer it. Once I relaxed my grip on perfect phrasing, the emails got better. They sounded like a person wrote them, because in a real sense, a person spoke them. Fewer stiff constructions. More direct language.

I sent an email to a client that I'd been avoiding writing for two days. Dictated it in four minutes. Sent it without rereading it three times. She replied within an hour.

Day Four: The Physical Difference

By Wednesday evening I noticed something I hadn't expected. My shoulders weren't tight. I get tension across my upper back by mid-afternoon most days, a slow accumulation of keyboard hours. Four days into the experiment, it hadn't arrived. I was still typing for code and quick searches, but the sustained prose work was all voice. That reduction was apparently enough.

Day Five: Long-Form Writing

I had a 2,000-word article due Friday. I dictated the first draft on Thursday morning in about 45 minutes, walking around my apartment. The draft was messy. There were repeated phrases and a few garbled sentences. But the structure was solid and the ideas were actually in there, not flattened by the effort of typing.

Editing a messy spoken draft is faster than writing a clean typed one from scratch. I had the final version done by noon.

Day Six: What Didn't Work

Not everything translated. Technical writing with lots of specific terminology needed more cleanup. Anything requiring precise formatting, tables, code blocks, command-line syntax, stayed on the keyboard. And there were moments where I wanted to think quietly and typing felt like the right tool for that. Voice isn't always faster. Sometimes it's just louder.

Day Seven: Deciding What to Keep

By Sunday I'd written roughly 11,000 words across the week. My previous weekly average was around 6,000. Some of that was the novelty effect. Some of it was real. The words had come out faster because I'd stopped fighting the keyboard for the high-volume parts.

I didn't swear off typing. I kept voice for first drafts, long emails, brainstorming, and any time I felt the familiar keyboard resistance setting in. I kept typing for code, edits, and anything that needed precision more than speed.

What the Week Actually Proved

The experiment didn't prove that voice is better than typing. It proved that typing has a cost I'd stopped noticing. Switching to voice made that cost visible by temporarily removing it.

If you've never tried a full day of voice-first work, the week is worth it. You'll find out quickly which parts of your workflow were being held back by the keyboard, and which ones actually belong there.