Why Your Hands Are the Bottleneck (Not Your Brain)

You have the idea. It's clear, it's sharp, and you know exactly what you want to say. Then your fingers get involved. By the time you've typed the first two sentences, the thread is already fraying. This is not a discipline problem. It's a hardware problem.

The Numbers Don't Lie

The average person speaks at 120 to 150 words per minute. The average typist hits 40 words per minute. Professional typists top out around 75. Even if you're fast, you're still working at roughly half the speed of your own thoughts.

That gap matters. When output lags too far behind input, your brain starts editing before you've captured anything. You lose the rough, generative part of thinking, the part that actually produces new ideas, because you're too busy managing the keyboard.

What Gets Lost in the Gap

This isn't abstract. Think about the last time you explained something clearly out loud, then sat down to write it and produced something flat. The spoken version was alive. The typed version was careful. Careful is good for editing. It's terrible for first drafts.

The bottleneck also creates a specific kind of fatigue. Typing requires sustained fine motor effort. After a few hours, your hands slow down and your brain follows. You're not mentally tired yet, but your fingers have voted to stop. So you stop.

Voice Changes the Equation

When you dictate, the mechanical constraint disappears. You speak at thinking speed. The words come out faster than your internal editor can object, which is exactly what you want when you're generating, not refining.

Tools like VoiceInk work locally on your Mac, so there's no upload delay, no cloud processing lag. You press a key, speak, and the text appears. The speed is close enough to real-time that it stops feeling like a tool and starts feeling like thinking out loud.

The Editing Objection

The common pushback is that spoken text is messy and needs heavy editing. This is true. It is also true of all first drafts, typed or spoken. The question is not which method produces cleaner raw output. The question is which method produces more raw output, faster, with less friction.

More words generated means more material to work with. A 600-word typed draft that took 45 minutes gives you less to edit than a 1,200-word spoken draft that took 20 minutes. The spoken draft will have more filler. It will also have more good ideas, because you had room to develop them.

When Typing Still Wins

Voice isn't the right tool for everything. Typing is better for short, precise inputs like code syntax, passwords, or specific commands. It's better in noisy environments where a microphone picks up the wrong things. And some people simply think better with their hands on a keyboard. That's real, and it's worth respecting.

But for long-form writing, emails, notes, and documentation, the case for typing as the default input method is weaker than most people assume. It became the default because it was the only option, not because it was the best one.

Breaking the Habit

Switching to voice takes about a week to feel natural. The first sessions are awkward. You'll pause mid-sentence, second-guess your phrasing, and feel the urge to look at the keyboard. Push through it. By day four or five, something shifts. You stop thinking about the input method and start thinking about what you're actually trying to say.

That's the point. The best tool is the one you forget you're using.

If you've never dictated seriously, try it for one writing session this week. Pick something low-stakes, a journal entry, a draft email, a rough outline. See what comes out when your hands are no longer in the way.