Product managers explain the same things out loud all day: the problem, who has it, why it matters now. Dictation turns that spoken explanation into the first draft of a PRD section, a user story or a release note. It works best for the narrative parts. Type the parts engineers will act on literally: ticket keys, feature-flag names, API fields, version numbers, metrics and requirement words such as "must" and "should". On a Mac, the free built-in Dictation is the place to start.
Publisher note: SuprFlow publishes this guide and is one of the products discussed. Competitor details come from each company's own pages, checked on 1 October 2026. Prices and features change; confirm before you buy.
Which parts of product writing suit voice?
| Writing task | Dictate? | Notes |
|---|---|---|
| Problem statement and context in a PRD | Yes | This is the explanation you already give in meetings |
| User stories | Yes | Use a fixed sentence pattern (below) |
| Acceptance criteria | Draft by voice, then edit | Each criterion must be testable; check every number and negation |
| Release notes | Yes, for the first draft | Then cut to the length your channel needs |
| Ticket descriptions and comments | Yes | Type the title, keys, labels and assignee |
| API names, field names, flags, version numbers, error codes | No | Type or paste them |
| Metrics and targets ("p95 under 300 ms", "+2% conversion") | No | Type them; speech to text guesses number formats |
How do you dictate a user story?
Atlassian's user story guide describes a user story as "an informal, general description of a software feature written from the end user's or customer's perspective", in the form "As a [user], I want [goal] so that [reason]." It adds that acceptance criteria help teams "understand what success looks like and ensures that the story is testable."
That fixed shape suits dictation, because you are filling in three blanks:
- Click in the description field of the ticket or the PRD table.
- Say: "As a returning shopper, I want to see my saved cart on my phone, so that I can finish checking out later."
- Say "new line", then dictate each acceptance criterion as one sentence, starting a new line for each.
- Stop dictation and read the criteria as a tester would. Is each one checkable? Did a "not" or "only" go missing?
Apple Dictation adds commas and full stops automatically in supported languages, according to Apple's Mac User Guide, so you seldom need to say "comma".
Watch the requirement words
Spoken English is loose about obligation; specs should not be. RFC 2119, the IETF document whose keywords some engineering teams borrow for requirement language, defines MUST as "an absolute requirement of the specification", while SHOULD means "there may exist valid reasons in particular circumstances to ignore a particular item". If you say "it should probably handle offline mode" and an AI cleanup step turns that into "it must handle offline mode", you have changed scope. After dictating a spec, search the draft for must, should, may, only, never and not, and confirm each one is what you meant. Whether or not your team uses RFC 2119, the check is the same.
Into Jira, Linear and Notion
Neither Jira, Linear nor Notion is a dictation tool itself, so you use system dictation or a dictation app in their text fields. Our step-by-step guides cover the traps:
- Dictate in Jira and Linear on a Mac covers why Escape can close an issue form and why single-letter shortcuts need the field focused first.
- Dictate into Notion or Obsidian on a Mac covers Notion's own voice features and how they differ from dictation.
A good habit for PRDs: dictate a whole section into a scratch document, edit it, then paste into the shared page. Your rough first pass never appears in a document that others are watching live.
How do you share a spoken draft with engineers safely?
A dictated draft reads fluently even when a detail is wrong, which makes it easy to trust. Before you share:
- Label it. Put "Draft, dictated, not yet reviewed" at the top until you have done the checks below.
- Check identifiers. Every ticket key, endpoint, field name, flag and version number against the source.
- Check numbers and units. Thresholds, percentages, dates, limits.
- Check negations and requirement words as above.
- Check who can see it. Unreleased features, pricing and customer names from research interviews may not belong in a ticket visible to the whole company, a shared channel or an external contractor's workspace.
- Check where your words went on the way. If your dictation tool sends audio or text to a cloud service, your company's policy on unreleased product information applies to that step too. Where does my dictation go? lists the questions.
Start with Apple Dictation
Turn on Dictation in System Settings → Keyboard → Dictation (macOS 27 wording; search for "Dictation" if yours differs), click a text field, press the Microphone key and speak. Apple says it works "anywhere you can type it" and stops after 30 seconds without speech. Setup is in How to use voice to text on a Mac.
When does a dedicated dictation app help a PM?
When you dictate dozens of short bursts a day across tickets, docs, Slack and email, and product names keep coming out wrong.
SuprFlow is one option. It is a menu-bar app for Apple Silicon Macs on macOS 14 or later. Hold the Fn key, speak, release, and it pastes the text into the focused field, in Jira, Linear, Notion, a browser or a code editor. Speech recognition runs on the Mac with a downloaded model, and Default formatting is local cleanup of punctuation, capitalization and numbers, so a spec draft is not rewritten by an AI model unless you turn on an optional formatter. A personal dictionary holds product names and acronyms, and voice snippets can insert text you reuse, such as a PRD heading block. It costs $125 once, with no free tier or trial; company-wide use needs separate terms, so contact SuprFlow.
It does not create tickets, fill in fields such as assignee or priority, record or summarise meetings, or integrate with Jira, Linear or Notion. Your company's policy decides whether it may be used with unreleased product information. We have not run a controlled accuracy benchmark against Apple Dictation.
Questions people ask
Can I dictate a whole PRD?
You can dictate most of the prose. Type the tables, metrics, identifiers and links. Expect to edit spoken prose for length.
What about meeting notes and decisions?
Dictate them yourself right after the meeting, with owners and dates. Dictate meeting action items by voice shows a check for owners and deadlines. Recording a meeting is a separate tool and a separate decision.
Should I let AI clean up my dictated spec?
Only with a tool your company allows for unreleased product information, and check requirement words and numbers afterwards. Cleanup can change "should" to "must" or drop a qualifier.
Can I dictate code or API names?
Type or paste them. Vibe coding by voice on a Mac covers where voice helps with technical prompts and where it does not.
Related guides
- Dictate in Jira and Linear on a Mac
- Dictate into Notion or Obsidian on a Mac
- Dictate in Slack and Teams on a Mac
- Dictate meeting action items by voice
- Teach SuprFlow names and acronyms
- Voice snippets on a Mac