Product managers are professional writers who rarely think of themselves that way. On any given day, a PM produces thousands of words across product requirement documents, Jira tickets, Slack threads, emails to stakeholders, meeting notes, and roadmap updates. The writing never stops, and it is almost never the deep, focused kind. It is fragmented, context-switching, and urgent. Voice to text changes the economics of all of it.
The PM Writing Problem
Most product managers spend between two and four hours per day writing. Not in long stretches, but in dozens of small bursts: a ticket description here, a Slack reply there, a quick email to the design lead, a comment on a spec. Each piece of writing requires a context switch. You stop thinking about the product problem, start thinking about how to phrase it, type it out, fix the typos, and move on. The typing itself becomes a bottleneck, not because you are slow at it, but because the mechanical act of typing interrupts the flow of your thinking.
This is where voice input fundamentally changes the workflow. When you speak your thoughts instead of typing them, you stay in the thinking mode. You explain the user story the way you would explain it to a colleague standing at your desk. The words come out more naturally, the reasoning is clearer, and the whole process takes a fraction of the time.
Drafting PRDs by Voice
Product requirement documents are the highest-stakes writing most PMs do. A PRD needs to be clear, comprehensive, and precise. It also needs to get written, which is where many PRDs die. The blank page problem is real: staring at an empty Google Doc trying to write the perfect problem statement is paralyzing.
Voice dictation solves the blank page problem by letting you talk through the document. Open your PRD template, hold the Steno hotkey, and start talking. Describe the problem you are solving and why it matters. Release, move to the next section, hold again, and explain the proposed solution. You can draft the core of a PRD in ten minutes this way, because you are not editing as you go. You are capturing your thinking.
The key insight is that a spoken first draft is almost always better than a typed first draft for PMs. When you type, you self-edit constantly, which slows you down and often produces stilted, overly formal prose. When you speak, you explain things the way you would to your engineering lead, which is usually exactly the level of clarity a PRD needs.
Practical Workflow
- Open your PRD template in Notion, Google Docs, or Confluence
- Click into the Problem Statement section
- Hold the Steno hotkey and describe the problem as if explaining it to a new team member
- Release, review, and make minor edits
- Repeat for each section: goals, non-goals, proposed solution, success metrics
- Total time for a first draft: 10 to 15 minutes instead of 45 to 60
Faster Ticket Writing
Jira tickets, Linear issues, Asana tasks, whatever your tracker of choice, they all share the same problem: writing good ticket descriptions takes time, so people write bad ones or skip the description entirely. The result is ambiguous tickets that generate questions, misunderstandings, and rework.
With voice dictation, writing a thorough ticket description takes the same amount of time as writing a lazy one used to. Hold the hotkey, describe the expected behavior, the current behavior, the acceptance criteria, and any context the developer needs. You are talking for maybe 30 seconds, but the resulting description is three or four paragraphs of clear, useful context.
This is especially powerful for bug tickets. Instead of typing "login button broken on mobile," you can dictate: "Users on iOS Safari are reporting that the login button does not respond to taps on the first attempt. It works on the second tap. This started after the 3.2 release. Repro steps: open the app in Safari on iPhone, tap the login button on the landing page, observe that nothing happens on the first tap." That level of detail takes 15 seconds to speak but two minutes to type, so it usually does not get typed.
Slack Without the Typing Tax
Slack is where PMs live, and it is also where the most time gets lost. A PM might send 50 to 100 Slack messages per day, and each one requires dropping what you are doing, thinking about how to phrase a response, typing it, and getting back to what you were working on. The individual cost is small but the aggregate cost is enormous.
Voice dictation turns Slack responses into two-second interactions. Someone asks a question in your channel, you hold the hotkey, answer it naturally, release, and the text appears in the message box. You hit enter and move on. The interaction that used to take 30 seconds now takes five.
This is even more valuable on the go. If you have Steno Keyboard on your iPhone, you can respond to Slack messages while walking between meetings. Tap the mic button on the Steno keyboard, speak your reply, and send. No fumbling with tiny keys or autocorrect mishaps.
Meeting Notes and Follow-ups
After every meeting, there are action items to capture, decisions to document, and follow-up messages to send. Most PMs either take notes during the meeting (which splits their attention) or try to remember everything afterward (which means things get lost). Voice dictation offers a better pattern.
Immediately after a meeting ends, while everything is still fresh, open a new document or your project management tool and dictate the key decisions, action items, and next steps. You can capture the essential content of a 30-minute meeting in two minutes of dictation. Then send the follow-up email by dictating it: "Hey team, here are the key decisions from today's review. We are going with option B for the checkout flow. Design will have mocks ready by Thursday. Engineering will start sprint planning on Monday." Ten seconds to speak, and your entire team is aligned.
Why Steno Works for PMs
Several qualities make Steno particularly well-suited for product management workflows.
The hold-to-speak interaction means you never accidentally dictate something you did not intend to share. In a world of open offices and Zoom calls, this matters. You dictate exactly when you mean to and not a second longer.
Sub-second transcription via Steno's transcription engine means there is no waiting around for your text to appear. You release the key and the words are there. For a PM who is switching between six tools and twelve conversations, even a two-second delay feels like an eternity.
The fact that Steno works in any application means you do not have to change your workflow. It works in Jira, in Notion, in Slack, in Gmail, in Google Docs, in Confluence, in Linear, in whatever tool your company uses. There is nothing to integrate and nothing to configure per-app.
And with Steno available on both Mac and iPhone, you get the same fast voice input whether you are at your desk or between meetings. The iPhone keyboard gives you a dedicated mic button right on your keyboard, so voice input is always one tap away in any app.
Getting Started
If you are a product manager who writes more than you would like to (which is all of you), voice dictation is the single biggest productivity unlock available. Download Steno for free at stenofast.com for Mac, or get Steno Keyboard from the App Store for iPhone. The free tier gives you enough daily usage to evaluate whether dictation fits your workflow. Pro at $4.99 per month removes the limits.
Start with Slack messages. They are low-stakes, high-volume, and the speed improvement is immediately obvious. Once you are comfortable, move to ticket descriptions, then PRD drafts. Within a week, you will wonder how you ever typed all of that by hand.
The best PRDs are not written, they are explained. Voice dictation lets you capture the clarity of a verbal explanation without losing it in translation to the keyboard.