Why Your Hands Are the Bottleneck (Not Your Brain)

Most people assume they think slowly. They don't. The average person speaks at 130 words per minute and thinks considerably faster than that. The average typing speed is 40 to 60 words per minute. That gap isn't a minor inconvenience. It's where ideas go to die.

The Math Nobody Talks About

At 50 words per minute, writing 1,000 words takes 20 minutes of pure typing, assuming zero pauses, no backspacing, no staring at the ceiling. Real writing sessions look nothing like that. You stop to reread. You second-guess a word. You fix a typo and lose the thread of the sentence.

At a comfortable speaking pace, 1,000 words takes about 7 minutes. That's not a productivity tip. That's a 65% reduction in time-to-first-draft.

What Gets Lost in the Gap

The problem isn't just speed. It's fidelity. When you think faster than you type, your brain starts editing before your fingers finish. You lose the rough version of an idea before it lands on the page. You sand the edges off thoughts that needed to stay sharp.

Writers know this feeling. You had a sentence in your head, a good one, and by the time you typed the first four words, the rest dissolved. It wasn't writer's block. It was input lag.

Developers feel it differently. A comment that would take 3 seconds to say out loud takes 45 seconds to type, so you skip it. Documentation gets deferred. Context disappears from the codebase.

Typing Is a Skill. So Is Speaking.

We've spent decades optimizing typing. Mechanical keyboards, ergonomic layouts, shortcut training. All of it valuable. But we treat speech like it's the fallback, the thing you do when you can't type. That's backwards.

Speech is the primary interface your brain was built for. You learned to talk before you could write. Your working memory, your sentence construction, your ability to hold an idea and extend it, all of it developed around spoken language first.

Typing is the workaround we invented for machines that couldn't listen. Machines can listen now.

The Cognitive Load Argument

Typing isn't just slow. It's expensive. Every moment you spend thinking about your fingers is a moment you're not thinking about your ideas. Touch typists reduce this cost, but they don't eliminate it. The motor task is always running in the background, consuming some fraction of your attention.

Dictation offloads that task entirely. When you speak, you think about what you're saying, not how to produce it. The cognitive overhead drops, and what's left goes toward the work.

This is especially noticeable in early drafts. The internal editor quiets down when you're talking. You get more raw material on the page, and raw material is what revision needs.

The Accuracy Problem Is Mostly Solved

The old objection to voice-to-text was accuracy. Dragon NaturallySpeaking in 2005 required training sessions and still made embarrassing errors. That era is over.

Modern local transcription, the kind VoiceInk uses on your Mac, runs Whisper-based models that hit accuracy rates above 95% in real conditions, without sending your words to a server. The errors that do slip through are faster to fix than writing the sentence from scratch.

One correction every two paragraphs costs you 10 seconds. Typing everything yourself costs you minutes.

What to Do With This

You don't have to abandon your keyboard. Most voice-first workflows are hybrid. You dictate the thinking parts, the drafts, the notes, the documentation, and type the precise parts, the code syntax, the terminal commands.

The shift doesn't have to be total to be useful. Even moving 30% of your daily writing to voice can save an hour across a workday.

If you've never tried dictating into whatever app you're already in, your Mac has the tools to do it today. Spend 10 minutes with it on something low-stakes, a Slack message, a draft email, a quick note. See what comes out when your fingers stop being the limit.