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

I set one rule: for seven days, any continuous prose gets dictated. Emails, documents, Slack messages, notes to myself, all of it. The keyboard stays for code, navigation, and editing. But if I am generating words, I speak them.

I expected it to feel liberating. The first two hours mostly felt awkward.

Day One: The Self-Consciousness Problem

I work from home, so there was no office noise concern. But I still felt strange. Speaking full sentences into a microphone to write a Slack message felt performative, even alone. There is a particular strangeness to hearing your own voice composing thoughts out loud that you normally handle silently.

I pushed through it. By early afternoon, the self-consciousness had faded. I stopped thinking about the act of speaking and started just speaking.

Output that day: faster than usual, rougher than usual. The editing took longer. Expected.

Day Three: The Flow State I Did Not See Coming

Something shifted on Wednesday. I was working on a long document, a project brief that had been sitting in my drafts folder for a week because every time I opened it I typed two sentences and got stuck.

I dictated the whole thing in twenty-two minutes. Not because the ideas were suddenly better, but because I could not stop and second-guess each sentence before moving to the next one. Speaking does not give you that option easily. You finish the thought or you stumble. I kept finishing the thoughts.

The draft needed work. But it existed, which was more than it had managed as a typed document.

Day Four: Where It Broke Down

I tried to dictate a technical email with specific numbers, product names, and structured lists. This was a mistake. Spoken lists are not real lists. Numbers require confirmation. Proper nouns get mangled.

I also discovered that some thoughts are genuinely better typed. Short, precise, syntactically specific things are keyboard territory. Trying to force them into voice created more editing work than just typing would have.

This was useful information. The goal was never to replace the keyboard entirely. It was to use voice where voice is better.

Day Five: The Microphone Setup Matters More Than You Think

I had been using my laptop's built-in microphone. On day five I switched to an over-ear headset I normally use for calls.

The accuracy improvement was noticeable immediately. Fewer corrections, faster output, less frustration. If you are going to dictate seriously, even a mid-range dedicated microphone changes the experience significantly. The built-in mic is fine for testing. It is not fine for a daily workflow.

VoiceInk ran locally the entire time, which meant no audio was going anywhere and the processing was fast. On a machine with a capable chip, the lag between speaking and text appearing is short enough that it stops being a mental obstacle.

Day Seven: What I Kept

By the end of the week, I had a clearer picture of where dictation belongs in my workflow.

Long-form prose: yes, always. First drafts are faster and often more natural when spoken. Emails over three sentences: yes, with a quick edit pass. Slack messages: sometimes, depends on the content. Code and structured data: no.

The self-consciousness from day one was completely gone. Speaking to write felt normal, which I would not have predicted.

What Actually Broke

Honestly, less than I expected. The main casualty was my assumption that typing was neutral, just the way writing works. It is not neutral. It is slow and it interrupts the thought process in ways that are easy to not notice until you remove it.

I did not stop typing after the week. But I stopped typing by default. That shift turned out to be the whole point.

If you have been curious about voice dictation but keep putting it off, one week is enough to find out if it fits. The first two days are the hardest part.