Issue No. 9 · October 7, 2026
TL;DR
If you've explained the same task more than twice, it should be a document, not a conversation. Writing one SOP this week is the fastest way to buy back your time and stop being the bottleneck.
Hey there, Ops Connectors... how's everybody connecting the dots this week?
New month, new mode. September was about finding what's broken: your bottleneck, your handoffs, your ownerless workflows. October is about fixing it, and we start with the single highest-leverage fix there is. Writing things down.
Turn the task you keep explaining into a process someone can follow.
Here's the trigger to watch for: if you've explained the same task more than twice, you don't have a training problem. You have a documentation gap. Every time you answer "how do I do this?" from memory, you pay the same tax again. An SOP pays it once.
What an SOP actually is (and isn't)
SOP stands for standard operating procedure. It sounds corporate. It isn't. It's just the written answer to "how do we do this?" so you never have to explain it from scratch again. It is not a twenty-page manual. The best SOP fits on one screen and could be followed by someone on their first day.
Let someone else try your SOP. Where they get stuck shows you what to clarify.
Why this is the highest-leverage thing you'll do this month
Every undocumented task lives in someone's head, usually yours. That means you can't take a day off without it breaking, you can't hand it off cleanly, and every new hire relearns it by interrupting you. Writing it down once turns a recurring interruption into a link you send. You do the work one time and collect the time back every week after.
Write your first one in 20 minutes
Pick the task you explain most often. Then:
Do it and narrate. The next time you run the task, write down each step as you go, in plain language. Don't polish. Just capture.
Add the four headers. Reshape your notes under: what this is and why it matters, who owns it, the steps, and how you know it worked. That last one is the header everyone skips, and it's the one that turns a document into a system.
Test it on someone green. Hand it to a person who's never done the task. Where they get stuck is where your SOP has a gap. Fix those spots.
That's a usable SOP. Not perfect. Usable. Perfect never ships.
Four simple sections turn your notes into a usable SOP.
Don't want to start from a blank page? The Business Operating System Starter Kit has fill-in SOP templates, with the four headers already built in, for the processes most businesses need.
This week's AI prompt
This is the fastest way to get what's in your head into a real document.
The SOP Writer Prompt
"I'm going to describe a task I do from memory. Turn it into a one-screen SOP with four sections: what this is and why it matters, who owns it, the numbered steps in plain language a brand-new person could follow, and how we know it worked. Ask me up to three questions if anything is unclear before you write it. Here's the task: [BRAIN-DUMP IT]."
Regina's Ops Lesson
For a long time I was proud of being the person who knew how everything worked. If you had a question, you came to me, and I liked being the answer. Then I realized what that actually meant: nothing could happen without me, I couldn't step away, and I had quietly made myself the bottleneck I kept complaining about.
The first time I turned one of those "just ask me" tasks into a written SOP and handed it off, two things happened. The work kept getting done correctly without me, and I got a little piece of my week back. So I did it again. And again. Every SOP was one more thing that no longer required my brain.
Being the person who knows everything isn't a flex. It's a cap on your business and your freedom. The real move is making yourself unnecessary for the things that don't need you, so you're free for the things that do.
Your challenge this week: write one SOP
Here's the challenge, and I'm making it a thing all week: write one SOP. Just one. Pick the task you're tired of explaining, run the 20-minute method above, and get it out of your head.
Not sure which task to document first? The free Business Operations Quick Check points you to the areas most dependent on someone remembering, which is exactly where your first SOP pays off most. Take it here.
Then reply and tell me which task you picked. Send me the SOP if you want, and I'll give you one note to tighten it.
Want a little guidance getting more of your business out of your head?
My Six-Day Business Operations Challenge opens October 12. You’ll work through six short video lessons with practical actions to clarify priorities, document a process, plan a handoff, and track what’s working.
It’s $57, including the Business Operating System Starter Kit™. Follow one lesson a day or go at your own pace. You keep access, and enrollment closes October 17.
Quick Hits
If it lives only in your head, it isn't a process. It's a liability with your name on it.
The best SOP fits on one screen and survives your vacation.
"How do I do this?" asked a third time is a document waiting to be written.
Your takeaways
Explained it more than twice? It should be a document, not a conversation.
A good SOP is one screen, plain language, with a "how we know it worked" line.
Write one this week: narrate the steps, add the four headers, test it on someone green.
Every SOP you write is one more thing your business no longer needs you for.
Quick Answers
What is an SOP? A standard operating procedure is a short written answer to "how do we do this?" so a task can be done the same way every time without you explaining it again.
How do I write an SOP quickly? Do the task and write each step as you go, organize your notes under four headers (what it is and why, who owns it, the steps, how you know it worked), then test it on someone who has never done it.
How long should an SOP be? As short as possible while still being followable. The best ones fit on a single screen.
Know a business owner who is the only one who knows how everything works? Forward this. The first SOP is the hardest and the most freeing.
Until next time, keep connecting the dots.
Regina Morgan
aka The Dot Connector™
Founder, Break Into Ops™
Founder, The Ops Connector™
Helping professionals and businesses connect the dots through better operations, smarter systems, and AI.
Next Wednesday: The Hidden Cost of Bad Onboarding. Why the first week decides whether a new hire becomes an asset or an anchor, and how to fix yours.