Document and Analyze Processes with AI
Intermediate · Save 3-4 hours per process
Overview
Capture how a process actually works and analyze it for problems in one pass—the as-is flow, the pain points, and where it breaks down. This workflow pairs documentation with diagnosis, distinct from writing step-by-step SOPs for execution.
Best For
- Operations leaders
- Process analysts
- Consultants
- Team leads
Problem
There's a gap between knowing a process exists and understanding how it really works—including where it fails. Documentation efforts often capture the idealized version, missing the workarounds, the exceptions, and the friction that people have quietly normalized. Without that honest picture, you can't diagnose what's actually wrong.
Solution
AI helps you both document the real process and analyze it in the same pass. It structures your description into a clear record of how work actually flows, then probes for pain points, exceptions, and breakdowns—the honest as-is, not the org-chart fiction. This is diagnostic documentation: the goal isn't execution instructions (that's an SOP) but an accurate, analyzed picture you can improve from.
Workflow Steps
- 1
Describe the process honestly, including the workarounds and the parts that annoy people.
- 2
Ask AI to document the real flow and simultaneously probe for pain points and exceptions.
- 3
Answer its questions about where things break down or get worked around.
- 4
Get a clear as-is record plus a list of the friction points and their likely causes.
- 5
Validate with the people in the process—they'll confirm or correct the pain points.
- 6
Use the analysis to decide what to fix (pairs with the improve-workflows workflow).
Recommended Tools
Example Prompt
Help me document AND analyze this process—the honest version, including where it breaks. How the process really works (include workarounds and annoyances): """ [DESCRIBE THE PROCESS HONESTLY] """ Do two things: 1. Document the actual as-is flow clearly (steps, owners, handoffs) 2. Analyze it: where are the pain points, exceptions, breakdowns, and workarounds? What's the likely cause of each? Probe me with questions about where things go wrong or get worked around—those are the parts I'm most likely to under-report. The goal is an accurate, diagnostic picture, not polished execution instructions.