I want to tell you about a number that changed how I work. I had been typing professionally for over a decade. I considered myself reasonably fast. Then one afternoon I measured my actual typing speed: 43 words per minute. Not terrible. Solidly average. But that same afternoon, I measured my speaking speed: 148 words per minute. I was 3.4 times faster with my mouth than with my fingers. And I had been choosing the slow option every single day for ten years.
The Realization
The moment that broke my brain was not the WPM test itself. It was watching the clock while I typed a routine email. The email was three paragraphs, roughly 200 words. It took me almost five minutes, which includes the typing, the backspacing, the rewriting, and the pausing to think. Then I dictated the same email. Forty-five seconds. The dictated version was not just faster. It was better. More natural, more direct, the way I would have said it to someone standing in front of me.
That gap haunted me. Five minutes versus forty-five seconds, multiplied by the dozens of emails, messages, documents, and notes I produce every day. I was leaving hours on the table. Not theoretical hours. Real, reclaimed, usable hours that I could spend on work that actually requires my brain rather than my fingers.
The Math That Changed Everything
Let me lay out the arithmetic because it is what convinced me to commit. I spend roughly two hours per day producing text. Emails, Slack messages, documentation, notes, code reviews, feedback. At 43 WPM, that is about 5,160 words of output per day. At 148 WPM, those same 5,160 words take 35 minutes. Even accounting for pauses, corrections, and moments where I need to think before speaking, I was looking at finishing in about an hour instead of two.
One hour saved per day. Five hours per week. Over 250 hours per year. That is more than six full work weeks. Six weeks of my life, every year, spent moving my fingers instead of just saying the words. The math was so stark that ignoring it felt irresponsible.
Week One: The Awkward Phase
I will not pretend it was smooth from day one. The first time I held down the key and started speaking into a Slack message, I felt ridiculous. My voice came out stiff and formal, like I was recording a voicemail for a bank. The transcription was accurate, but the text sounded nothing like how I normally write. It sounded like how I talk when I am nervous at a job interview.
The bigger problem was that I kept stopping mid-sentence to check the output. Dictate three words, release, read, dictate four more words, release, read. This completely killed the speed advantage. I was dictating at maybe 40 WPM, which is exactly what I was already doing with my keyboard. I almost quit on day two.
What saved me was a simple rule I set for myself: do not look at the output until the entire thought is finished. Hold the key, say the complete sentence or paragraph, release, and only then look. This forced me to trust the tool and to formulate my thoughts before speaking. Within three days, the awkwardness started to fade. By day five, I was dictating at 110 WPM without trying. Not my natural speaking speed yet, but already nearly three times my typing speed.
The Tools: What I Tried Before Finding What Works
I started with Apple's built-in dictation. It is decent, and it is free, which makes it the obvious first step. But it has limitations that became frustrating quickly. The activation is clunky (you have to double-tap a key or click a button). There is a noticeable delay before it starts listening. It struggles with technical vocabulary. And the accuracy, while fine for casual sentences, drops on anything specialized.
I tried a few browser-based transcription tools. They worked for documents but not for system-wide dictation. I could not use them in Slack, in my terminal, in my code editor. I needed something that worked everywhere, in every text field, on every app.
That is when I found Voice Keyboard Pro. The hold-to-speak model clicked immediately. Hold Left Control, speak, release, text appears at the cursor. No mode switching, no activation delay, no fumbling with UI. It worked in every application: VS Code, Slack, Gmail in the browser, Notes, Terminal, even Figma's text fields. The accuracy was noticeably better than built-in dictation, and it handled my technical vocabulary (API endpoints, framework names, abbreviations) without garbling them.
But the feature that sealed it was that Voice Keyboard Pro does not touch my clipboard. It injects text directly into the cursor position using the Accessibility API. After years of losing clipboard contents to dictation apps that paste via Cmd+V, this felt like someone had finally thought through the actual workflow of a person who copies and pastes things dozens of times a day.
Getting Faster: The Breakthrough Moments
Speed came in stages, not a smooth ramp. Here is what I remember.
Week two: I stopped dictating in fragments and started thinking in full paragraphs. Instead of "hold key, say one sentence, release, hold key, say next sentence, release," I would hold the key and say three or four sentences in a row. This was the single biggest speed improvement. My WPM jumped from 110 to 135 overnight.
Week three: I started dictating things I never would have typed. Quick notes to myself, comments on pull requests, journal entries, brainstorming sessions. The friction of typing had been silently killing these activities. I did not realize how many thoughts I was not capturing until capturing them became nearly free.
Week four: I hit my natural speaking pace. 145 to 155 WPM depending on the day and the content. At this point, dictation stopped feeling like a technique and started feeling like a superpower. I could produce a 500-word email in two minutes. I could write meeting notes in real time, while the meeting was happening, without falling behind the conversation. I could brain-dump an entire project plan into a document in ten minutes.
Month One: The Transformation
By the end of the first month, I had dictated over 80,000 words. I know this because Voice Keyboard Pro tracks it. Eighty thousand words. That is roughly the length of a novel. In a month. Without any conscious effort to "write more." The volume increased because the cost of producing text dropped to near zero. When speaking a paragraph takes fifteen seconds, you stop rationing your words.
The time savings were real and measurable. I tracked my daily schedule for two weeks before switching to voice and two weeks after. My text-producing tasks (email, messaging, documentation) went from consuming about two hours per day to about fifty minutes. The other seventy minutes went to deep work, code review, and leaving the office earlier. I did not work harder. I just stopped spending time on the mechanical act of pressing keys.
The Surprising Benefit: Better First Drafts
This was the part I did not expect. When you type, you edit as you go. You write half a sentence, delete it, rewrite it, move a clause, reconsider a word. The backspace key is your most-used key. This produces polished text, but it also produces slow text, and it interrupts your train of thought constantly.
When you dictate, you cannot backspace mid-sentence. You have to commit to your thought and say it. This forces a different kind of thinking: you compose the sentence in your head before speaking it. The result, paradoxically, is that dictated first drafts are often better than typed first drafts. They are more coherent, more direct, and less over-edited. They sound like a human talking to another human, which is exactly what good written communication should sound like.
I noticed this most dramatically in emails. My typed emails used to go through three or four rounds of internal editing before I hit send. My dictated emails go through one, maybe two. They arrive at "good enough" faster because they start closer to what I actually want to say.
Voice Keyboard Pro's Smart Rewrite feature amplifies this. After I dictate a rough paragraph, I can have Voice Keyboard Pro clean it up: tightening sentences, removing filler words, adjusting formality. The combination of fast dictation plus AI cleanup means I produce polished text in a fraction of the time it used to take to type and edit manually.
What Does Not Work Well by Voice
I want to be honest about the limitations because overpromising helps no one.
Code. Writing actual code by voice is awkward. Symbols, indentation, and precise syntax are hard to express verbally. I still type all my code. But I dictate everything around the code: commit messages, pull request descriptions, code review comments, documentation, README files. These account for a surprising percentage of a developer's daily text output.
Highly structured data. Filling out forms, entering numbers, working with spreadsheets. Anything that requires precise positioning or non-text input is still keyboard territory.
Editing existing text. Dictation excels at producing new text. It is less useful for revising existing paragraphs. For editing, I still use the keyboard, mouse, and traditional select-and-retype workflows. That said, I find myself editing less because my dictated first drafts need fewer revisions.
Environments without audio privacy. If you are sitting in a library, on a quiet train, or in a shared room where any sound is disruptive, voice dictation is not practical. I keep my keyboard skills sharp for these situations. But most of my work happens at home or in an office with normal ambient noise, where speaking at a conversational volume is perfectly fine.
Practical Tips for Making the Switch
- Start with Slack and email. These are casual, conversational, and forgiving. Perfect training ground. Do not start by dictating a research paper.
- Commit to full sentences. The temptation to dictate two words at a time will kill your speed. Force yourself to hold the key and say at least one complete sentence before releasing.
- Do not check the output after every dictation. Trust the accuracy and keep going. Review and edit in batches, just like you would with typed text.
- Pick one full day and dictate everything. All emails, all messages, all notes. Full immersion collapses the learning curve from two weeks to about three days.
- Track your WPM. Voice Keyboard Pro shows your words per minute after each dictation. Watching that number climb from 90 to 120 to 150 over the first few weeks is genuinely motivating. It turns the learning curve into a game.
- Wear a headset. Even a basic one. It improves mic quality, reduces background noise pickup, and signals to people around you that you are working. This eliminates most social awkwardness.
- Add your custom vocabulary. If Voice Keyboard Pro stumbles on a word you use frequently (a product name, a colleague's name, a technical term), add it to your custom vocabulary. This is a one-time fix that pays dividends forever.
Six Months Later: The Results
It has been six months since I made the switch. Here is where I am now.
I dictate roughly 70% of my daily text output. The other 30% is code, form fills, and situations where I cannot speak. My average dictation speed is 152 WPM, which is close to my natural speaking pace. I produce more text per day than I did before, but I spend less total time doing it. The quality of my first drafts has improved because I think in complete sentences before speaking them.
The time savings have compounded in ways I did not anticipate. It is not just about producing text faster. It is about removing the friction that prevented me from producing text at all. I write more documentation now because it takes five minutes instead of twenty. I give more thorough code reviews because writing detailed feedback is no longer a time tax. I respond to emails the same day instead of letting them pile up because each reply takes thirty seconds instead of three minutes.
My keyboard is not gathering dust. I still type code, edit text, and use shortcuts for navigation and commands. But for producing new prose (which is the majority of what knowledge workers actually do all day) my voice is faster, easier, and produces better results than my fingers ever did.
The gap between 40 WPM and 150 WPM is not a marginal improvement. It is a category change. If someone told you there was a tool that could make you three times faster at a task you perform for two hours every day, you would adopt it immediately. That tool is your voice. You just need software that gets out of the way and lets you use it.
Frequently Asked Questions
How long does it take to get comfortable with voice dictation?
Most people feel natural with voice dictation within one to two weeks of daily use. The first three days are the hardest as you adjust to speaking text aloud. By the end of the first week, dictation starts to feel as automatic as typing. Within a month, most users actively prefer voice for the majority of their text input.
Can I really speak at 150 WPM?
Yes. The average conversational speaking speed is 130 to 150 words per minute. Most people naturally speak in this range without any training. When dictating, you may start closer to 100 WPM as you adjust to the format, but within a few weeks you will reach your natural speaking pace. Some users consistently dictate at 160 to 180 WPM.
What about coding and technical writing -- can I dictate those?
Technical prose like documentation, code comments, and commit messages work extremely well by voice. Actual code with syntax symbols is less suited to pure dictation, though Voice Keyboard Pro's profession detection helps with technical vocabulary. Most developers use voice for prose and keyboard for code, which still captures a significant portion of their daily text output.
Is voice dictation practical in an open office?
More practical than you might think. You do not need to project your voice. Speaking at a normal conversational volume, or even slightly quieter, works well with modern microphones. Voice Keyboard Pro's voice isolation feature filters out background noise and other speakers. Many users wear a headset, which both improves mic quality and signals to colleagues that they are focused. Read more about how the voice isolation technology works.
Ready to Try It?
If you spend any meaningful part of your day producing text, you owe it to yourself to try voice. Download Voice Keyboard Pro, set aside thirty minutes, and dictate everything during that window: emails, messages, notes, whatever comes up. You will feel awkward for about ten minutes. Then you will feel fast. Then you will wonder why you waited so long. Your voice has always been your fastest input device. You were just not using it.