May 16, 2026

The Mac Power User’s Guide to Voice Workflows: Slack, Email, Notes, Code Comments

Most dictation guides treat voice as a typing replacement — “speak instead of type, same result.” That misses the point. Dictation is not a slower keyboard. It is a different input modality with different strengths, and the power users who adopt it fastest are the ones who learn which apps reward voice and which ones do not. This guide covers exactly that — with real workflows for the apps you use every day.

The setup: one hotkey, everywhere

Before we get into app-specific workflows, establish one rule: your dictation hotkey must be the same everywhere. I use Control+Option+Space. It is easy to hit, does not conflict with anything I use regularly, and works in every application. Your dictation tool should be global — hold the hotkey, speak, release, and a small preview popup appears with the cleaned text. From there it is one tap to accept (Rewisper copies it to your clipboard by default) and one Cmd+V to paste at your cursor. If you flip the auto-paste setting on, the accepted text drops at your cursor automatically. No app switching, no modal window that steals focus.

This is the difference between dictation as a feature and dictation as a workflow. If you have to switch to a dictation app, dictate, copy, switch back, and paste — you will use it three times and quit. The hotkey must be invisible.

Slack

Slack is the highest-volume text app for most knowledge workers. It is also the app where dictation provides the most immediate value. Slack messages are conversational by design — they are meant to sound like you talking. When you actually talk them, they come out more natural and take a fraction of the time.

Quick replies

For one-line answers (“yes, will take a look,” “deploy is done,” “meeting at 3 works”), dictation might be overkill. But for anything longer than a sentence — status updates, explanations, code review feedback — dictation is faster.

Standup updates

Async standup messages (“yesterday I finished X, today I am working on Y, blocked on Z”) are the perfect dictation use case. They follow a predictable structure, they benefit from conversational tone, and you already know what you need to say. I dictate my standup update in about 20 seconds every morning.

Threads and longer discussions

For technical discussions in Slack threads, I use a hybrid approach: dictate the prose, type any code references, file paths, or command-line snippets. The Slack formatting (backticks, code blocks, bullet lists) is easier to type than to dictate. I speak the explanation and type the markup.

Email

Email is where dictation shines for structure. A good email has a clear arc — context, ask, next steps — and speaking that arc out loud produces a more natural flow than typing it sentence by sentence.

The three-sentence rule

For emails under three sentences, just type them. The cognitive overhead of switching to voice mode is not worth it. For anything longer, dictate. The threshold where dictation beats typing is lower for email than for any other medium because email rewards structured prose, and structured prose is what dictation produces naturally.

External communication

When emailing people outside your company — clients, vendors, users — the tone matters more. Dictation helps here because spoken language is warmer and more direct than typed corporate prose. Your dictated emails will sound more human. The cleanup pipeline removes the filler words but keeps the conversational structure. That is exactly what you want.

Workflow

Open a compose window. Hold the hotkey and dictate the subject line in one pass; release, accept the preview, paste it. Click into the body, hold again, and dictate the body — in one breath if you can, or in paragraph-sized passes with a release between each. Each release gives you a preview popup; accept and paste, or edit inline first. Then do one quick review pass on the full message: check names, dates, and any specific details the model might have gotten wrong. Hit send. Total time for a 200-word email: about 90 seconds.

Apple Notes and personal writing

Apple Notes is the sleeper dictation app. It is always open, it syncs everywhere, and it is where most people capture quick thoughts. Dictation turns it into a proper capture tool.

Brain dumps

When you have a thought you need to capture — an idea for a project, a reminder, a to-do — the friction of opening an app, placing your cursor, and typing is enough to lose it. With dictation: Control+Option+Space, say the thing, release, accept the preview, Cmd+V into Notes. The capture latency drops from seconds to a couple of seconds. You will capture more ideas because the cost of capturing them is lower. (If your captures are short enough that even the preview feels like friction, this is the workflow where flipping on auto-paste pays for itself.)

Meeting notes

During or immediately after a meeting, dictate your notes. Do not try to make them pretty. “Meeting with design team about the onboarding flow. Decision was to simplify the first screen and remove the optional fields. Sarah is going to update the Figma by Thursday. I need to update the API to support the new flow by Friday. Follow-up meeting next Tuesday.” That took 20 seconds to dictate. It is not formatted, but it has everything you need.

VS Code and code comments

As I said in the developer workflow post: do not dictate code. Code is symbolic, not phonetic. Type it. But dictation has two strong use cases inside an editor.

Code comments

A good code comment explains the why, not the what. That explanation is prose, and prose is faster by voice. When you write a function that does something non-obvious, place your cursor above it, type the comment syntax (// or # or /** */), and dictate the explanation. The comment will be clearer because you are explaining it conversationally rather than typing a terse note.

Commit messages

A commit message has a specific format: short summary line, blank line, detailed explanation. Dictating it works surprisingly well. Speak the summary line in one go, pause, then dictate the body. The structure comes naturally because you are explaining your change — which is exactly what a good commit message is.

PR descriptions

This is the highest-value dictation use case for developers. A good PR description takes 5-10 minutes to type. It takes 2 minutes to dictate, and the dictated version is usually better because it reads like a human explaining their work rather than a developer typing bullet points. Open the PR, click the description field, hold the hotkey, walk through what you changed and why, release, accept the preview, paste. Then type any code references or attach screenshots. Done.

Notion, Obsidian, and long-form tools

Long-form writing tools are the natural home for dictation. Notion docs, Obsidian vaults, Google Docs — anywhere you write paragraphs, dictation is faster.

Design docs and RFCs

Technical design documents have a predictable structure: problem statement, proposed solution, alternatives considered, trade-offs, implementation plan. You already know the content — you have been thinking about it for days. Dictating it is just explaining it out loud, and the structure follows naturally from the format. I dictate design docs section by section, with the section headers typed. The body text is all voice.

Blog posts and articles

See the full guide at the linked post below, but the short version is: outline verbally first, dictate the full first draft without editing, run cleanup, then do one thorough editing pass. The separation of drafting and editing is the key insight.

The apps where dictation does not help

Being honest about where dictation fails is as important as knowing where it succeeds. Do not try to dictate in these contexts:

• Terminal. Shell commands are symbolic, abbreviated, and often contain characters that are not phonetic. Type them.
• Spreadsheets. Excel and Google Sheets are about cell navigation and formulas. Dictation adds nothing here.
• Code editors (for actual code). Already covered. Type code. Dictate everything around the code.
• Password fields and forms. Dictation tools process audio to produce text. Never dictate passwords, credit card numbers, or sensitive form fields. The risk is not worth the minor convenience.
• Real-time collaborative editing. When multiple people are editing the same document, dictation creates confusing merge states. Type during collaborative sessions.

Building the habit

The technical setup takes five minutes. The habit takes three weeks. Here is how to make it stick:

1. Force the first week. Every time you reach for the keyboard to type a message, stop and dictate it instead. Even if it is slower. Even if it feels awkward. The only way to build the neural pathway is repetition.
2. Focus on one app at a time. Start with Slack. When Slack dictation feels natural (about a week), add email. Then notes. Then code comments. Expanding app by app is more sustainable than trying to switch everywhere at once.
3. Do not aim for perfection. If you dictate a message and the cleanup misses a word, type the correction. Do not re-dictate. The goal is lower total typing, not zero typing.
4. Review your dictated text. After a week, look back at messages you dictated versus messages you typed. You will notice the dictated ones are longer, clearer, and more conversational. Let that reinforce the habit.

The bottom line

Dictation is not a replacement for your keyboard. It is a complement — a second input modality that is faster for prose and worse for symbols. The power users who get the most out of dictation are the ones who learn which apps reward voice and which ones do not, and switch between keyboard and voice without thinking about it.

The setup is simple: one global hotkey, one on-device dictation tool, one preview-and-paste flow. The habit is harder: three weeks of forcing yourself to speak instead of type, app by app, until it becomes transparent.

Once it does, you will wonder why you ever typed an email.

Read: How I Write 3x Faster Using Dictation (As a Developer Who Hates Voice Assistants) →
Read: Dictation for Writers — How to Draft a Blog Post by Talking to Your Mac →