← All articles
Story

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

September 8, 2026·5 min read

I set one rule for myself on a Monday morning: no typing unless absolutely necessary. Passwords, terminal commands, things that genuinely couldn't be spoken. Everything else had to come from my voice. I figured I'd last two days.

I lasted seven, and I'm still mostly voice-first three weeks later.

Day One Was Uncomfortable

The first morning was rough. I felt self-conscious immediately, even alone in my apartment. Speaking out loud to write an email felt theatrical. I kept stopping mid-sentence, second-guessing myself, wanting to just reach for the keyboard.

The email I dictated took longer than it would have typed. But when I read it back, it was warmer and more direct than my usual emails. Less hedging. I hadn't had time to overthink the phrasing.

I filed that away and kept going.

By Day Three, Something Shifted

The self-consciousness mostly dissolved by Wednesday. I stopped performing and started just talking. That's the actual shift, from narrating at your computer to having something closer to a conversation with your work.

I wrote about 2,200 words of a draft that day. My usual output for a full writing day is closer to 800 to 1,000. The words weren't all good. But they were there, and having them there is the whole job at the draft stage.

I was using VoiceInk on my Mac. Press a key, talk, text appears wherever my cursor is. I'd open a document, start speaking, and just walk around the room. Pacing, it turns out, is genuinely useful for thinking. I'd forgotten that.

The Unexpected Problem

Day four introduced a problem I didn't anticipate: I got tired of my own voice.

Not in a dramatic way. More like a low-grade fatigue from continuous speaking. I'd never noticed how much I usually relied on silence when I worked. Some people put on music. I apparently liked quiet and keyboard clicks.

I started building in short breaks. Ten minutes of silence between dictation sessions. That helped significantly. By the end of the week I'd found a rhythm: speak for 25 to 30 minutes, rest the voice for 10, repeat.

What It Did to My Writing

My sentences got shorter. Spoken sentences naturally break sooner than written ones. You don't have as many subclauses when you're talking. Some of that is good, some of it needs editing, but the raw material was more readable than my usual first-draft output.

I also stopped burying the point. When you speak, you tend to lead with what you actually mean. Writing sometimes lets you delay and obscure the main thing because you have time to construct elaborate run-ups. Speaking is less patient.

What I Missed About Typing

Honestly, code. I'm not a developer but I do write markdown, and dictating formatting is genuinely annoying. Saying "hashtag hashtag space" to get a subheading works but feels ridiculous. For structured writing with lots of formatting marks, typing is still faster.

I also missed the edit-as-you-go feeling. Typing lets you revise mid-sentence quietly. Dictating and then deleting out loud has a different energy. I adapted, but I kept notes on what I wanted to fix rather than fixing it live.

What I Kept After the Week Ended

I type now for editing, code-adjacent work, and anything that requires precise structure. I dictate for first drafts, emails, messages, notes, and anything where I'm capturing thought rather than constructing something.

That split feels right. The keyboard is a great editing tool. It's a mediocre transcription tool. Voice is a terrible editing tool. It's a very fast transcription tool.

Using both for what they're actually good at changed how much I get done in a day more than any other habit I've tried.

If you've been curious about dictation, one week is enough time to get past the awkward part and find out if it actually fits you. It's a low-cost experiment. Try it and see.

Stop typing. Start talking.

VoiceInk turns your voice into text in any app. Local, fast, private. Free to start.

Download VoiceInk Free