SOPs & Documentation with AI

Standard Operating Procedures and documentation are the backbone of any scalable business. They're also incredibly tedious to write — which is exactly why most companies don't have them. AI changes that equation completely.

Why Documentation Matters

• •New hires ramp up 3x faster with good SOPs
• •You can delegate tasks you currently do yourself
• •Knowledge doesn't walk out the door when someone leaves
• •Consistent quality across your team
• •You can finally take a vacation without everything falling apart

The SOP Generator Prompt

Create a Standard Operating Procedure for: [process name]

Context: [who performs this, how often, what tools are used]

Include:
1. Purpose/Overview (2-3 sentences)
2. Scope (who this applies to)
3. Prerequisites (what's needed before starting)
4. Step-by-step instructions (numbered, with sub-steps where needed)
5. Common mistakes and how to avoid them
6. Troubleshooting guide (if X happens, do Y)
7. Quality checklist (verify these before marking complete)
8. Version history placeholder

Format: Clear numbered steps. Each step should start with an action verb.
Include [SCREENSHOT] placeholders where visual guidance would help.
Write it so someone with no prior knowledge could follow it on day one.

Documentation Types

Process Documentation

"Document the process of [task] from start to finish. Write it so someone with no prior knowledge could follow it successfully on their first try. Include the 'why' behind each step, not just the 'what.' Assume the reader has basic computer skills but no domain knowledge."

Technical Documentation

"Write technical documentation for this [API/function/system]. Include: overview (what it does in plain English), setup instructions (every step), configuration options (with defaults and examples), usage examples (3 common scenarios), error handling (what can go wrong and how to fix it), and FAQ (5 questions a new user would ask)."

Onboarding Guide

"Create an onboarding guide for a new [role] at a [company type]. Week 1-4 breakdown. Include: tools to set up (with links), people to meet (and why), processes to learn (in order of priority), goals for each week, and a 'you'll know you're ramped up when...' checklist."

Runbooks for Recurring Tasks

"Create a runbook for [recurring task, e.g., monthly reporting, weekly newsletter]. Include:

- When to do it (exact day/time)

- Tools needed (with login info placeholders)

- Step-by-step process

- What 'done' looks like

- Who to notify when complete

- Common variations (e.g., 'if it's end of quarter, also do X')"

The Interview-to-SOP Method

The fastest way to document a process that lives in someone's head:

1. 1.Record yourself (or a colleague) doing the task while narrating
2. 2.Transcribe the recording (use Otter.ai, Whisper, etc.)
3. 3.Feed the transcript to AI:

"Here's a transcript of someone performing [task name]. Convert this into a clean, step-by-step SOP. Organize the rambling narration into logical sections. Fill in any gaps you notice with clarifying questions at the end."

Tips for Great Documentation

1. 1.Tell AI the reader's skill level — "for a non-technical person" vs "for a senior developer"
2. 2.Ask for the 'why' — Steps without context are hard to follow when something goes wrong
3. 3.Include screenshots/image placeholders — A picture is worth a thousand words in documentation
4. 4.Have the actual process performer review it — They'll catch what AI and you both missed
5. 5.Add version dates and owners — Documentation rots fast; someone needs to maintain it
6. 6.Test it with a new person — The real test is whether someone can follow it cold