Question
What is standard operating procedures?
Quick Answer
An undocumented workflow lives only in your head and degrades over time.
Example: You publish a newsletter every Thursday. Some weeks it takes 90 minutes, other weeks it takes four hours. You can't figure out why. When you finally write down every step — research, outline, draft, edit, format, schedule, promote — you discover the variance comes from one step: you sometimes research and outline simultaneously, which produces false starts. The documentation didn't change the workflow. It revealed the workflow you actually have, which turned out to be different from the one you thought you had.
This concept is part of Workflow Design in the How to Think curriculum, which builds the epistemic infrastructure for workflow design.
Learn more in these lessons
- Document your workflows
- Workflow templates
Create reusable templates for recurring workflow types so that you invest design effort once and execute many times without reinventing the process.
- Workflow sharing
Documenting workflows well enough to share them multiplies their value. A workflow that lives only in your head dies with your attention. A workflow shared becomes a reusable asset — for your team, your community, and your future self.
Go beyond the answer
This topic is part of Build Systems Beyond Yourself — a guided sequence of 20 lessons.
After completing this path you will have documented your key workflows, identified where YOU are the bottleneck (your bus factor is currently 1), built delegation criteria for systems, tools, habits, and people, and begun the identity shift that makes letting go feel like freedom instead of failure — because operational excellence means your systems run reliably without your constant attention.
Start the path →