The document is a hands‑on, step‑by‑step guide for business owners, operations leads, and teams who want to capture their knowledge in Standard Operating Procedures (SOPs) so that work can be handed off and automated without recurring bottlenecks. It warns against the trap of over‑documenting and proposes a focused approach: identify high‑value, repeatable tasks using four simple tests, record the task the last time you perform it with Loom, feed the recording or transcript to Claude (or similar AI) to draft a concise SOP, then edit for accuracy. A standardized eight‑part SOP template (Name, Owner, When it runs, Outcome, Tools & access, Steps, Definition of done, Who to ask) is provided, along with guidance on keeping SOPs to one page. The guide stresses a single, searchable home for all SOPs (Google Drive, Notion, ClickUp/Asana, or a community platform) and outlines naming and indexing conventions. Ownership must be handed to the person who executes the task, reinforced by the “two‑question rule” – if a question is asked twice, the SOP is updated immediately. Ongoing maintenance includes quarterly reviews, instant updates on process changes, and using new hires as auditors. A 90‑day rollout roadmap (top 3 SOPs this week, one per week thereafter, then review and hand‑over) helps teams adopt the system without overwhelm. Finally, a table of common mistakes (e.g., trying to document everything, writing long SOPs, retaining ownership) and their fixes provides practical troubleshooting.
Topics
Why SOPs Matter and the Over‑Documentation Trap
Explains that knowledge lives in the owner’s head, causing work to bounce back, and warns against trying to document everything, which leads to unused files and perceived system failure.
Four Tests to Decide What Deserves an SOP
Provides a decision framework—repeatability, delegability, impact of error, and head‑only knowledge—to filter tasks, requiring three ‘yes’ answers to proceed.
Record the Task Live with Loom Instead of Writing from Memory
Advocates capturing the task the last time you perform it via video narration, minimizing missed steps and turning the SOP creation into a near‑zero‑cost activity.
The Eight‑Part SOP Template
Defines the mandatory sections—Name, Owner, When it runs, Outcome, Tools & access, Steps, Definition of done, Who to ask—ensuring completeness while staying concise.
Centralized, Findable Home for All SOPs
Recommends picking a single storage solution (Google Drive, Notion, ClickUp/Asana, or community platform) and outlines naming, grouping, and index‑page best practices.
Hand Over Ownership and the Two‑Question Rule
Mandates that the executor becomes the SOP owner immediately, and introduces the rule that if a question is asked twice, the SOP must be updated that day.
Keeping SOPs Alive: Review, Update, and New‑Hire Audits
Describes ongoing maintenance: quarterly skim, instant updates on process changes, and using new team members to surface gaps.
90‑Day Rollout Roadmap for SOP Adoption
Lays out a realistic cadence—top 3 SOPs this week, one per week thereafter, then review and hand‑over—so teams avoid overwhelm and achieve tangible progress.