Levels 0–2 · 8 lessons · Start here
The Ops Foundation
Any operation can be documented. The cost with AI is lower than leaving it undocumented.
Most organizations have dozens of critical processes living only in people's heads, email threads, and tribal memory. This module establishes why that costs real money and gives you the core skill to start fixing it. You will write your first SOP in 10 minutes, build a reusable prompt library, and learn to ask an AI assistant what your process is missing.
Worth knowing:A single undocumented process costs an average of $2,400 per year in lost time, errors, and rework. Most organizations have dozens of them.
Operations managersSmall business ownersExecutive assistants
Start Module 1 →Levels 3–4 · 8 lessons
Process Extraction
Your organization's processes exist. They are trapped in heads, emails, and tribal memory.
At Level 3, the approach shifts from writing SOPs to extracting knowledge that already exists in your organization. You will learn to turn a 10-minute voice memo, a disorganized Notion page, or a scattered email thread into a structured process document. By the end of this module you are no longer starting from scratch.
Worth knowing:A 10-minute unstructured voice memo, fed into Claude with a simple extraction prompt, produces a better first-draft SOP than most people write after an hour of deliberate effort.
Team leads capturing tribal knowledgeFounders systemizing their roleHR managers rebuilding onboarding docs
Start Module 2 →Levels 4–5 · 8 lessons
Workflow Design
A workflow assigns steps to roles, defines handoff triggers, and specifies what happens at each decision point.
A procedure describes steps. A workflow assigns steps to roles, defines when handoffs happen, and specifies what occurs at each decision point. This module teaches you to design complete operational workflows with AI support, including RACI tables, decision trees, escalation runbooks, and full operational playbooks any team member can execute.
Worth knowing:Describing a workflow in free-form text and asking Claude to identify every role, handoff, decision point, and dependency typically reveals 3 to 5 gaps the team did not know existed.
Project managersCOOs designing team systemsAgency owners building delivery playbooks
Start Module 3 →Levels 3–5 · 8 lessons
The Living Operations System
The problem is not writing the SOP. It is keeping it alive.
Documentation tools solve the storage and retrieval problem. They do not solve the creation and maintenance problem. This module teaches you to use a persistent AI workspace as an ops brain, build a change management process for procedure updates, run quarterly process audits, and convert your SOP library into self-service knowledge base articles and training materials.
Worth knowing:Storing your company context, team structure, and existing process docs in one AI workspace means every SOP you update starts with your operational reality already loaded. No re-explaining from scratch.
Ops managers owning documentation maintenanceHR leads with stale onboarding contentFounders preparing to delegate their role
Start Module 4 →Levels 6–7 · 8 lessons
Operations Automation
The ops workflows that eat your week can run themselves. No code required.
Zapier, Make, Power Automate, and AI assistants can connect your existing tools through plain-English workflow design. This module teaches you to build your first automated ops workflow in 30 minutes, identify the five highest-return automations for any team, and design the workflows that eliminate the most manual work from your week: status digests, meeting-to-action pipelines, inbound request triage, and onboarding sequences.
Worth knowing:Make is 13x cheaper per operation than Zapier at comparable complexity. The practical rule: prototype on Zapier, switch to Make when volume makes Zapier expensive.
Operations managers automating recurring cyclesAgency owners reducing manual client workSmall business owners reclaiming 3 to 5 hours per week
Start Module 5 →Levels 7–10 · 8 lessons
Autonomous Operations
What if your operations ran overnight, surfaced exceptions in the morning, and escalated what needed human judgment?
Autonomous operations means shifting human attention from initiating recurring cycles to designing systems and adjudicating exceptions. This module covers scheduled AI tasks, exception-flagging agents, multi-agent operations design, and the scope and guardrail patterns that make autonomous systems safe to deploy. It also covers the four most common failure modes and how to prevent each one.
Worth knowing:Agentic operations work only when the system knows what to watch, where to report, when to stop, and who owns the exception.
Ops leaders ready to delegate recurring cyclesChiefs of staff building autonomous briefing systemsFounders designing businesses that run without them
Start Module 6 →