Many long emails are finished in your head before you start typing them. The typing is what eats the afternoon. You know the points, the tone, even the sentence that opens the second paragraph, and then your fingers have to catch up.
Dictation goes after that gap. It helps with some office work and gets in the way of the rest.
Where talking beats typing
Long emails, reports and first drafts
Take a status email to a client. You already know what you’d tell them if they were standing at your desk, so say it in that order and fix the wording at the keyboard afterwards. Typing adds a delay between the thought and the page, and in that delay people start polishing a sentence they haven’t finished. A report works the same way, one section at a time, and a rough page you can fix beats a blank one you’re polishing in your head.
Notes after a call
The minutes right after a call are when notes are worth the most and when nobody wants to type them. Walk back to your desk and say what was agreed, who owns it and by when. Nothing needs composing, so it comes out fast. Do it before the next meeting starts, because after that the details blur.
Prompts for AI tools
Short prompts tend to get generic answers, and people write short prompts because long ones are tedious to type. Say the background out loud and the tedium goes away. (Whether the answer improves depends on what you say, and no tool fixes that.)
Where it doesn’t help
Anything that means moving around a document or arranging things in a grid is a keyboard job. In practice that covers:
- Editing. Changing one word or moving a sentence is faster with the cursor, every time.
- Tables and spreadsheets: you can say a number into a cell, but building the sheet takes keys and a mouse.
- An open office, where speaking softly with the microphone near your mouth helps and is still a favor you’re asking of the people around you. Ask them.
- Quiet public places such as a train carriage, or a waiting room where everyone would hear your client’s name.
- Thinking while you write.
Some people think by typing. The slow pace of the keys holds them to one thought at a time, and when they stop typing they find they’ve stopped thinking. If that’s you, dictating a muddled thought gives you the muddle faster. I don’t know how common this is, and I can’t give you a test for which kind of writer you are. Try it on a real task and see. A middle route worth trying: type the outline, then dictate the paragraphs under each heading.
Habits that make it work
Speak in whole sentences and the text comes back looking like writing. Ramble in fragments and it comes back as one long run-on. So start talking when you know how the sentence ends. The pause before it costs nothing, and a paragraph at a time is easier to review than a whole page in one go.
Decide the punctuation as you go. Many tools let you say it aloud, and “new paragraph” is the one I’d learn first. Saying the break when you mean it is quicker than hunting for the spot afterwards.
Then edit by keyboard. Treat what you dictated as a draft. Read it once through. Names and numbers need the closest look, and anything that rambles can go. Don’t send dictated text unread.
Put the microphone near your mouth. A basic headset keeps it at a steady distance, which gives the software cleaner audio to work from. If your tool lets you hold a key to talk, do that, because the microphone is only open while you hold it, and that matters when the next desk is on a call.
A two week trial for a small team
Start with three volunteers who want to try it. People assigned to a trial they didn’t ask for tend to find reasons it fails. Run it on one tool, approved by whoever approves software at your company, so nobody ends up running it behind IT’s back. Give anyone without a headset a basic one, and tell them before day one what stays off the microphone: passwords, and anything your clients’ confidentiality terms say shouldn’t leave the building.
Which tool is for your IT lead to decide, and any tool that fits your company’s data rules will do. Dictate Safe is one candidate, and it’s made by Vibhaga Group, which also runs oem.news, so weigh the mention with that in mind. On Mac or Windows you hold a key, talk, and the text appears in whatever app is open. In its normal mode the speech engine runs on your own computer. It works in English only and is a one-time purchase, with no subscription. It comes with 25 free dictations, no account and no card, enough for a first feel of it. For the full two weeks, plan on a license for each of the three volunteers; there’s a 30 day refund window.
On the first two working days, each volunteer times their usual typing on work they do every week, say a long email and a set of call notes. For the rest of the two weeks they dictate the same kinds of work and time that. Pick work that really is long. A two line reply is quicker typed, and counting it will drag the dictated average the wrong way. Write the success list before day one and don’t change it afterwards:
- Minutes from starting a task to a draft they’d send, typed against dictated.
- How much of the dictated text survives. If a volunteer retypes most of it, that tells you more than the timings do.
- Whether they’re still using it in week two. A drop after day three is an answer too.
- Complaints from the people sitting nearby.
- What they chose not to dictate, and why.
At the end of week two, each volunteer reads their own numbers against the list. If two of the three are still dictating and the draft times came down, widen the group. If only one is, ask what got in the way before you spend anything.

