Why Your Hands Are the Bottleneck (And How to Fix It)

Most people assume they think at the speed they type. They don't. The average typing speed sits around 40 words per minute. The average speaking speed is 130. That's not a small gap, it's a 3x difference that costs you something real every time you sit down to write.

The Gap Between Thinking and Typing

When you type, your brain doesn't slow down to match your fingers. It races ahead, generates ideas, loops back, generates more. Your hands are playing catch-up the entire time. The result is a kind of cognitive friction: you lose thoughts mid-sentence, you simplify ideas to make them easier to type, you stop to fix typos and lose the thread entirely.

Speaking doesn't have that problem. You've been doing it since you were two years old. The motor pattern is automatic. The words come out as fast as you form them.

Typing Speed Has a Hard Ceiling

Professional typists, the people who do this for a living, top out around 120 words per minute. That's after years of deliberate practice. Most knowledge workers sit between 50 and 70 wpm and stay there for decades. Practice helps at the margins, but you're never going to type as fast as you talk.

The ceiling matters because output volume affects output quality. Writers who produce more first-draft material have more to work with. Developers who capture ideas faster lose fewer of them. The bottleneck isn't creativity or intelligence. It's the physical act of pressing keys.

What You Lose in Translation

There's a specific kind of idea that only exists for a few seconds. You're in a meeting, or in the shower, or mid-conversation, and something clicks. The window to capture it is short. If capture requires opening a laptop, finding a document, and typing it out, you lose it. If capture means pressing a key and speaking one sentence, you don't.

This is where tools like VoiceInk make a practical difference. Press a key, say the thing, it appears in whatever app you're using. The friction is low enough that you actually use it, which is the only metric that matters for a capture tool.

Accuracy Is No Longer an Excuse

Five years ago, voice recognition was bad enough that the correction overhead erased the speed gains. That's not true anymore. Local models running on Apple Silicon are fast and accurate. Most people find that dictated text requires fewer corrections than they expect, and the speed advantage more than covers the ones it does require.

The mental shift is accepting that first drafts don't need to be clean. They need to exist. You can fix a messy paragraph. You can't fix a paragraph that never got written because your hands were the bottleneck.

Who This Matters Most For

Anyone who writes more than a few hundred words a day feels this. Writers lose narrative momentum when they type slowly. Developers write sparse comments because full explanations take too long. Managers send clipped emails because they don't have time to type the full context. The problem scales with output demand.

If you've ever thought faster than you could write, you've already felt the bottleneck. You just might not have named it.

What to Do About It

Start small. Pick one writing task you do every day, a morning note, a status update, a reply to a common email, and try dictating it for a week. Don't aim for perfection. Aim for speed.

Most people who try dictation seriously report that the first few sessions feel awkward and the second week feels obvious. The gap between thinking and writing closes, and it turns out there was a lot more thinking happening than the typing ever showed.

If you've never tried dictating your work, there's no better time to find out what your hands have been holding back.