Why Your Hands Are the Bottleneck (Not Your Brain)

Most people type between 40 and 60 words per minute. Most people speak at 120 to 150 words per minute. That is not a small gap. That is the difference between keeping up with your thoughts and constantly falling behind them.

The Speed Math Nobody Does

Say you average 50 words per minute typing. A 1,000-word email takes 20 minutes. The same email, dictated at 130 words per minute, takes under 8 minutes. Over a week of heavy writing, that gap compounds into hours. Over a year, it becomes days of your life spent waiting for your fingers to catch up.

The problem is not that typing is slow in isolation. It feels fast when you are transcribing something you already know. The problem is that writing is not transcription. Writing is thinking, and thinking does not pause politely while your hands catch up.

What Gets Lost in the Gap

When you speak, you can sustain a train of thought. One idea pulls the next. The rhythm of your own voice keeps you moving forward. When you type, every sentence has a small tax: the physical act of producing it. That tax interrupts the flow just enough to let doubt creep in, to let the internal editor start working before the first draft is even done.

Writers know this feeling. You had a clear idea in your head, started typing it, and by the third sentence you had already revised the first one four times. The draft stalls not because the idea was weak but because the input method kept breaking the thread.

The Keyboard Is a Tool Built for a Different Job

The keyboard was designed for data entry and correspondence. Short bursts, structured input, precise commands. It is excellent at that. It is less excellent at capturing the continuous, associative flow of human thought. A conversation, a brainstorm, a first draft, these are not data entry tasks.

Voice changes the equation. When you dictate, you commit to completing a thought before stopping. You cannot go back and retype a word mid-sentence the same way you can with a keyboard. That constraint, which sounds like a limitation, is actually what keeps the draft moving.

The Accuracy Question

The objection most people raise is accuracy. "Voice recognition makes mistakes." This is true. It also misses the point. A draft with a few transcription errors that you wrote in 8 minutes beats a perfect draft you never finished. Fixing errors takes seconds. Recovering momentum takes much longer.

Modern local tools like VoiceInk have narrowed the accuracy gap considerably. Running on-device means no round-trip to a server, which keeps transcription fast enough that it feels like typing at the speed of speech. The errors that do appear are usually minor and easy to clean up in a pass.

When Typing Still Wins

This is not an argument to throw away your keyboard. Code, terminal commands, precise technical input, these belong to the keyboard. The case for voice is specific: for any task where you are generating original prose, the keyboard is slowing you down.

Emails, documents, notes, first drafts, meeting summaries. These are voice tasks. If you are still typing all of them, you are using the wrong tool for the job.

Try the Experiment

Pick one thing you write every day, a morning update, a project summary, a response to a long email. Dictate it instead of typing it. Time yourself. Read it back. The quality will surprise you, and the speed will surprise you more.

The bottleneck was never your ideas. It was always your hands.