NeuroDynamic.Tech
Sign inJoin
Assistive toolingillustrative example

Dictation-first writing: tickets, emails and docs by voice

Most dyslexic engineers explain brilliantly out loud and painfully in text. Dictation closes that gap - here's a working setup and the editing pass that makes it professional.

NeuroDynamic.Tech editors · 5 min read ·

If people say "just explain it to me" and you shine, but the written version takes an hour - stop typing first drafts. Speak them.

The core insight

Dictation separates composition (deciding what to say) from transcription (getting it into text). Dyslexia taxes the second, not the first. Let software do the transcription and you keep all your fluency.

Working setups

  • Windows: Win+H voice typing works in any text field, including your ticket system in a browser. Surprisingly good since Windows 11.
  • macOS: built-in Dictation (double-tap a modifier key), or Voice Control for heavier use.
  • Phone first: many practitioners dictate ticket updates into their phone's notes app while walking back from the server room, then paste and tidy at the desk.
  • Self-hosted: Whisper-based tools give excellent accuracy fully offline - worth it if your employer's data policy forbids cloud dictation.

The two-pass method

  1. Talk pass. Say it like you'd explain it to a colleague. Don't stop to fix anything. Rambling is fine.
  2. Tidy pass. Read it back with TTS (hearing catches what eyes skip), cut the padding, fix names and commands by hand - dictation reliably mangles hostnames and CLI syntax, so type those.

Total time is usually a third of typing-first, and the tone comes out more natural.

Where dictation struggles

  • Commands, hostnames, IPs - always type these.
  • Open-plan offices - the phone-notes trick or a quiet room solves most of it. A quiet corner and two minutes of talking beats forty-five minutes of staring at an empty ticket.
  • Highly structured docs - dictate the sections, not the skeleton. Start from a template.

Tried it? Improved it?

Tell the forum what worked and what didn’t: real experience beats recommendations, and the best answers get folded back into this guide with credit.

Discuss in the forumMore in Guides

Related guides

Assistive toolingillustrative example

A runbook template that works at 3am (for every brain)

Diagram first, one action per step, commands in blocks, explicit success criteria. Copy this template and stop writing prose runbooks.

5 min read

Assistive toolingillustrative example

The text-to-speech toolkit for ops work

For many dyslexic technical staff, TTS is the tool that makes the biggest difference. What to use for tickets, docs, email and code review, and how to set speeds.

7 min read