Short answer: Yes, you can dictate in an open plan office. Speak at quiet conversational volume with the microphone close to your mouth, work in short bursts of one or two sentences rather than long monologues, type anything confidential, and batch your longest writing into a booth, a walk, or a quiet hour.
The single most common reason people abandon voice dictation is not accuracy. It is the room. You install a dictation app, you try it once at your desk, you become aware that the person across from you can hear every word, and the app quietly moves to the corner of your screen where unused apps go to die.
That reaction is reasonable. Open plan offices are already noisy in ways people resent, and nobody wants to become the reason a colleague puts headphones on. But the conclusion most people draw from it is wrong. The choice is not between dictating everything out loud at your desk and dictating nothing. There is a middle setting, and once you find it, most of the writing you do in a workday becomes two to three times faster without your neighbours ever mentioning it.
This guide covers how to find that setting: how loudly you actually need to speak, which writing tasks are worth speaking and which are not, where to put the noisy work, and how to handle the parts of your job that genuinely should not be said out loud.
First, separate the two fears
People say "I can't dictate, I work in an open office" and mean one of two completely different things. It is worth knowing which one is yours, because they have different fixes.
Fear one: disturbing other people. You are worried about the noise you add to a shared room. This is a real, measurable, social problem, and everything in this guide about volume, bursts, and location is aimed at it.
Fear two: being overheard. You are not worried about the noise, you are worried about people hearing the content, or hearing you talk to a computer at all. This one is partly practical (some text really is confidential) and partly self-consciousness, which fades. If your discomfort is mostly the second kind, read our piece on why voice typing feels weird at first, because that feeling has a predictable shape and a predictable end.
Most people have some of both. The good news is that the fixes stack.
The volume rule: proximity beats loudness
The most important technical fact about dictating quietly is this: a microphone close to your mouth hears a whisper better than a microphone across the desk hears a shout.
Sound pressure falls off fast with distance. Speaking into a headset boom mic two inches from your lips gives the transcription engine a strong, clean signal even when you are barely audible one desk away. Speaking at the built-in microphone on a laptop that is sitting behind an external monitor gives it a weak signal plus every keyboard, air conditioner, and conversation in the room, and you will instinctively raise your voice to compensate. That instinct is what makes people loud.
So the first move is not "speak more quietly." It is "move the microphone closer, then speak more quietly." In practice:
- Use whatever headset you already own for calls. If you have a headset for meetings, you already have the right dictation hardware. The boom or the wire mic sits near your mouth, which is exactly what you want.
- Wired beats wireless for accuracy. Bluetooth headsets often switch to a low quality voice profile when the microphone activates, which is why your voice sounds thin to people on calls. It affects dictation the same way.
- Do not buy anything yet. Most people are within a few percent of their best accuracy using the microphone that came with their machine, positioned properly. We went through the whole question in the best microphone for dictation, and the short version is that four of the five biggest accuracy improvements are free.
Once the microphone is close, aim for the volume you would use to say something to the person sitting directly beside you without leaning in. Not a whisper, which strains your voice and drops consonants. Not your phone-call voice, which is the actual problem in most offices. Conversational, low, and steady.
The desk-neighbour test
Before you decide the office is too quiet for this, run one honest test. Pick a low-stakes piece of writing, put your headset on, and dictate three or four sentences at the volume described above. Then look up. If nobody has looked at you, you have your answer. If someone has, drop half a step in volume and try again tomorrow.
People consistently overestimate how much attention their voice draws in a room that already contains calls, keyboards, and conversation. They also consistently underestimate how much a monologue draws. Which brings us to the second rule.
Speak in bursts, not monologues
A sustained two minute stream of speech reads as a phone call to everyone around you, and phone calls are the thing open plan offices are least tolerant of. A six second burst reads as nothing at all. People barely register short utterances in a working room.
This matters more than volume, and it happens to be better dictation practice anyway. Hold your hotkey, say one or two sentences, release, glance at the result, continue. You get four benefits from working this way:
- Errors surface after one sentence instead of after ten, so you never have to rescue a long garbled paragraph.
- You keep control of structure, because you are thinking a sentence ahead rather than improvising a monologue.
- Your pauses give the room a break from your voice, which is most of what "not being disruptive" actually means.
- You can stop instantly when someone walks up to your desk, which is impossible mid-monologue.
Voice Keyboard Pro is built around this rhythm on the Mac. You hold a hotkey, speak, release, and the text appears at your cursor in whatever app you are in. There is no window to open, no recording to save, no session to end. The natural unit of use is a sentence, not a session, which is exactly what an open office needs.
Choose the right work to speak
Not all writing is equally worth dictating, and in a shared room the calculation changes. You want maximum words per second of audible speech. Some tasks are outstanding on that measure and some are terrible.
Excellent candidates
- Long email replies and client updates. The highest ratio of typing saved to noise made. Three hundred words of email is four or five bursts.
- Meeting notes and post-meeting summaries. You have just been talking anyway, and the room expects noise around meetings.
- Ticket descriptions, bug reports, and project updates. Long, structured, low-precision prose that you would otherwise type badly and briefly.
- Code comments, docstrings, commit bodies, and pull request descriptions. The prose around the code, not the code.
- Anything you are currently avoiding writing. The performance review, the handover doc, the postmortem. These get written short because typing them is miserable, and they get written properly when spoken.
Poor candidates in a shared room
- Short replies. "Sounds good, Thursday works" is faster typed and makes you visibly a person talking to a laptop for no gain.
- Anything with heavy syntax. Code, formulas, file paths, and configuration values are faster and safer by hand.
- Precise edits. Changing one word in an existing sentence is a keyboard job.
- Anything confidential. Covered in its own section below, because it deserves one.
A reasonable target for the first week is to speak only the first category and type everything else. That alone tends to move the majority of a knowledge worker's daily word count onto voice while adding perhaps two or three minutes of total audible speech to the room.
Relocate the loudest work
Some writing is long enough that it will not fit into polite bursts. A two thousand word proposal, a full draft of a strategy memo, a long set of interview notes. Do not fight that at your desk. Move it.
The options most offices already have:
- The phone booth or small meeting room. Book twenty minutes. This is not an exotic use of a room designed for one person making noise.
- The quiet hour. Early morning and the tail end of the day are dramatically emptier in most offices. A first draft dictated at 8:30am costs nobody anything.
- The walk. Long form thinking is often better on the move anyway. Our guide to voice typing while walking covers the practical side, including why the phone version matters here.
- The commute, if you drive. Voice notes on the way in, cleaned up at the desk.
This is where having the same tool on both devices stops being a marketing bullet and starts being the actual mechanism. Voice Keyboard Pro's iPhone keyboard has a built in mic button that works inside any iOS app, so the draft you speak into a note on your phone in a booth is the same workflow you use at your Mac, and it lands in whatever app you were already using rather than in a separate transcription silo you have to copy out of.
The confidentiality question
Some text should not be spoken aloud in a room with other people in it, and no amount of volume control changes that. Salary figures. Performance concerns about a named person. Client matters under an NDA. Patient details. Security incident specifics. Anything a competitor sitting behind you would find interesting.
The rule is simple and it is not really about dictation: if you would not say it on a phone call at your desk, do not dictate it at your desk. Type it, or move to a room with a door.
There is a second and separate question people ask here, which is what happens to the words after you speak them. For Voice Keyboard Pro specifically, the servers store only operational pings. No audio and no transcript content. Your text goes to your cursor and lives in your document. That is a meaningful boundary, but it does not solve the room problem, and we would rather be plain about that: the risk in an open office is the human two metres away, not the network.
Dealing with the noise coming the other way
Open offices are not just a place where your voice is a problem. They are also a place where other people's voices are a problem for your accuracy. Background conversation, air handling, and mechanical keyboard clatter all reach your microphone.
Three things help, in order of effect:
- Microphone position. Again. A close mic hears you much better than it hears the room, which is most of what noise rejection actually is.
- Facing away from the loudest source. If there is a permanent conversation cluster, turn your chair or move your machine so your mouth is between the mic and the noise.
- Speaking through the noise rather than over it. Do not raise your volume to compete with a nearby conversation. Wait four seconds for the sentence to end, then speak.
If you are still seeing the specific failure pattern where words from someone else's conversation appear in your text, we wrote up the full diagnostic in fixing dictation in background noise.
Editing without talking more
One trap in a shared room is spending your saved time talking to your computer about the mistakes it made. That is the worst possible ratio of noise to output.
Two habits fix it. First, fix repeat offenders at the source rather than repeating yourself. If the engine consistently mangles a client's name, a product name, or an internal acronym, add it to Smart Vocabulary once as a replacement rule and stop dealing with it forever. Names, jargon, and internal shorthand are the error class that no amount of clearer speech will solve, because the words are simply not common English.
Second, do the repairs with your hands. Dictation produces a draft; the cleanup pass is quick keyboard work and it is silent. Our full guide to editing dictated text lays out the two-pass workflow, and in an open office the second pass being silent is a feature rather than a compromise.
When you do want to change something by voice, Voice Keyboard Pro's Voice Edit lets you speak the change rather than retyping the sentence, which is one short burst instead of a rewrite. Use it for the substantive edits, not the typos.
Talking to your team about it
If you sit in a genuinely quiet, library-style office, have the conversation rather than guessing. It is a thirty second conversation and it almost always goes better than people expect, for two reasons. One, you are asking about something quieter and shorter than the calls that already happen. Two, once colleagues understand you are doing focused work in six second bursts rather than holding a meeting, the perceived nuisance drops immediately.
If the answer is genuinely no, that is useful information too. It tells you your office is a type-at-desk, speak-in-booths environment, and you can structure your day accordingly rather than abandoning a two to three times speed advantage entirely.
What the speed difference actually is
It is worth being concrete about what is being traded for the social friction. Average adult typing sits around 40 words per minute. Professional typists reach 80 to 100. Normal conversational speech runs at 130 to 150 words per minute, and it requires no practice, because you have been doing it since you were four.
Applied to the writing you actually do at work, that difference is not marginal. It is the reason the handover doc gets written properly instead of in bullet fragments, and the reason a long client reply takes four minutes instead of fifteen. The question worth asking is not whether you can dictate everything in an open office. It is whether the twenty percent of your writing that is long, prose-heavy, and non-confidential is worth two minutes of quiet talking per hour. For most people it plainly is.
Frequently asked questions
Can I dictate quietly enough that nobody hears me at all?
Not reliably, and chasing that goal usually backfires. Whispering removes the voiced sound that transcription depends on, so accuracy drops and you end up repeating yourself, which is louder overall than speaking properly the first time. Aim for quiet and brief rather than inaudible.
Do noise cancelling headphones help my colleagues?
No. They help you hear less of the room. What helps your colleagues is your microphone being close to your mouth so that you can speak more quietly, plus short bursts. A headset with a boom does both jobs at once.
Will people think I am on a call and interrupt less?
Often, yes, and this cuts both ways. Some people find the ambiguity useful. Others find it awkward that colleagues hover waiting for a call to end. A brief mention to the people who sit nearest you resolves it.
What if I share a desk with someone who takes constant calls?
Then you are in the easiest possible environment for this and you have been worrying about nothing. A room that already contains continuous speech will not notice a six second burst.
Does dictation work in every app, or do I need a plugin?
On the Mac, Voice Keyboard Pro types at your cursor system-wide, so it works in whatever has focus: your email client, the browser, your editor, your ticketing system. There is nothing to install per app.
What about video calls, can I dictate during a meeting?
Not while unmuted, for obvious reasons. Dictating notes while muted works fine, and is one of the few times an open office genuinely does not care what you say, because you are visibly in a meeting.
The bottom line
The open office objection is real but it is aimed at the wrong target. It rejects a mode of working that nobody actually proposed: sitting at a shared desk narrating documents for an hour. What works instead is quiet, close-mic, one sentence at a time, on the long prose that eats your afternoon, with the confidential material typed and the biggest drafts moved to a booth or a walk.
Try it on one long email tomorrow morning before the room fills up. Voice Keyboard Pro has a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year. One email is enough to tell you whether the room was ever the problem.