Voice Typing for ADHD and Focus

Why speaking starts easier

Typing a first sentence asks for a decision before you have anything to react to. Speaking skips that: you produce a rough version in a minute, and reacting to messy text is a much smaller job than inventing clean text.

• There is no blank line to stare at, because words appear as you talk.
• Standing or pacing works with speaking, which helps some people think.
• A finished rough transcript gives you something concrete to change.

None of this is a claim about attention or clinical outcomes. It is a workflow preference. Use it when it lowers the cost of starting and drop it for tasks where typing feels easier.

One shortcut, and nothing to set up

Setup at the start of a session is where short windows die. Ten minutes of preparation once removes the excuse for every session after that.

• On Mac, bind dictation to a shortcut you can hit without looking, and never maintain two competing hotkeys.
• On iPhone, keep exactly one AI keyboard in the globe list so switching takes one gesture.
• Open the target document before the timer starts.
• Decide the engine and settings in advance, so no choices are waiting for you at the start.
• Turn on a Focus mode before the session rather than during it, since notifications arriving mid-sentence cost you the sentence.

Auri Voice works this way on Mac: one shortcut, dictation into whichever app has the cursor, and local cleanup so you are not choosing options mid-thought.

Five minutes, one outcome

Open-ended writing blocks invite drift. A named outcome makes finishing visible, which is the part that keeps you coming back.

1. Say the outcome out loud before you start: “outline the launch email”.
2. Set a five-minute timer.
3. Talk until the timer ends, even if the draft is ugly.
4. Stop when it rings. Do not roll straight into editing.
5. Book the polish pass separately, after a break or later that day.

When you keep skipping the session, the outcome is too big. Shrink it until starting feels boring, then let a few finished small drafts rebuild your trust in the method.

Talk first, edit second

Mixing capture and editing is the failure most people describe as “dictation does not work for me”. A typo appears, you stop to fix it, you lose the sentence you were building, and the session ends.

• Capture: speak continuously, mark gaps aloud, ignore tone and typos.
• Editing: structure first, then sentences, then spelling.
• Use a physical cue if it helps: stand to speak, sit to edit.
• Keep AI tools out of capture. Reach for grammar and paraphrase after you stop talking.

On iPhone, that means dictating the whole reply before you touch the keyboard's cleanup buttons. On Mac, finish the spoken pass before your hands go near the transcript.

Park the gap instead of restarting

Losing the thread mid-draft is routine. The skill is continuing past it, because restarting from the top feels productive and quietly burns the window you had.

• Say “come back to budget” or “name later” and keep talking.
• If you go blank, read the last sentence on screen out loud and continue from there.
• Reuse the same placeholder words every time so they are easy to search for.
• End early if frustration builds. A partial draft beats a deleted one.

During editing, search for your placeholders and fill them one at a time. That turns a stuck draft into a short list of small tasks.

Defaults for low-energy days

A workflow you only use when motivated is not a workflow. Keep a smaller version for the days when the full version is out of reach.

• Two spoken sentences is a valid session. Send them.
• Reuse the same opening line every time so starting is a habit rather than a decision.
• Keep one list of parked threads so you are not holding them in your head.
• Skip the streak thinking. A missed day is a missed day.

Count what you sent, not how long you worked. Sent messages are the only output that matters here, and they are the thing that makes tomorrow's session more likely.

A two-minute weekly check

Once a week, look at what happened and change exactly one thing. Redesigning the system every Sunday is another way to avoid writing.

1. Name three things you shipped by voice this week.
2. Name one session that stalled, and what stalled it.
3. Name one piece of friction: a missing shortcut, the wrong keyboard, a noisy room.
4. Change one default for next week and leave everything else alone.

If a task type never worked by voice, type it. The point is finished writing, not loyalty to the microphone.

FAQ