Overview
Most process documentation fails because it is written by the person who designed the process, not the person who runs it. The result is documentation that describes the ideal state, omits the edge cases that consume 40% of execution time, and becomes outdated within 90 days because no one owns the update cycle.
The Process Documentation System Prompt builds documentation from the execution layer: what actually happens, in what order, by whom, and what to do when it doesn't go as planned. The output is documentation that works for the person doing the job — not the person who designed it.
What you get: - Process audit framework: how to capture what actually happens vs. what was designed - SOP template: the structure that covers steps, decisions, edge cases, and escalation - Decision tree design: how to document judgment calls so they can be delegated - Ownership model: who writes, who reviews, who updates, and on what cadence - Version control protocol: how to keep documentation current without a dedicated team - Onboarding integration: how to use documentation to cut new hire ramp time - Quality check: the test that confirms documentation is actually usable
Built for: operators, COOs, and founders who need documentation that survives the departure of the person who wrote it — and that actually gets used.