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

I set a simple rule on a Monday morning: no typing unless absolutely necessary. Navigation, passwords, code, fine. But any writing, notes, emails, messages, all of it had to come out of my mouth first.

I expected to feel slow. I did not expect to feel exposed.

Day One Was Humbling

The first thing I tried to dictate was a reply to an email from my editor. It was three sentences. I said them out loud, watched them appear on screen, and immediately wanted to delete everything and start over with a keyboard.

Speaking the words made them feel more real, more committed, than typing ever did. Typing felt like sketching. Dictating felt like signing my name.

That discomfort, I realized by the end of day one, was not a problem with dictation. It was information about how much I had been hiding behind the buffer of the keyboard.

The First Thing That Got Better: Email

By Wednesday I had stopped dreading my inbox. Email had always felt like a chore partly because of the typing. Short responses took effort. Long ones felt like work before the real work.

Dictating replies changed the texture of it. I spoke the way I would talk to the person if they were in the room. The emails got shorter, warmer, and faster. What used to take 25 minutes in the morning was done in eight.

I used VoiceInk for most of this, pressing a key, speaking into whatever field was active, and moving on. No mode switching, no copy-paste, no friction worth naming.

The Thing Nobody Warns You About: Punctuation

By Thursday I had mostly stopped noticing the awkwardness of speaking. But punctuation was still clunky. Saying "comma" and "period" out loud breaks the rhythm of a sentence if you think about it too hard.

The trick I landed on was to stop thinking about punctuation while dictating and add it in a light editing pass afterward. First pass by voice, second pass by hand. That split actually made my drafts better. I stopped over-editing while writing, which is a habit that kills momentum.

Where It Failed

There were real limits. I could not dictate in a coffee shop without feeling self-conscious and without my words colliding with background noise. I could not dictate code, at least not usefully. Slack messages felt fine by voice but anything with a link or a formatted snippet still needed the keyboard.

And late at night, when I was tired, I did not want to talk. I just wanted to type quietly in the dark. I broke my own rule twice and felt no guilt about it.

What Changed After the Week Ended

I did not go fully voice-first after the experiment. That was never really the point. What I did do was stop treating dictation as a curiosity and start treating it as a tool with a specific job.

Long-form drafts: voice. Morning email: voice. Quick notes when I have an idea mid-walk: voice into my phone, pulled up on my Mac later. Editing, code, anything requiring precision: keyboard.

My output went up. Not because I was working more hours but because the first draft step, historically my slowest, got dramatically faster. I was producing 800 to 1,000 word drafts in 15 minutes where before it took 40.

The Surprising Part

The biggest change was not speed. It was that I started finishing things.

The mental overhead of opening a document and facing a keyboard had been quietly killing ideas before they started. Dictating lowered that barrier enough that pieces I had been putting off for weeks got drafted in a single session.

You do not have to go voice-only for a week to find out if it works for you. A single morning, one piece written by speaking instead of typing, is enough to know if there is something here worth building on.