The reason your SOPs don’t exist isn’t that you don’t know the process — it’s that writing them from scratch is mind-numbingly tedious, and the version you’d grind out from memory would miss half the edge cases. This workflow inverts the order: AI interviews you, you answer like you’re talking to a colleague over coffee, and AI structures the answers into a real SOP. You then fact-check the AI’s draft against actual tool screens, stress-test edge cases, and publish. First useful version in under 90 minutes — and the next person who runs the process can actually do it.
What this covers
A 4-step AI workflow that interviews you, drafts the SOP, fact-checks it against your own evidence, and gets the first useful version in under 90 minutes. Plus the edge-case walkthrough that prevents “works on the happy path, breaks for everyone else” SOPs.
Who this is for
Team leads documenting how things actually work, ops people inheriting undocumented processes, founders capturing what’s in their head before delegating, hiring managers writing onboarding docs, and anyone who has ever said “let me just do it, it’s faster than explaining”.
When to reach for it
When a process lives only in one person’s head and the next hire has to repeatedly ask “how do you do X?”. When you’re about to delegate something you’ve done 50 times. When you realize you’ve explained the same thing to 4 different people and saved it nowhere.
When this is NOT the right tool
Processes that change weekly — documentation can’t keep up; build self-explanatory tooling instead. Processes with security / compliance constraints requiring direct expert review (financial controls, HIPAA workflows). Single-step “how do I do this once” tasks — those don’t need SOPs, they need notes.
Before you start
- Pick ONE process to document. Batching SOPs tanks quality; one focused 90-minute session beats four parallel half-finished docs.
- Have the actual tool open in another window. You’ll fact-check against live screens, not memory.
- Set a deliverable in mind: “Someone hired tomorrow could execute this on their first try.” That bar drives clarity.
- Decide where the finished SOP lives. Notion, Google Docs, internal wiki — wherever your team actually reads docs.
Step by step
- Ask Claude or ChatGPT to interview you. Use this exact prompt: “You’re a process designer. Ask me 15 questions about how I do [process X], starting with broad context and getting more specific. Wait for my answer between each question.” Don’t try to write the SOP yourself first — the interview surfaces what you’d skip.
- Answer the questions in plain conversation. Don’t edit, don’t polish, just dump. Voice-to-text is great here. Skipped details get filled in by AI’s next question — that’s the whole point.
- Ask AI to draft an SOP in this fixed structure: purpose (1 sentence), when to trigger, prerequisites / inputs, ordered steps, exceptions and edge cases, rollback / recovery, who owns it, when to revisit. Don’t accept a freeform structure — consistency across SOPs matters more than perfect prose.
- Fact-check pass: open the actual tool screens / files mentioned in the SOP. If the SOP says “click Settings then Billing” and the menu is now “Settings then Subscription”, the SOP is wrong. Walk through every step against the live tool.
- Find the most ambiguous step and ask AI: “What’s the failure mode if someone misreads this step? Rewrite for clarity.” Repeat for any step a new hire could plausibly get wrong.
- Edge-case walkthrough: ask AI to generate 3 “this didn’t go as planned” scenarios. Walk through each — does the SOP still work? If not, add the edge case to the exceptions section.
- Save the SOP, the interview transcript, and the AI prompts together in the same folder. The next refresh starts from the interview, not from scratch.
First-run exercise
- Pick a process you’ve done 10+ times and that you’d genuinely like to hand off. Skip processes you’re emotionally attached to — those need a second pair of eyes anyway.
- Run the full 4-step workflow once end-to-end. Time it. First time: 90-120 minutes. Practiced: 60-75 minutes.
- Hand the SOP to one person who has NEVER done the process. Watch them attempt it. Their stumbles are your edits.
- Update the SOP based on the stumble points. The first attempt is always the editor; SOPs are tested by use.
Quality check
- Could someone hired tomorrow execute the SOP on their first try? If not, what’s missing — context, a screenshot, a specific click path?
- Are the steps in the actual order someone would do them, or in the order you remembered them? They’re often different.
- Did you fact-check every “click X” or “open Y” against the live tool? Stale UIs destroy SOP trust.
- Are exceptions and edge cases captured, or is the SOP only the happy path? Happy-path-only SOPs collapse on first real-world use.
- Is there a named owner? Anonymous SOPs rot. Named-owner SOPs get refreshed when reality changes.
How to reuse this workflow
- Save the interview prompt as a slash command or template snippet. Each new SOP starts with the same 15-question interview.
- Build a small library of “common edge case categories”: permissions issues, vendor downtime, partial data, mid-process errors. Apply these to every SOP.
- Keep all SOPs in one folder with consistent structure. Search-ability across SOPs is more useful than perfect formatting per SOP.
- Refresh every 6 months or when the underlying tool changes UI. Stale SOPs lose all trust within one wrong screenshot.
Recommended workflow
AI interviews you (15 questions) → unedited brain dump (voice-to-text encouraged) → AI drafts structured SOP → manual fact-check against live tool → ambiguity rewrite on weakest steps → 3-scenario edge-case walkthrough → archive transcript + prompts + SOP together.
Common mistakes
- Skipping the AI interview — you write a worse SOP from memory than AI extracts via questions.
- Not fact-checking — SOPs that say “click button that doesn’t exist” destroy trust on first use.
- No edge-case pass — SOPs work only on the happy path; first real-world variation collapses them.
- No named owner — anonymous SOPs rot. Someone has to own refresh.
- Documenting too many at once — quality drops sharply after the first one in a batch session.
- Skipping the new-hire test — the first attempt is the editor; SOPs are validated by use.
FAQ
- How many SOPs in a week?: Realistically 3-5 if each is 60-90 minutes of focused work. Don’t batch in one session — quality drops sharply after the first.
- Should AI sign / own the SOP?: No — a human owner per SOP is non-negotiable. Owners refresh. Anonymous SOPs rot.
- What about SOPs for creative work?: Workflows yes, exact-output SOPs no. Creative work documents principles + examples, not steps.
- How long should an SOP be?: As long as it needs to be. A 2-step process is 2 steps; a 30-step one is 30 steps. Don’t pad or compress.
- Screenshots or video?: Screenshots for individual steps, short Loom for the whole flow. Video alone doesn’t survive search; text alone doesn’t survive UI ambiguity.