Stop Being the Bottleneck: The 2026 Guide to Creating SOPs That Actually Work
- Tyler Leber
- Jan 15
- 3 min read
If you want to step back from the day-to-day operations of your business and delegate effectively, you need solid Standard Operating Procedures (SOPs). Most founders make the mistake of spending weeks creating massive manuals that nobody reads, or they skip the process entirely because it feels like too much work.
Based on the system used at Coconut VA to train hundreds of new hires, here is the step-by-step guide to writing SOPs that do the heavy lifting for you.
Step 1: Map Your Process Visually
Before you write a single word, draw the workflow. Use a digital whiteboard tool like Mural to break down tasks visually. This helps you identify which steps are "rinse and repeat"—the points where the process is exactly the same every time. This visual map becomes the foundation for your SOP.
Step 2: Record Yourself Doing the Task
Stop trying to write manuals from memory; you will miss details and edge cases. The better way is to use Loom.
Record your screen and your voice while performing the actual task.
Explain not just what you are doing, but why you are doing it.
Don't edit out mistakes; they are valuable lessons for the person learning the process.
Pro Tip: Keep videos under 5 minutes. They are easier to consume and much simpler to replace if a part of the process changes.
Step 3: Use AI to Convert Recording into Text
You don’t need to be a technical writer. Take your Loom transcript and feed it to an AI (like ChatGPT or Gemini) with a simple prompt: "Adapt this transcript into an organized SOP I can give to a team member." The AI will turn your commentary into a clean, formatted document with step-by-step instructions.
Step 4: The "Hybrid Learning" Package (Video + Written)
Give your assistant both assets. People learn differently: some prefer reading for quick reference, while others prefer watching to understand the nuance.
"I realized that the SOP was doing the heavy lifting, not me." — Tyler Leber
Step 5: Store and Organize Obviuosly
An SOP that no one can find is useless. Centralize everything in tools like Notion or Monday.com. On Monday, for example, you can automate deadline notifications and organize tasks into groups like "Radar" (ideas), "Open Projects," and "Done".
Step 6: Create Templates for Consistency
Identify patterns and build templates for emails (Gmail/Superhuman), graphics (Canva), and project scopes. This speeds up the creation of new SOPs and ensures that your brand identity and work quality remain consistent, regardless of who is executing the task.
Step 7: Test and Iterate (The 2-Week Rule)
Your first version won't be perfect, and that’s okay. The real test is: can someone follow this manual without asking you questions? Use the questions that arise in the first two weeks to improve the document. If a question repeats, the SOP is missing something. Add the answer so the next person has the solution ready.
Conclusion: From Assistant to Leader
Well-built SOPs don't just free up your time; they create growth paths for your team. A real-world example is Issa’s story at Coconut VA: she followed and mastered the SOPs so well that she eventually systematized her own role and was promoted to lead onboarding for over 70 new VAs.
If you are a founder tired of being stuck in the "weeds," Coconut VA can help you identify what to delegate and find the right person to own those processes.
Comments