Dictation Costs Me 5 Fixes a Paragraph

I use the dictation that comes with my phone and my laptop, in English. Speaking is a little faster than typing for me, not dramatically. The problem is technical words: when a paragraph has tool names or code in it, I am correcting 5 or more things afterwards. That correcting takes back whatever speaking saved. So I still use dictation, but only for short messages now, and I type anything long.

This is about dictation only. I have not used ElevenLabs or anything else that generates a voice, so I have nothing to tell you about that half.

The arithmetic of a small speed gain

Most writing about dictation starts from the claim that speaking is three times faster than typing. For me it was a little faster, and a small gain changes the whole calculation.

If speaking were three times faster, a few corrections would still leave me ahead. At a little faster, the margin is thin enough that 5 fixes wipe it out. And fixing is slower per item than writing, because each fix is a separate operation: find the wrong word, select it, replace it, read the sentence again to check it still means what I meant.

So the honest question is whether your typing is slow enough for the gap to absorb your error rate. Mine is not, which is why this stopped working for me and may not for you.

Why the errors land on exactly the wrong words

The 5 or more corrections are never spread evenly through a paragraph. They cluster on the words that carry the meaning.

Ordinary prose comes out fine. It is the tool names, the library names, the identifiers and the jargon that break, and those are the words a technical sentence exists to deliver. A sentence with its common words right and its one proper noun wrong is worse than a sentence with a few typos, because it reads as fluent and says something false.

That is also why proofreading dictated text is slower than proofreading typed text. A typo looks like a typo. A confidently substituted real word looks like a word I chose, and I have to be reading for meaning rather than for spelling to catch it. That is the kind of error I am most likely to read straight past.

What the documentation does and does not promise

Google's Gboard help page, read on 2 October 2026, is more careful than the marketing around voice input generally is.

It explains the basics plainly: tap the microphone, and say what you want written when it shows "Speak now". For punctuation you say the mark, with "Period", "Comma", "Exclamation point", "Question mark", "New line" and "New paragraph" all listed. To fix a word you touch and hold it, then tap the microphone and say the replacement.

It also states two limits I would want to know first: "Talk-to-text doesn't work with all languages", and punctuation "might not be available in all languages". It notes some steps need Android 7.0 or later. If you write in a language other than English, check it is covered before you plan around this at all. The language gap is the same wall I hit with notetakers in Fireflies and Google Meet, where the Hindi and Gujarati sections of my own calls simply did not arrive.

What I tried before giving up on long text

Two things, and neither moved my number.

I tried speaking more slowly and more clearly around the technical words. It helps a little and it is also the opposite of why you dictate: if I am slowing down to enunciate a library name, I have given up the speed I came for. I tried the voice correction route as well, holding the word and saying the replacement, which the Gboard help describes. For an ordinary word that works. For the words I was actually getting wrong it tends to produce the same wrong word again, because the audio was never the problem.

So the 5 or more corrections stayed 5 or more, and I stopped trying to fix the method and changed what I use it for instead.

Where I still use it

Short messages. A WhatsApp reply, a note to myself, a line of text with no tool names in it. At that length a wrong word is obvious at a glance and fixing it costs seconds, so the small speed gain survives.

Anything long, anything technical, anything that someone else will read without me checking it again: I type, because my correction cost scales with the technical content and my speed gain does not.

If you want to test this on your own work, dictate one real paragraph from your actual job, with the names and terms you actually use in it, and count the corrections. One paragraph is enough. My number was 5 or more, which was enough to settle it.