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

I typed my last sentence on a Monday morning, then pushed the keyboard to the back of my desk. The experiment was simple: one week, voice only, for everything I'd normally write. Emails, Slack messages, notes, documents. If I needed to produce words, I had to speak them.

By Wednesday I had cheated twice and learned three things I didn't expect.

Day One Was Humbling

The first hour was genuinely rough. I dictated an email to a colleague and said "uh" four times in two sentences. I kept stopping mid-thought to mentally edit, which defeated the whole point. The transcription was accurate. The problem was me.

I was still typing in my head. I'd form a sentence mentally, hold it, then speak it carefully. That's not how talking works. That's how reading aloud works. It took most of the first day to stop doing it.

By the afternoon, something shifted. I stopped thinking in sentences and started thinking in ideas. The sentences worked themselves out on the way out of my mouth.

What Got Better Fast

Email was the first win. I wrote a project update that would normally take me fifteen minutes. It took four. Not because I rushed, but because I stopped rewriting as I went. I said what I meant, and VoiceInk dropped it into Gmail while I was already thinking about the next paragraph.

The output was less polished and more clear. My manager replied within ten minutes, which almost never happens. She said it was easy to follow. I think that's because I explained it the way I'd explain it standing in front of a whiteboard, not the way I'd write it for a performance review.

Notes also got better. My usual approach is to type fragments while half-listening in a meeting. Voice let me capture full thoughts after someone finished speaking. The notes were longer and more useful than anything I'd typed in the same context.

Where It Fell Apart

Code was the obvious wall. I'm not a full-time developer, but I write occasional scripts and work in spreadsheet formulas. Dictating logic is slow and error-prone. That was a typing exception I gave myself without guilt.

The second failure was open offices. I work from home three days a week, but two days I'm in a shared space. Dictating into a laptop in a quiet office feels invasive. I went back to typing on those days and felt the difference immediately. My output dropped, and I noticed.

Short, precise inputs, passwords, search queries, code snippets, are genuinely faster to type. Voice is a tool for prose, not for syntax.

What the Week Actually Proved

I wrote more. Not because I was trying to, but because the barrier was lower. The thing that stops most writing isn't lack of ideas. It's the resistance of sitting down and making your fingers do the work. When I only had to speak, I started more things.

I also wrote differently. My sentences got shorter. My explanations got more direct. I used fewer qualifiers. Reading back through the week's output, it sounded like me in a conversation, not me performing professionalism.

The cheating, twice I silently typed rather than disrupt a quiet moment, felt like a loss. Not because of the rule, but because I noticed how much slower my thoughts came when I went back to the keyboard.

Would I Do It Again

I'm still mostly voice-first, three weeks later. I type when it's the right tool. I dictate when I need volume, speed, or clarity. VoiceInk made the switching cost low enough that I don't think about it. Press a key, talk, done.

The experiment wasn't about proving typing is bad. It was about finding out whether the habit of typing was limiting what I could produce. The answer, for long-form anything, was yes.

If you've been curious, one week is enough time to know whether it's for you. Start smaller. Try one day.