Productivity
Voice-only is the wrong goal
Speaking is better for prose and worse for structure, symbols and compression. Treating dictation as a replacement for the keyboard is how people end up abandoning it.
Last updated
The two failure modes
People go wrong in one of two directions, and both are avoidable.
The enthusiast tries to do everything by voice, including code, spreadsheets and four-word replies. Those fail, and the failures get attributed to dictation generally rather than to using it for the wrong things.
The sceptic tries it once on a badly chosen task — a formatted document, a technical note full of identifiers — concludes it is not accurate enough, and never returns. Both have made the same mistake: treating input method as an identity rather than a choice per task.
The map
| Task | Input | Why |
|---|---|---|
| Email replies | Voice | Prose you already know how to say |
| Chat messages over ten words | Voice | Conversational by nature |
| Chat messages under five words | Type | The shortcut costs more than the typing |
| AI prompts | Voice | Length is the whole benefit |
| First drafts | Voice | Speed matters, structure comes later |
| Revision | Type | Precision and navigation, which speech cannot do |
| Code | Type | Symbol density |
| File paths, URLs, email addresses | Type | Faster and far more reliable |
| Figures, dates, reference numbers | Type | A misheard digit looks entirely plausible |
| Headlines and subject lines | Type | Compression, not composition |
| Tables, lists, formatting | Type | Structure is a keyboard task |
| Explaining why | Voice | The thing that gets cut when typing |
| Notes after a meeting | Voice | Speed against decay |
| Passwords | Type | macOS blocks dictation into secure fields, correctly |
The pattern underneath: speak the meaning, type the specifics. Anything where the exact characters matter is a keyboard task. Anything where the meaning matters and the characters follow from it is a speaking task.
Switching mid-sentence is normal
The thing people do not realise they are allowed to do. A dictation app is typing, so you can interleave freely: speak a sentence, type a file path, speak the rest.
The prompt, mixed
There's a race condition in services/upload.ts where two concurrent requests for the same file id can both pass the exists check. Reuse the advisory lock helper in db/locks.ts rather than adding a mutex.
How it was produced
Spoken: "There's a race condition in" · typed: services/upload.ts · spoken: "where two concurrent requests for the same file id can both pass the exists check. Reuse the advisory lock helper in" · typed: db/locks.ts · spoken: "rather than adding a mutex."
Three switches, no friction, and neither input method was used for something it is bad at. After a fortnight this stops being a decision you make.
What the keyboard is genuinely better at
Worth stating properly, because pages about dictation tend not to.
- Precision. A keyboard produces exactly the characters you pressed. Speech produces the most likely interpretation of a sound.
- Navigation. Moving the cursor, selecting, jumping between fields. Dictation types; it does not drive.
- Revision. Editing is a precision activity and speech has no equivalent of "click here and delete that word".
- Silence. Sometimes the room, the meeting or the person next to you decides it.
- Thinking slowly. Typing's friction is sometimes load-bearing. A difficult reply written at speaking speed is a difficult reply sent too fast.
How the switch becomes automatic
- Put the shortcut somewhere your hands already are If reaching for it is a deliberate act, you will only use it when you have decided to dictate — which is the opposite of fluent.
- Start every prose task by speaking Not because it is always right, but because the default has to be something and prose is where it pays.
- Let yourself stop mid-sentence Switching to the keyboard is not a failure of dictation. It is the workflow.
- Do not evaluate per sentence Judge it over a week. A single bad dictation proves nothing; a week of clearing your replies proves something.
- Keep the read-back Permanently. It is the cost of the speed and it is worth paying.
Questions
Is it worth dictating if I type quickly?
The words-per-minute gain is smaller, and the practical gain is often larger — because for most people the constraint was never typing speed but finding twenty uninterrupted minutes. Speaking fits a ninety-second gap that typing does not.
Can I dictate and type into the same field?
Yes, freely, and it is the normal way to work. A dictation app types, so the receiving application cannot tell which words came from which input.
Should I use voice control instead?
If you need to drive the whole Mac by voice — navigation, selection, menus — macOS Voice Control is the right tool and it is free. A dictation app types text and does nothing else.
What is the single thing I should never dictate?
Numbers that someone will act on: figures, times, dates, reference numbers. A misheard digit is grammatically perfect and visually unremarkable, so it survives the read-back.