Why Your Hands Are the Bottleneck (Not Your Brain)

You have an idea. It's clear, it's sharp, it's ready. Then you start typing, and somewhere between your brain and your keyboard, it gets ground down. By the time the words appear on screen, the energy is gone. This is not a writing problem. It is a throughput problem.

The Numbers Don't Lie

The average person speaks at 130 to 150 words per minute. Trained speakers hit 180. The average typist does 40 to 60 words per minute. Even fast typists, the ones who brag about their 90 WPM, are still running at half the speed of natural speech.

Thought doesn't wait for your fingers. When your hands can't keep up, your brain throttles back. You start thinking in shorter sentences. You edit while you draft. You lose the thread of an idea because you were still transcribing the last one.

The Hidden Cost of Transcription Mode

Typing forces your brain into two jobs at once: generating ideas and operating your hands. These are not the same cognitive task. One is creative; one is mechanical. Running them in parallel means neither gets full attention.

Writers know this feeling. You're in the middle of a good paragraph and your fingers fumble, or you mistype a word, and the interruption costs you the sentence you were building toward. The idea doesn't wait. It moves on.

Developers feel it differently. You're explaining something complex in a comment or a doc, you know exactly what you mean, but reducing it to typed words slows the explanation until it becomes a summary instead of a real account.

Speaking Lets You Think Out Loud

Speech is how humans have always worked through ideas. Before writing existed, everything was spoken. Your brain is wired for it. When you talk through a problem, you use different cognitive pathways than when you type. You get more of your thinking on the surface, faster.

This is why rubber duck debugging works. It's why explaining a problem to a colleague often solves it before they respond. The act of speaking externalizes your thinking in real time.

Dictation captures that. Tools like VoiceInk let you press a key, speak, and have your words appear wherever your cursor is. No switching apps, no cloud upload, no latency. The gap between thinking and text gets small enough that the two start to feel like one thing.

The Editing Trap

Typists edit while they write. It's almost unavoidable. You see the words forming on screen and your instinct is to fix them. This is one of the worst things you can do to a first draft.

Editing while drafting splits your attention between creation and critique. The internal critic is useful, but not yet. Not during the generative phase. Speaking tends to quiet it. When you're talking, you don't see the words accumulating. You stay in the idea instead of the sentence.

The result is rougher text, but more of it, and faster. You can clean it up later. You cannot recover an idea you lost because your fingers were too slow to catch it.

What to Do About It

You don't have to give up typing entirely. Most people find a hybrid approach works well: dictate first drafts, rough notes, emails, and documentation, then type to edit and refine.

Start with something low-stakes. A quick email, a Slack message, a note to yourself. Get used to the rhythm of speaking your words. It feels awkward for about twenty minutes. After that, it starts to feel obvious.

Your hands are not the problem. They're just the wrong tool for the first part of the job. If you think faster than you type, which you almost certainly do, it might be time to stop making your brain wait.