I Automated My SOP Writing With AI and It Was a Disaster — Here’s What I Learned

#ai #career #discuss #productivity

📚 Part of the Operations That Actually Work series
Also in this series:
• Stop Building SOPs Nobody Reads
• I Automated My SOP Writing With AI — Here's What I Learned
• The Weekly Review Template That Caught Problems

I spent $87.42 on API credits last month to build an automated SOP generator. I got 47 pages of beautifully formatted nonsense that my team immediately ignored.

Here's exactly what went wrong, what I salvaged, and the 3 rules I now use instead.

The Setup (Transparent Numbers)

I run operations for a distributed team of 12. We needed documented processes for:

Client onboarding (takes ~6h per client)
Weekly delivery reviews
Incident response
Tool provisioning

Manual SOP writing was slow. I averaged one solid SOP per day. At 4 hours each, that's $600/week in my time alone.

So I built a pipeline: ChatGPT drafts → Claude refines → human approves. Estimated savings: 70% time reduction. Estimated cost: ~$30/week in API calls.

The Failure (What Actually Happened)

Week 1: The AI produced 8 SOPs in 2 days. I felt like a genius.

Week 2: I asked my lead to follow the client onboarding SOP. She got stuck at step 3 — the AI had hallucinated a tool integration that doesn't exist. She spent 45 minutes debugging before calling me.

Week 3: We had 19 AI-generated SOPs. We referenced exactly 2 of them. The rest were technically correct but practically useless — they described ideal workflows, not the messy reality of how our team actually works.

Week 4 (the disaster): A new hire tried to follow the incident response SOP during a real P1 outage. The AI had written a "recommended escalation path" that didn't match our actual Slack channels. Time-to-resolve: 3x normal.

Total API spend: $87.42
Total usable SOPs: 0
Team trust in documentation: lower than when I started

The Salvage (What I Kept)

Not everything was waste. Three patterns survived:

AI templates as starting points, not final drafts. The AI is great at structure (headers, section order, checklist frames). It's terrible at the specific decisions, exceptions, and real-world constraints that make an SOP useful.
Voice-of-process interviews. Instead of AI writing SOPs from scratch, I now record a 10-minute Loom of myself walking through a process (real clicks, real decisions). AI transcribes + formats. Human edits. Time: 25 minutes total. Quality: actually usable.
The "Friday afternoon test." An SOP passes if someone can follow it on a Friday at 4pm when you're not available to answer questions. AI SOPs fail this test every time because they don't contain the unwritten knowledge — the "oh, and if X happens, call Bob" details that only humans add.

The 3 Rules I Use Now

Rule 1: AI writes the skeleton, humans write the organs.
Structure is commodity. Judgment is not. Never publish AI-generated SOPs unedited.

Rule 2: Every SOP must survive one real run.
Before any SOP is "final," someone has to execute it start-to-finish. AI can't test what it writes. This has caught hallucinated tool names, impossible timelines, and missing approvals every single time.

Rule 3: Documentation debt compounds faster than code debt.
Bad docs cost less to create but more to clean up. The cleanup cost on those 19 AI SOPs? I had to unpublish, re-interview, and re-write 16 of them. Total time lost: ~14 hours. The "70% time savings" became a 40% net loss over 4 weeks.

What This Means (The Real Takeaway)

AI for SOP writing is like a self-driving car that works 90% of the time but randomly drops you in a ditch.

The 90% feels amazing. The 10% costs you more than the 90% saved.

I still use AI for documentation — but as a transcription tool and structural assistant, not as an author. The $87.42 taught me that the hard way.

Related: For the four rules I follow instead of AI-generated SOPs, read Stop Building SOPs Nobody Reads. And if your team needs catch problems before they become firefights, the Weekly Review Template is the diagnostic tool I use every Friday.

Browse all templates at fieldwork-sops.surge.sh — including free checklists, process improvement tools, and full SOP packs.

If you are tired of SOPs that do not work, I built a fillable SOP Template Pack with the exact templates I use now. Or grab the free Daily Operations Checklist to start.