Why Your Hands Are the Bottleneck (And What to Do About It)

The average person speaks at 130 words per minute. The average typist hits around 40. That three-to-one ratio means you are losing two thirds of your thinking speed every time you sit down to write. Your hands are not a neutral tool. They are a filter, and a slow one.

The Gap Between Thinking and Typing

When you type, you are not just pressing keys. You are translating. A thought forms, then your brain queues up the letters, then your fingers execute. That chain has latency. For short sentences it is barely noticeable. For long, complex ideas, it creates a kind of cognitive traffic jam where thoughts pile up behind the bottleneck of your fingers.

Writers know this feeling. You have a sentence in your head, fully formed, and by the time you finish typing the first half, the second half has dissolved. You spend the next thirty seconds trying to reconstruct it. Multiply that by an hour of writing and you have lost a significant amount of your best material.

Speed Is Not the Only Problem

Typing speed is the obvious issue, but it is not the only one. Physical effort matters too. Every keystroke is a small muscular action. Over a full workday, that adds up to tens of thousands of individual finger movements. Your hands fatigue before your mind does. You stop writing not because you have run out of ideas but because your hands need a break.

This is especially true for people with repetitive strain injuries. But even without diagnosed RSI, most heavy computer users carry chronic tension in their wrists, forearms, and shoulders. The keyboard is not an ergonomic instrument. It was designed for mechanical typewriters, not for people who write eight hours a day.

What Voice Changes

Speaking removes the translation layer. You think a sentence and it comes out. There is no queuing, no finger choreography. The connection between your mind and the page is about as direct as it gets.

This does not mean voice is perfect. You lose some precision. You catch yourself saying "um" or looping back to restate something. But those are editing problems, and editing is a different job from drafting. The goal of a first pass is to get ideas out fast, not to get them out perfect. Voice is extremely good at that.

Tools like VoiceInk make this practical on a Mac. You hold a key, speak into your microphone, and your words appear wherever your cursor is sitting, whether that is a document, an email, a code comment, or a notes app. The transcription runs locally, so nothing leaves your machine. There is no perceptible lag. It just works like typing, except faster.

The 130 vs 40 Math in Practice

If you write 1,000 words a day by typing, that is roughly 25 minutes of pure keystroke time at 40 words per minute. At speaking speed, the same output takes about 8 minutes. You do not get all 17 minutes back because you will pause, think, and correct. But even at half the theoretical gain, you are saving real time every single day.

For someone who writes a lot, that compounds. A blogger, a developer writing documentation, a manager sending a dozen emails, anyone producing significant text volume starts to feel the difference within a week.

Start Small

You do not have to rebuild your entire workflow to test this. Pick one task you do every day, a morning journal entry, a status update, a reply to a long email, and try speaking it instead of typing it for a week. Note how fast it feels. Note whether your ideas feel more complete.

The keyboard is not going away. But for getting ideas out of your head and onto a screen, your voice is a faster road. It is worth finding out what you have been leaving on the table.