Picture this: you need to write an SOP. You open a blank doc. The cursor blinks. Twenty minutes later, you’ve written exactly nothing.
That’s exactly where the original poster started. Then they hit record instead. Four minutes of rambling out loud about a process they already knew cold. Transcribed it. Pasted it into Claude with a specific prompt. What came back was a polished, complete SOP ready to hand to someone. The same day. Zero rewrites needed.
The recipient had zero questions. Total time from voice memo to delivery: six minutes. I came across this in r/PromptEngineering and honestly haven’t stopped thinking about it since.
🧠 Why This Works So Well
The bottleneck in writing SOPs isn’t knowledge. It’s translation. You already know the process. The hard part is converting what’s in your head into clear, structured written words.
Talking is effortless. Documentation feels like work. So the move here is simple: record yourself, let AI handle the structure, and get out of your own way.
One commenter in the thread said it perfectly: “You just discovered that your brain works better when talking than typing, which is wild considering you’ve probably spent years forcing yourself to do the opposite.”
That’s exactly it. Talking out loud is the natural state. Forcing it into a blank doc is the unnatural one. We’ve just been trained to think typing is the professional way to do it.
📋 The Exact Prompt That Did It
The original poster shared the full prompt. Drop your raw transcript into the [raw content] section without editing it first. The mess is the point.
Turn this into a complete SOP I can hand to someone on day one. Raw content:
[paste your transcript or rough notes, don’t tidy anything up]Structure:
1. Purpose, what this process covers and why it matters
2. Who this is for
3. What you need before starting, tools, logins, resources
4. Step by step, numbered, clear enough for someone doing this for the very first time
5. Common mistakes and how to avoid them
6. What to do when something goes wrongPlain English throughout.
Bold every heading.
Number every step.
Ready to paste into Notion or Word as-is.
That structure is doing a lot of work. It tells Claude exactly what shape the output should take, which is why what comes back is usable on the first pass.
🛠 How to Run It Step by Step
- Open your phone’s voice memo app. Walk through the process out loud like you’re explaining it to a new hire on their first day. No script. No preparation. Just talk.
- Transcribe the audio. Drop it into any transcription tool. Otter.ai, Whisper, Google Docs voice typing. Accuracy doesn’t need to be perfect.
- Paste the transcript into Claude. Use the prompt above. Put your transcript in the [raw content] section. Do not clean it up first. The filler words, the false starts, the repetition. Claude handles all of it.
- Sanity-check the output. One commenter made a fair point: read through the steps before handing the doc to someone. Claude is solid but can occasionally miss context-specific nuance. A two-minute read catches that.
- Paste into your tool of choice. The prompt asks for output that’s ready to paste into Notion or Word as-is. It usually lands exactly that way.
💡 Tips and Tricks
- Don’t tidy the transcript. The prompt literally says “don’t tidy anything up.” Resist the urge. Cleaning the transcript first just adds time and doesn’t change the output.
- Add a quick context note before your transcript. If the process has important background (software version, team-specific context, access requirements), drop a line before [raw content]. It helps the output hit closer to perfect on the first pass.
- Swap “Notion or Word” for your actual tool. Change the last line to Confluence, Google Docs, Linear, or whatever your team uses. Claude adjusts formatting to match.
- Use this for simple processes too. The original poster said they’ve been running this for every process since. Even short, simple workflows benefit from having something written down that a new person can actually follow.
- Record on the go. Waiting for a meeting to start? Walking to the coffee machine? Those two minutes are enough to cover a short process. The bar for starting is basically zero.
🚀 Your Turn
Pick one process that lives in your head and nowhere else. The one you keep meaning to document but never do. Record yourself explaining it out loud right now. Six minutes from record to finished doc.
Head over to the original Reddit thread to see the full post and how the community reacted to it.
Frequently Asked Questions
Q: How do I make sure Claude doesn’t invent tools or permissions that don’t exist?
Always sanity-check the generated SOP against your actual tech stack and access levels before handing it off. Claude fills logical gaps confidently, but it doesn’t know which tools you actually have or which permissions are real on your system. A quick 2-minute review catches most invented steps.
Q: What if my ramble contradicts itself or I change my thinking mid-way?
Claude handles this well: it synthesizes conflicting thoughts and extracts the core logic, even when you’re second-guessing yourself. If the SOP feels off, it usually means you’ve uncovered a better approach while talking. Re-record with your updated thinking, or edit the output to match your new logic.
Q: Should I transcribe manually or use speech-to-text?
Speech-to-text (Otter, Whisper, or even your phone’s voice recorder) saves time and works great. Minor transcription errors don’t usually matter: Claude is good at inferring intent even with “umms” and rough grammar. Just make sure the transcript is legible enough that you can follow along.
Q: Does this method work for other types of documentation?
Absolutely. The same approach works for guides, training docs, decision frameworks, troubleshooting docs, and more. The prompt structure adapts to whatever you need (Purpose → Audience → Prerequisites → Steps → Common mistakes → Troubleshooting). The key is giving Claude a clear structure to organize your raw thoughts.
I recorded myself rambling for four minutes. Claude turned it into a complete SOP I handed to someone the same day.
by u/Professional-Rest138 in PromptEngineering