person using MacBook Pro

Every business hits the same ceiling: it cannot grow past the tasks only one person knows how to do. The standard advice is to document your processes, and the standard outcome is that nobody does, because writing procedures is slow, dull, and always less urgent than the work itself. There is a shortcut that actually holds up. Do the task the way you always do, narrate it into your phone while you work, and convert the recording into text. The transcript is a rough SOP draft that took you zero extra hours to produce.

Why process docs never get written

The math works against writing. Most people type around 40 words a minute when composing, and much slower when staring at a blank template titled “Procedure name, Purpose, Scope.” Speaking runs 130 to 150 words a minute with no blank page involved. Worse, the person who knows the process best is usually the busiest person in the company, which is exactly why the knowledge is stuck with them. Asking your most overloaded employee, or yourself, to sit down and author a manual is how documentation projects die. Asking them to talk while doing what they already do costs nothing.

Narrate the task, keep the details

The capture step needs no new equipment. Open Voice Memos, or whatever recorder app is on the phone in your pocket, hit record, and walk through the process out loud: which login, which spreadsheet, what you check before approving, what you do when the numbers look off. Phones save these recordings as .m4a files, a compact format that holds an hour of talking in a small file, so length is not a concern. The narration catches the details written procedures usually miss, because you mention the exceptions at the moment you handle them instead of trying to remember every edge case at a desk two weeks later.

From recording to a document someone can follow

Raw audio helps nobody, so the recording needs to become text. Run the file through anĀ m4a to text transcription tool and you get the full narration with punctuation in a few minutes. VOMO is one option shaped well for this job: it reads the phone’s .m4a directly, puts no cap on a single recording’s length, generates a summary with the key steps pulled out, and lets you question the transcript afterward, so asking what you said about refund approvals jumps you to that passage. Its free plan covers 30 minutes a week, enough for a procedure or two, and the paid tier costs less than two dollars a week if you decide to document everything. Export to DOCX or Markdown and the draft drops into your wiki, your shared drive, or Notion. Then make one editing pass: cut the filler, number the steps, fix the product names the model guessed at. Twenty minutes of editing versus an afternoon of authoring.

Where the payoff shows up

Documented processes compound quietly. New hires ramp up from written steps instead of shadowing you for a month. You take an actual vacation, because the invoicing procedure no longer lives only in your head. Quality stops depending on who happened to be on shift. And if you ever sell the business, documented operations raise what a buyer will pay, since they are buying a machine that runs rather than a founder who cannot leave. A recorded Q&A works too: have the person taking over a task interview you about it, record that conversation, and transcribe it with speaker labels so the handover becomes a searchable reference.

The honest limits

Dictation is not the right capture for everything. If a process is a series of on-screen clicks, a Loom video or a click-capture tool like Tango documents it better than any narration. Spoken drafts also run wordy, so a transcript is a draft to trim, never a finished manual to publish untouched. And since process recordings can mention customer names and internal numbers, pick a service that encrypts uploads and complies with GDPR rather than a free page you found once. None of those caveats change the core trade: one process narrated per week, converted and trimmed, and within a quarter the business runs on paper instead of memory.