# Systemization Documentation Expert > Create Standard Operating Procedures (SOPs) and document business processes for delegation and scaling. Use when preparing to hire, onboarding contractors, or systemizing recurring tasks. Use when this capability is needed. - Skill: `tomevault-io/systemization-documentation-expert` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/systemization-documentation-expert` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/systemization-documentation-expert/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/systemization-documentation-expert --- # When to Use This Skill Use this skill when you need to: - **Prepare for first hire** by documenting all processes - **Delegate tasks** without being the bottleneck - **Systemize operations** for scalable business processes - **Onboard employees or contractors** effectively - **Scale beyond solo** without sacrificing quality - **Create training documentation** for repeatable processes - **Reduce founder dependency** on day-to-day operations # Core Concepts ## Systemize Before You Hire **The critical mistake**: Hiring before systemizing leads to founder dependency and chaos **Practical approach**: Document most recurring tasks before the first hire (often targeting around 70-80% coverage for core workflows) **Case evidence**: Reilly Chase (HostiFi) has shared an SOP-first approach: recording support workflows, identifying patterns, and documenting repeatable playbooks before delegating more support work. **The E-Myth approach**: Create processes so almost anyone can produce consistent results, not clones of yourself ## 5 Types of SOPs 1. **Checklists** - For experienced workers (fast, minimal context) 2. **Decision Trees** - For complex troubleshooting (if/then flows) 3. **How-To Guides** - Step-by-step instructions (detailed procedures) 4. **Reference Guides** - Quick lookup tables (config options, error codes) 5. **Foundational Articles** - Background context (why we do it this way) # Step-by-Step SOP Creation Process ## Phase 1: Audit Your Processes (Week 1) **Document everything you do for 1 week**: - Every task, meeting, email, decision - Time spent on each activity - Tasks that repeat daily/weekly/monthly - Knowledge that's only in your head **Categorize tasks**: - **High frequency, low complexity**: Automate - **High frequency, high complexity**: Document first priority - **Low frequency, low complexity**: Quick SOP - **Low frequency, high complexity**: Video SOP or document **Deliverable**: Process inventory spreadsheet ## Phase 2: Record and Document (Weeks 2-4) **For each recurring process**: **Step 1**: Record yourself solving the problem - Use Zoom/Loom to screen record - Narrate your thought process - Capture edge cases and troubleshooting **Step 2**: Identify patterns - Watch recordings for common steps - Extract repeatable framework - Note decision points and exceptions **Step 3**: Create written SOP - Choose SOP type (checklist/guide/tree) - Write clear, actionable steps - Include screenshots and examples - Test with someone unfamiliar with process **Deliverable**: 10-20 SOPs for critical processes ## Phase 3: Organize and Store (Week 5) **Documentation tools**: - **Notion + AI**: Searchable, AI-queryable, collaborative - **ScreenSteps**: Purpose-built SOP software - **Google Drive**: Simple, accessible - **GitHub**: For technical documentation **Organization structure**: ``` SOPs/ ├── Customer Support/ │ ├── refund-policy.md │ ├── technical-troubleshooting.md │ └── common-questions.md ├── Operations/ │ ├── daily-tasks.md │ ├── weekly-reviews.md │ └── monthly-reports.md ├── Development/ │ ├── deployment-process.md │ ├── bug-fixing-workflow.md │ └── code-review-checklist.md └── Marketing/ ├── social-media-posting.md ├── email-sequences.md └── content-calendar.md ``` **Deliverable**: Organized SOP library accessible to team ## Phase 4: Validate and Iterate (Ongoing) **Test SOPs**: - Give to employee/contractor - Observe them following process - Note gaps and confusion - Revise based on feedback **Update frequency**: - Initial version: Fast and imperfect - Version 2: After first use (fix gaps) - Version 3: After 3-5 uses (polish) - Ongoing: Quarterly review and update **Deliverable**: Validated, tested SOPs # Common Mistakes **Mistake 1: Perfectionism** - **Problem**: Spending weeks perfecting SOPs before hiring - **Solution**: Done is better than perfect. Version 1 is rough but usable. **Mistake 2: Narratives Over Checklists** - **Problem**: Long-form documents when checklists work better - **Solution**: Use appropriate SOP type for the context **Mistake 3: No Screenshots or Examples** - **Problem**: Text-only SOPs are hard to follow - **Solution**: Screenshots > text, video > screenshots **Mistake 4: Buried in Obscure Tools** - **Problem**: SOPs exist but no one can find them - **Solution**: Central, searchable location (Notion, Google Drive) **Mistake 5: Never Updating** - **Problem**: SOPs become outdated and misleading - **Solution**: Quarterly reviews, version numbers, "last updated" dates # Success Metrics **SOP Health Indicators** (directional targets): | Metric | Warning | Healthy | Optimal | | ----------------------- | ---------- | --------- | -------- | | **SOP coverage** | <50% tasks | 70-80% | 90%+ | | **Founder dependency** | High | Medium | Low | | **Training time** | >4 weeks | 2-3 weeks | <2 weeks | | **Process consistency** | <70% | 80-90% | 95%+ | | **New hire autonomy** | <50% | 70-80% | 90%+ | **Red flags**: - ❌ Only founder knows how to do critical tasks - ❌ New hires need constant supervision - ❌ Processes vary depending who does them - ❌ No documentation for recurring tasks # Deep Dives For comprehensive SOP frameworks, templates, and systems, see the references: **[references/sop-templates.md](references/sop-templates.md)** - Templates for all 5 SOP types with examples - Checklist templates (fast, focused) - Decision tree frameworks (complex troubleshooting) - How-to guide structures (step-by-step) - Reference guide layouts (quick lookup) **[references/documentation-tools.md](references/documentation-tools.md)** - Notion + AI setup for searchable knowledge base - ScreenSteps for purpose-built SOP software - Video recording tools (Zoom, Loom) - Screenshot and annotation tools - Collaboration and version control **[references/hiring-checklist.md](references/hiring-checklist.md)** - Ready-to-hire benchmarks (revenue, profit, time, process) - First hire roles: Technical Support, Customer Success, Contractor - SOP coverage readiness guidance before hiring - Training and onboarding frameworks - HostiFi case study (SOP-heavy support documentation) ## Research Notes This skill synthesizes findings from scaling and systemization research: **Primary Research**: - The E-Myth Revisited approach to process documentation **Key Principles**: - **Systemize before hiring**: Build broad process coverage before first employee - **5 types of SOPs**: Checklists, decision trees, how-to guides, reference guides, foundational articles - **HostiFi case study**: SOP-heavy support operations improved delegation speed - **E-Myth approach**: Create processes so "almost anyone" can produce consistent results **Hiring Benchmarks**: - **Revenue/Profit**: consistent economics to support payroll and learning curve - **Time**: founder bandwidth is constrained despite prioritization - **Process**: recurring workflows are documented enough for safe delegation **First Hire Roles**: 1. Technical Support Engineer (handle day-to-day inquiries) 2. Customer Success Manager (onboarding, QBRs, retention) 3. Contract Specialist (task-specific: UI, content, dev) **SOP Best Practices**: - Screenshots > text (visual is faster to follow) - Checklists > narratives (for experienced workers) - Video SOPs for complex processes - Quarterly reviews and updates - Version control and change logs --- ## Next Steps After Systemization Once your SOPs are documented: 1. **Validate processes** - Test SOPs with contractor or employee 2. **Train and onboard** - Use SOPs for new hire training 3. **Measure consistency** - Track process standardization 4. **Iterate quarterly** - Update SOPs based on feedback and changes Related skills: - `solo-operations-manager` for weekly operating systems - `technical-automation-architect` for automation of documented processes --- ## Sources - [SOP Template | Confluence](https://www.atlassian.com/software/confluence/templates/sop) - [SOP Template and Guide | Asana](https://asana.com/resources/sop-template) - [Notion Help Center](https://www.notion.so/help) - [Loom Help Center](https://support.loom.com/hc/en-us) --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/briansunter) — claim your Tome and manage your conversions.