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

It started as a productivity experiment and turned into something closer to a personality test. Seven days, no typing except for passwords and navigation. Everything else, every email, every draft, every Slack message, had to be dictated out loud.

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

Day One: The Weirdness Is Real

The first thing I noticed was how strange it felt to speak into my computer in a quiet apartment. There is a social muscle you have to build around dictating out loud. Even alone, it felt performative in a way typing never does. I kept lowering my voice, which tanked the accuracy, which annoyed me, which made me lower my voice more.

By afternoon I had adapted. I moved to a room where it felt less odd to speak at a normal volume, set up VoiceInk, and started actually working. The transcription was fast enough that it did not break my train of thought. That part surprised me. I had expected lag. There was almost none.

Day Three: The Emails Problem

Email was where I noticed the biggest shift, and not in the direction I expected. My emails got longer. Not because I was padding them, but because speaking removes the tiny tax that makes you cut the friendly sentence or skip the context. My colleagues mentioned that my messages that week felt different. More conversational. One person asked if I had hired someone to help with communications, which is a strange compliment.

The flip side: short replies were annoying to dictate. Saying "sounds good" out loud felt absurd. I started batching my short replies into one typing session in the evening, which technically broke the rules but preserved my sanity.

Day Five: The Draft That Got Away From Me

On Thursday I dictated a 2,000 word essay draft in one session. I have never typed a 2,000 word draft in one session in my life. I walk away, I check things, I fiddle. Speaking forced continuity. You cannot really pause to second-guess a sentence when your voice is still going. You keep moving.

The draft was messier than what I normally produce at that stage. It was also more interesting. There were ideas in it that I genuinely do not think I would have typed. Speaking does not give you time to talk yourself out of the risky sentence.

Day Seven: What I Kept

By the end of the week, I had a clearer picture of where voice helps and where it does not. Long-form drafts: voice wins. Brainstorming: voice wins. Detailed technical documentation: surprisingly good. Code comments and quick notes: much faster to dictate than type.

Short, precise messages. Anything requiring special formatting or symbols. Situations where you cannot make noise. Those still belong to the keyboard.

The most useful outcome was not a productivity number. It was learning that I self-censor when I type. Not dramatically, not in ways I had noticed before. But the voice drafts had a looseness that my typed work often lacks, and looseness in a first draft is exactly what you want. You can tighten later. You cannot add back the idea you never wrote down.

What I Actually Changed After the Week

I did not go full voice-first permanently. That was never the goal. But I changed my default for first drafts. Articles, memos, any piece of writing that needs to exist and then be shaped: I start by talking now. I use VoiceInk, get the words into the document, and then switch to the keyboard for editing.

The week taught me that I had been using the wrong tool for the creation phase of writing. Keyboards are excellent editing tools. They are patient and precise. But they are not great thinking tools, at least not for me.

If you are curious whether the same is true for you, there is one way to find out. Pick a single afternoon and try speaking your work instead of typing it. You might just find out what you actually think.