Why Your Hands Are the Bottleneck (Not Your Brain)

You have a thought. A sharp one. By the time your fingers finish the previous sentence, the new one has already started fading. This is not a writing problem. It is a hardware problem. Your hands are slow.

The Numbers Are Not Close

The average typing speed is around 40 words per minute. Fast typists hit 70 or 80. Competitive stenographers can reach 200, but they spent years training for exactly that.

Speech is different. A relaxed conversational pace runs 120 to 150 words per minute. You are not trying. You are just talking. That means even a mediocre speaker outpaces a good typist by a factor of two or three.

The bottleneck is not your vocabulary. It is not your ideas. It is the physical act of pressing keys.

What Gets Lost in the Gap

Writers talk about flow states, that condition where sentences arrive faster than you can record them. What breaks flow is almost never a lack of ideas. It is the lag between thinking and typing.

The same thing happens in professional contexts. You finish a meeting with six clear action items in your head. By the time you have opened a notes app and typed two of them, the others are already fuzzy. Not gone, but softened. The precision is gone.

This is not a memory failure. It is a transcription failure.

Speaking Is Not Slower Thinking

Some people worry that dictation will produce worse output because speaking feels less deliberate than typing. The opposite tends to happen.

When you type, you edit as you go. You stop, backspace, reword. That internal editor is useful for polish, but it is expensive during a first draft. It interrupts the generative process before it can build momentum.

When you speak, especially to a tool like VoiceInk that transcribes locally and instantly, the words appear fast enough that you stay in production mode. You fix things later. The draft exists. That is the hard part done.

The Keyboard Is a 150-Year-Old Tool

The QWERTY layout was designed in the 1870s, partly to prevent mechanical typewriter jams by slowing typists down. That constraint no longer exists. The keyboard persists anyway, mostly because it is familiar.

Familiarity is a weak reason to keep a bottleneck. Most knowledge workers spend six to eight hours a day typing. They have accepted the constraint so completely that they do not see it as one.

When Typing Still Wins

This is not an argument against keyboards. Typing is better for certain things: entering passwords, writing code syntax, navigating command lines, filling forms. Precision and brevity favor the keyboard.

But for prose, for notes, for emails, for documentation, for anything where you are generating language in volume, speaking is faster and the gap is not small.

Closing the Gap in Practice

The shift to voice takes about a week to feel natural. The first day is awkward. You will forget what to say mid-sentence. You will speak punctuation wrong. You will feel silly.

By day three, you stop thinking about the tool. By day seven, going back to typing for prose feels like writing with your non-dominant hand.

Tools matter here. If transcription has a two-second lag or requires sending audio to a server, the friction is high enough to break the experience. Local, fast transcription keeps you in the moment. That is what makes the speed advantage real rather than theoretical.

If you have never tried dictating a first draft, even a short one, the gap between what you expect and what actually happens is worth experiencing for yourself.